search for: config_paravirt

Given all the discussion, let's just require NO_HZ when CONFIG_PARAVIRT. Anyone object? Signed-off-by: Chris Wright <chrisw@sous-sol.org> --- --- a/arch/i386/Kconfig Mon Mar 12 11:07:45 2007 -0700 +++ b/arch/i386/Kconfig Mon Mar 12 16:53:14 2007 -0700 @@ -208,7 +208,7 @@ endchoice config PARAVIRT bool "Paravirtualization support (EXPERIMENTAL)"...

Given all the discussion, let's just require NO_HZ when CONFIG_PARAVIRT. Anyone object? Signed-off-by: Chris Wright <chrisw@sous-sol.org> --- --- a/arch/i386/Kconfig Mon Mar 12 11:07:45 2007 -0700 +++ b/arch/i386/Kconfig Mon Mar 12 16:53:14 2007 -0700 @@ -208,7 +208,7 @@ endchoice config PARAVIRT bool "Paravirtualization support (EXPERIMENTAL)"...

...-714,6 +714,41 @@ kernel tries to allocate a number starting from this one. ============================================================== +paravirt_poll_grow: (X86 only) + +Multiplied value to increase the poll time. This is expected to take +effect only when running as a virtual machine with CONFIG_PARAVIRT +enabled. This can't bring any benifit on bare mental even with +CONFIG_PARAVIRT enabled. + +By default this value is 2. Possible values to set are in range {2..16}. + +============================================================== + +paravirt_poll_shrink: (X86 only) + +Divided value to reduce...

...-714,6 +714,41 @@ kernel tries to allocate a number starting from this one. ============================================================== +paravirt_poll_grow: (X86 only) + +Multiplied value to increase the poll time. This is expected to take +effect only when running as a virtual machine with CONFIG_PARAVIRT +enabled. This can't bring any benifit on bare mental even with +CONFIG_PARAVIRT enabled. + +By default this value is 2. Possible values to set are in range {2..16}. + +============================================================== + +paravirt_poll_shrink: (X86 only) + +Divided value to reduce...

...this one. >> >> ============================================================== >> >> +paravirt_poll_grow: (X86 only) >> + >> +Multiplied value to increase the poll time. This is expected to take >> +effect only when running as a virtual machine with CONFIG_PARAVIRT >> +enabled. This can't bring any benifit on bare mental even with >> +CONFIG_PARAVIRT enabled. >> + >> +By default this value is 2. Possible values to set are in range {2..16}. >> + >> +============================================================== >>...

...this one. >> >> ============================================================== >> >> +paravirt_poll_grow: (X86 only) >> + >> +Multiplied value to increase the poll time. This is expected to take >> +effect only when running as a virtual machine with CONFIG_PARAVIRT >> +enabled. This can't bring any benifit on bare mental even with >> +CONFIG_PARAVIRT enabled. >> + >> +By default this value is 2. Possible values to set are in range {2..16}. >> + >> +============================================================== >>...

Tim Chen wrote: > With CONFIG_PARAVIRT turned on, I've found that time invoking > system_call jumped up quite a lot. Using TCP streaming test as a > workload and running on 32-bit 2.6.20 kernel, system_call goes up from > 0.00025% all the way to 1.6% in the oprofile data. There is a drop of > about 4% in overall throug...

Tim Chen wrote: > With CONFIG_PARAVIRT turned on, I've found that time invoking > system_call jumped up quite a lot. Using TCP streaming test as a > workload and running on 32-bit 2.6.20 kernel, system_call goes up from > 0.00025% all the way to 1.6% in the oprofile data. There is a drop of > about 4% in overall throug...

Paravirt ops is currently only capable of either replacing a lot of Linux internal code or none at all. The are users that don't need all of the possibilities pv-ops delivers though. On KVM for example we're perfectly fine not using the PV MMU, thus not touching any MMU code. That way we don't have to improve pv-ops to become fast, we just don't compile the MMU parts in! This

Paravirt ops is currently only capable of either replacing a lot of Linux internal code or none at all. The are users that don't need all of the possibilities pv-ops delivers though. On KVM for example we're perfectly fine not using the PV MMU, thus not touching any MMU code. That way we don't have to improve pv-ops to become fast, we just don't compile the MMU parts in! This

