[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080122194710.GC3218@elte.hu>
Date: Tue, 22 Jan 2008 20:47:10 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Eduardo Pereira Habkost <ehabkost@...hat.com>,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
glommer@...il.com, tglx@...utronix.de, avi@...ranet.com,
anthony@...emonkey.ws, virtualization@...ts.linux-foundation.org,
rusty@...tcorp.com.au, ak@...e.de, chrisw@...s-sol.org,
rostedt@...dmis.org, hpa@...or.com, zach@...are.com,
roland@...hat.com, mtosatti@...hat.com
Subject: Re: [PATCH 0/4] paravirt_ops-64 compile fixes
* Jeremy Fitzhardinge <jeremy@...p.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.
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.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists