search for: vvar

...nd 5 fix Xen (I hope). - Patch 6 (optional) adds a trace event to vsyscall emulation. It will make it easier to handle performance regression reports :) [1] https://gitorious.org/linux-test-utils/linux-clock-tests Changes from v1: - Improve changelog message for "x86-64/xen: Enable the vvar mapping" - Fix 32-bit build. - Add patch 6. Andy Lutomirski (6): x86-64: Pad vDSO to a page boundary x86-64: Move the "user" vsyscall segment out of the data segment. x86-64: Work around gold bug 13023 x86-64/xen: Enable the vvar mapping x86-64: Add user_64bit_mode parav...

...nd 5 fix Xen (I hope). - Patch 6 (optional) adds a trace event to vsyscall emulation. It will make it easier to handle performance regression reports :) [1] https://gitorious.org/linux-test-utils/linux-clock-tests Changes from v1: - Improve changelog message for "x86-64/xen: Enable the vvar mapping" - Fix 32-bit build. - Add patch 6. Andy Lutomirski (6): x86-64: Pad vDSO to a page boundary x86-64: Move the "user" vsyscall segment out of the data segment. x86-64: Work around gold bug 13023 x86-64/xen: Enable the vvar mapping x86-64: Add user_64bit_mode parav...

...nd 5 fix Xen (I hope). - Patch 6 (optional) adds a trace event to vsyscall emulation. It will make it easier to handle performance regression reports :) [1] https://gitorious.org/linux-test-utils/linux-clock-tests Changes from v1: - Improve changelog message for "x86-64/xen: Enable the vvar mapping" - Fix 32-bit build. - Add patch 6. Andy Lutomirski (6): x86-64: Pad vDSO to a page boundary x86-64: Move the "user" vsyscall segment out of the data segment. x86-64: Work around gold bug 13023 x86-64/xen: Enable the vvar mapping x86-64: Add user_64bit_mode parav...

...and 5 from some Xen/paravirt people. [1] https://gitorious.org/linux-test-utils/linux-clock-tests Andy Lutomirski (5): x86-64: Pad vDSO to a page boundary x86-64: Move the "user" vsyscall segment out of the data segment. x86-64: Work around gold bug 13023 x86-64/xen: Enable the vvar mapping x86-64: Add user_64bit_mode paravirt op arch/x86/include/asm/desc.h | 4 +- arch/x86/include/asm/paravirt_types.h | 6 ++++ arch/x86/include/asm/ptrace.h | 19 +++++++++++++ arch/x86/kernel/paravirt.c | 4 +++ arch/x86/kernel/step.c...

...and 5 from some Xen/paravirt people. [1] https://gitorious.org/linux-test-utils/linux-clock-tests Andy Lutomirski (5): x86-64: Pad vDSO to a page boundary x86-64: Move the "user" vsyscall segment out of the data segment. x86-64: Work around gold bug 13023 x86-64/xen: Enable the vvar mapping x86-64: Add user_64bit_mode paravirt op arch/x86/include/asm/desc.h | 4 +- arch/x86/include/asm/paravirt_types.h | 6 ++++ arch/x86/include/asm/ptrace.h | 19 +++++++++++++ arch/x86/kernel/paravirt.c | 4 +++ arch/x86/kernel/step.c...

...and 5 from some Xen/paravirt people. [1] https://gitorious.org/linux-test-utils/linux-clock-tests Andy Lutomirski (5): x86-64: Pad vDSO to a page boundary x86-64: Move the "user" vsyscall segment out of the data segment. x86-64: Work around gold bug 13023 x86-64/xen: Enable the vvar mapping x86-64: Add user_64bit_mode paravirt op arch/x86/include/asm/desc.h | 4 +- arch/x86/include/asm/paravirt_types.h | 6 ++++ arch/x86/include/asm/ptrace.h | 19 +++++++++++++ arch/x86/kernel/paravirt.c | 4 +++ arch/x86/kernel/step.c...

