[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47962E1D.2090308@goop.org>
Date: Tue, 22 Jan 2008 09:55:41 -0800
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Eduardo Pereira Habkost <ehabkost@...hat.com>
CC: Ingo Molnar <mingo@...e.hu>, 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
Eduardo Pereira Habkost wrote:
> If this is desirable for broader testing, we can make config PARAVIRT
> visible and selectable on menuconfig, even when there is no guest
> implementation being enabled. Should I do it?
>
Yes please.
> 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.
J
--
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