From: Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Eduardo Pereira Habkost <ehabkost@redhat.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, chrisw@sous-sol.org,
anthony@codemonkey.ws, hpa@zytor.com, akpm@linux-foundation.org,
tglx@linutronix.de, roland@redhat.com, ak@suse.de
Subject: Re: [PATCH 0/4] paravirt_ops-64 compile fixes
Date: Tue, 22 Jan 2008 12:05:14 -0800 [thread overview]
Message-ID: <47964C7A.6000609@citrix.com> (raw)
In-Reply-To: <20080122194710.GC3218@elte.hu>
Ingo Molnar wrote:
> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>
>>> Maybe should this force-paravirt mode be a kernel debugging option?
>>>
>> No, just a plain CONFIG_PARAVIRT to turn it on and off independently
>> of everything else.
>>
>
> it should be a debugging option in the way that it's dependent on
> KERNEL_DEBUG and KERNEL_EXPERIMENTAL.
>
EXPERIMENTAL certainly, but not DEBUG. Sure, CONFIG_PARAVIRT is
somewhat useless if you don't also configure Xen/lguest/etc, but running
a paravirt system on bare hardware will probably be the most common way
a paravirt kernel gets run (a distro will always enable it and compile
in whatever hypervisor support they want, but most people will end up
just running it on bare hardware). Therefore, we should try to be as
sure as possible that PARAVIRT works well (ie, indistinguishable from
non-PARAVIRT) on bare hardware.
> i dont think you shold worry about this - i think 64-bit guest support
> for specific hypervisors could be added even after the merge window, if
> it's reasonably isolated (which i'd expect it to be). It clearly cannot
> break anything else so it's the same category as new driver or new
> hardware support - more relaxed integration rules. Then we can remove
> the KERNEL_DEBUG and KERNEL_EXPERIMENTAL dependency as well.
Good, I'm glad you feel that way.
J
prev parent reply other threads:[~2008-01-22 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 21:48 [PATCH 0/4] paravirt_ops-64 compile fixes Eduardo Habkost
2008-01-21 21:48 ` [PATCH 1/4] Add missing semicolon to SWAPGS macro Eduardo Habkost
2008-01-21 21:48 ` [PATCH 2/4] include/asm-x86/paravirt.h: x86_64 mmu operations Eduardo Habkost
2008-01-21 21:48 ` [PATCH 3/4] Don't set pagetable_setup_{start,done} hooks on x86_64 Eduardo Habkost
2008-01-21 21:48 ` [PATCH 4/4] Fill in missing pv_mmu_ops entries for PAGETABLE_LEVELS >= 3 Eduardo Habkost
2008-01-22 12:02 ` [PATCH 0/4] paravirt_ops-64 compile fixes Ingo Molnar
2008-01-22 12:34 ` Eduardo Pereira Habkost
2008-01-22 17:55 ` Jeremy Fitzhardinge
2008-01-22 18:50 ` [PATCH 1/2] Allow enabling PARAVIRT without any guest implementation Eduardo Pereira Habkost
2008-01-22 18:52 ` [PATCH 2/2] Remove depends on X86_32 from PARAVIRT & PARAVIRT_GUEST Eduardo Pereira Habkost
2008-01-22 19:47 ` [PATCH 0/4] paravirt_ops-64 compile fixes Ingo Molnar
2008-01-22 20:05 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47964C7A.6000609@citrix.com \
--to=jeremy.fitzhardinge@citrix.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anthony@codemonkey.ws \
--cc=chrisw@sous-sol.org \
--cc=ehabkost@redhat.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).