...e methods that I used? Can any one give some help? I am stuck for a week. I can send the code to you. First time to raise a question here. Not sure if it is proper to post all code. ########################################################################## # the main R script n=100 beta=c(-0.5,1) vvar=2 #sigma^2=2 psi=matrix(c(1,0.2,0.2,1),2,2) b.m.true=mvrnorm(n=n,mu=c(0,0),Sigma=psi) #100*2 matrix, each row is the b_i Xi=cbind(rnorm(7,mean=2,sd=0.5),log(2:8)) #Xi=cbind(rep(1,7),1:7) y.m=matrix(NA,nrow=n,ncol=nrow(Xi)) #100*7, each row is a y_i Zi=Xi b.list=as.list(data.frame(t(b.m.true))...

...e give some help? I am stuck for a week. I can send the code to you. First time to raise a question here. Not sure if it is proper to post all code. Below is the same as the zip file. ########################################################################## # the main R script n=100 beta=c(-0.5,1) vvar=2 #sigma^2=2 psi=matrix(c(1,0.2,0.2,1),2,2) b.m.true=mvrnorm(n=n,mu=c(0,0),Sigma=psi) #100*2 matrix, each row is the b_i Xi=cbind(rnorm(7,mean=2,sd=0.5),log(2:8)) #Xi=cbind(rep(1,7),1:7) y.m=matrix(NA,nrow=n,ncol=nrow(Xi)) #100*7, each row is a y_i Zi=Xi b.list=as.list(data.frame(t(b.m.true))...

Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the required support by adding hvclock_page VVAR. Signed-off-by: Vitaly Kuznetsov <vkuznets at redhat.com> --- arch/x86/entry/vdso/vclock_gettime.c | 36 +++++++++++++++++++++++++++++++++++ arch/x86/entry/vdso/vdso-layout.lds.S | 3 ++- arch/x86/entry/vdso/vdso2c.c | 3 +++ arch/x86/entry/vdso/vma.c | 7 +++++++ a...

Hi, Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. I implemented the required support re-using pvclock_page VVAR. Simple sysbench test shows the following results: Before: # time sysbench --test=memory --max-requests=500000 run ... real 1m22.618s user 0m50.193s sys 0m32.268s After: # time sysbench --test=memory --max-requests=500000 run ... real 0m50.218s user 0m50.171s sys 0m0.016s So...

Hi, Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. I implemented the required support re-using pvclock_page VVAR. Simple sysbench test shows the following results: Before: # time sysbench --test=memory --max-requests=500000 run ... real 1m22.618s user 0m50.193s sys 0m32.268s After: # time sysbench --test=memory --max-requests=500000 run ... real 0m50.218s user 0m50.171s sys 0m0.016s So...

...gnu/ld-2.19.so 0x7f276ea03000-0x7f276ea08000 0x7f276ea1e000-0x7f276ea2a000 0x7f276ea2a000-0x7f276ea2b000 /lib/x86_64-linux-gnu/ld-2.19.so 0x7f276ea2b000-0x7f276ea2c000 /lib/x86_64-linux-gnu/ld-2.19.so 0x7f276ea2c000-0x7f276ea2d000 0x7ffd99d31000-0x7ffd99d52000 [stack] 0x7ffd99d73000-0x7ffd99d75000 [vvar] 0x7ffd99d75000-0x7ffd99d77000 [vdso] 0xffffffffff600000-0xffffffffff601000 [vsyscall] ==25950==End of process memory map. -- greg

Hi, Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implemented the required support. Simple sysbench test shows the following results: Before: # time sysbench --test=memory --max-requests=500000 run ... real 1m22.618s user 0m50.193s sys 0m32.268s After: # time sysbench --test=memory

Hi, Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implemented the required support. Simple sysbench test shows the following results: Before: # time sysbench --test=memory --max-requests=500000 run ... real 1m22.618s user 0m50.193s sys 0m32.268s After: # time sysbench --test=memory

