Ingo Molnar wrote:
* Jeremy Fitzhardinge <[EMAIL PROTECTED]> 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
* Jeremy Fitzhardinge <[EMAIL PROTECTED]> 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
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
On Tue, Jan 22, 2008 at 01:02:07PM +0100, Ingo Molnar wrote:
>
> * Eduardo Habkost <[EMAIL PROTECTED]> wrote:
>
> > This series contain fixes to make the paravirt_ops code compile and
> > boot on x86_64.
> >
> > This is a follow-up for the previous series from Glauber.
>
> thanks Eduardo,
* Eduardo Habkost <[EMAIL PROTECTED]> wrote:
> This series contain fixes to make the paravirt_ops code compile and
> boot on x86_64.
>
> This is a follow-up for the previous series from Glauber.
thanks Eduardo, i've applied your fixes.
could you perhaps send the missing bits that add the
* Eduardo Habkost [EMAIL PROTECTED] wrote:
This series contain fixes to make the paravirt_ops code compile and
boot on x86_64.
This is a follow-up for the previous series from Glauber.
thanks Eduardo, i've applied your fixes.
could you perhaps send the missing bits that add the missing
On Tue, Jan 22, 2008 at 01:02:07PM +0100, Ingo Molnar wrote:
* Eduardo Habkost [EMAIL PROTECTED] wrote:
This series contain fixes to make the paravirt_ops code compile and
boot on x86_64.
This is a follow-up for the previous series from Glauber.
thanks Eduardo, i've applied your
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
Ingo Molnar wrote:
* Jeremy Fitzhardinge [EMAIL PROTECTED] 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
* Jeremy Fitzhardinge [EMAIL PROTECTED] 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
This series contain fixes to make the paravirt_ops code compile and boot
on x86_64.
This is a follow-up for the previous series from Glauber.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
This series contain fixes to make the paravirt_ops code compile and boot
on x86_64.
This is a follow-up for the previous series from Glauber.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
12 matches
Mail list logo
