From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [patch 14/21] Xen-paravirt: Add XEN config options and disable unsupported config options. Date: Sun, 18 Feb 2007 13:32:23 +0200 Message-ID: <45D83947.8080505@qumranet.com> References: <20070216022449.739760547@goop.org> <20070216022531.570154735@goop.org> <45D54BFF.80100@vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45D54BFF.80100@vmware.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Zachary Amsden Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Ian Pratt , Andi Kleen , linux-kernel@vger.kernel.org, Chris Wright , virtualization@lists.osdl.org, "Eric W. Biederman" , Andrew Morton , Ingo Molnar , Christian Limpach List-Id: virtualization@lists.linuxfoundation.org Zachary Amsden wrote: > Jeremy Fitzhardinge wrote: >> The XEN config option enables the Xen paravirt_ops interface, which is >> installed when the kernel finds itself running under Xen. (By some >> as-yet fully defined mechanism, implemented in a future patch.) >> >> Xen is no longer a sub-architecture, so the X86_XEN subarch config >> option has gone. >> >> The disabled config options are: >> - PREEMPT: Xen doesn't support it >> - HZ: set to 100Hz for now, to cut down on VCPU context switch rate. >> This will be adapted to use tickless later. >> - kexec: not yet supported >> >> Signed-off-by: Jeremy Fitzhardinge >> Signed-off-by: Ian Pratt >> Signed-off-by: Christian Limpach >> Signed-off-by: Chris Wright >> > > We do support different HZ values, although 100HZ is actually > preferable for us, so I don't object to that. Ditto for kvm. > PREEMPT is supported by us, but not as tested as I would like, so I > also don't object to dropping it for generic paravirt guests - Rusty - > Avi any objections to dropping preempt in terms of lguest/KVM > paravirtualization? I don't have any objections myself, but Ingo (who has done the bulk of the kvm paravirt work; cc'ed) uses PREEMPT_RT, so he will certainly object. > > Paravirt-ops definitely needs a hook for kexec, although we should not > disable kexec for the natively booted paravirt-ops. Eric - is there a > way to disable it at runtime? kvm paravirt should work correctly with kexec. > > We do support the doublefault task gate, and it would be good to keep > it, but I can't complain so much if it is gone from generic paravirt > kernels for now, because it is non-essential, and generally fatal > anyway. We do need it for native boots of paravirt-ops kernels, > however, so turning off the config option still needs to be revisited. kvm doesn't support task gates (a task switch will immediately kill the guest). -- error compiling committee.c: too many arguments to function