...gnu/ld-2.19.so 0x7f86a78d7000-0x7f86a78dc000 0x7f86a78f2000-0x7f86a78fe000 0x7f86a78fe000-0x7f86a78ff000 /lib/x86_64-linux-gnu/ld-2.19.so 0x7f86a78ff000-0x7f86a7900000 /lib/x86_64-linux-gnu/ld-2.19.so 0x7f86a7900000-0x7f86a7901000 0x7fff98977000-0x7fff98998000 [stack] 0x7fff989b2000-0x7fff989b4000 [vvar] 0x7fff989b4000-0x7fff989b6000 [vdso] 0xffffffffff600000-0xffffffffff601000 [vsyscall] ==14645==End of process memory map. On Mon, Sep 14, 2015 at 9:46 PM, Evgenii Stepanov <eugeni.stepanov at gmail.com> wrote: > Yes, the kernel is too new. > This bug has a patch set that's compati...

Hi, merge window is about to close so I hope it's OK to make another try here. Changes since v2: - Add explicit READ_ONCE() to not rely on 'volatile' [Andy Lutomirski] - rdtsc() -> rdtsc_ordered() [Andy Lutomirski] - virt_rmb() -> smp_rmb() [Thomas Gleixner, Andy Lutomirski] Thomas, Andy, it seems the only blocker for the series was the ambiguity with TSC page read algorithm.

Hi, merge window is about to close so I hope it's OK to make another try here. Changes since v2: - Add explicit READ_ONCE() to not rely on 'volatile' [Andy Lutomirski] - rdtsc() -> rdtsc_ordered() [Andy Lutomirski] - virt_rmb() -> smp_rmb() [Thomas Gleixner, Andy Lutomirski] Thomas, Andy, it seems the only blocker for the series was the ambiguity with TSC page read algorithm.

...-nostdlib -fPIC -shared -Wl,-soname=linux-vdso.so.1 -Wl,--hash-style=sysv -Wl,-z,max-page-size=4096 -Wl,-z,common-page-size=4096 -Wl,-T,arch/x86_64/vdso/vdso.lds arch/x86_64/vdso/vdso-start.o arch/x86_64/vdso/vdso-note.o arch/x86_64/vdso/vclock_gettime.o arch/x86_64/vdso/vgetcpu.o arch/x86_64/vdso/vvar.o -o arch/x86_64/vdso/vdso.so arch/x86_64/vdso/vvar.o: file not recognized: File format not recognized collect2: ld returned 1 exit status .... Now, If the build systems generates .so files, then it will be difficult o actually generate fully arch-independent kernel code, isn't it? thanks, as...

On Wed, Feb 8, 2017 at 9:07 AM, Vitaly Kuznetsov <vkuznets at redhat.com> wrote: > Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol > defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the > required support re-using pvclock_page VVAR as VCLOCK_PVCLOCK is mutually > exclusive with VCLOCK_HVCLOCK at run time. > > Signed-off-by: Vitaly Kuznetsov <vkuznets at redhat.com> > --- > arch/x86/entry/vdso/vclock_gettime.c | 48 ++++++++++++++++++++++++++++++++++++ > arch/x86/entry/vdso/vma.c | 26 ++++++...

On Wed, Feb 8, 2017 at 9:07 AM, Vitaly Kuznetsov <vkuznets at redhat.com> wrote: > Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol > defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the > required support re-using pvclock_page VVAR as VCLOCK_PVCLOCK is mutually > exclusive with VCLOCK_HVCLOCK at run time. > > Signed-off-by: Vitaly Kuznetsov <vkuznets at redhat.com> > --- > arch/x86/entry/vdso/vclock_gettime.c | 48 ++++++++++++++++++++++++++++++++++++ > arch/x86/entry/vdso/vma.c | 26 ++++++...