...e patches must have been a nightmare 8( Andi then tried to fix it with x86_64-mm-paravirt-compile.patch but then it didn't boot so he disabled it in x86_64-mm-paravirt-broken.patch This patch undoes those two patches and rearranges processor.h correctly so the kernel compiles and boots with CONFIG_PARAVIRT. Andi's "paravirt-compile" patch also cleans up the spinlock header, which is good but should probably be patched separately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/dontdiff --minimal linux-2.6...

...e patches must have been a nightmare 8( Andi then tried to fix it with x86_64-mm-paravirt-compile.patch but then it didn't boot so he disabled it in x86_64-mm-paravirt-broken.patch This patch undoes those two patches and rearranges processor.h correctly so the kernel compiles and boots with CONFIG_PARAVIRT. Andi's "paravirt-compile" patch also cleans up the spinlock header, which is good but should probably be patched separately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/dontdiff --minimal linux-2.6...

...llocate a number starting from this one. > > ============================================================== > > +paravirt_poll_grow: (X86 only) > + > +Multiplied value to increase the poll time. This is expected to take > +effect only when running as a virtual machine with CONFIG_PARAVIRT > +enabled. This can't bring any benifit on bare mental even with > +CONFIG_PARAVIRT enabled. > + > +By default this value is 2. Possible values to set are in range {2..16}. > + > +============================================================== > + > +paravirt_poll_shrink...

FYI - I was working on some changes, and just noticed this with !CONFIG_PARAVIRT. CC arch/i386/kernel/alternative.o arch/i386/kernel/alternative.c:436: error: ?apply_paravirt? undeclared here (not in a function) arch/i386/kernel/alternative.c:436: warning: type defaults to ?int? in declaration of ?apply_paravirt? arch/i386/kernel/alternative.c:437: error: ?__start_par...

FYI - I was working on some changes, and just noticed this with !CONFIG_PARAVIRT. CC arch/i386/kernel/alternative.o arch/i386/kernel/alternative.c:436: error: ?apply_paravirt? undeclared here (not in a function) arch/i386/kernel/alternative.c:436: warning: type defaults to ?int? in declaration of ?apply_paravirt? arch/i386/kernel/alternative.c:437: error: ?__start_par...

...ne. > > > ============================================================== > > > +paravirt_poll_grow: (X86 only) > > > + > > > +Multiplied value to increase the poll time. This is expected to take > > > +effect only when running as a virtual machine with CONFIG_PARAVIRT > > > +enabled. This can't bring any benifit on bare mental even with > > > +CONFIG_PARAVIRT enabled. > > > + > > > +By default this value is 2. Possible values to set are in range {2..16}. > > > + > > > +====================================...

On Mon, 2007-03-05 at 13:06 +0100, Ingo Molnar wrote: > Subject: [patch] paravirt: VDSO page is essential > From: Ingo Molnar <mingo@elte.hu> > > commit 3bbf54725467d604698721384d858b5983b87e8f disables the VDSO for > CONFIG_PARAVIRT kernels. This #ifdeffery was a bad change: the VDSO is > an essential component of Linux, and this change forces all of them to > use int $0x80 - including sane ones like KVM. (If a hypervisor does not > handle the VDSO properly then it can work things around via the vdso=0 > boot o...

On Mon, 2007-03-05 at 13:06 +0100, Ingo Molnar wrote: > Subject: [patch] paravirt: VDSO page is essential > From: Ingo Molnar <mingo@elte.hu> > > commit 3bbf54725467d604698721384d858b5983b87e8f disables the VDSO for > CONFIG_PARAVIRT kernels. This #ifdeffery was a bad change: the VDSO is > an essential component of Linux, and this change forces all of them to > use int $0x80 - including sane ones like KVM. (If a hypervisor does not > handle the VDSO properly then it can work things around via the vdso=0 > boot o...

This version over last version: (1) Gets rid of the no_paravirt.h header and leaves native ops in place (with some reshuffling to keep then under one #ifdef). (2) Fixes the "X crashes with CONFIG_PARAVIRT=y" bug. (3) Puts __ex_table entry in paravirt iret. Another followup patch implements binary patching... Rusty. === Create a paravirt.h header for all the critical operations which need to be replaced with hypervisor calls, and include that instead of defining native operations, when CONFIG_P...

This version over last version: (1) Gets rid of the no_paravirt.h header and leaves native ops in place (with some reshuffling to keep then under one #ifdef). (2) Fixes the "X crashes with CONFIG_PARAVIRT=y" bug. (3) Puts __ex_table entry in paravirt iret. Another followup patch implements binary patching... Rusty. === Create a paravirt.h header for all the critical operations which need to be replaced with hypervisor calls, and include that instead of defining native operations, when CONFIG_P...