[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52D472ED.3050303@redhat.com>
Date: Tue, 14 Jan 2014 00:12:45 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Dave Hansen <dave@...1.net>
CC: linux-kernel@...r.kernel.org, x86@...nel.org, bp@...e.de,
dtor@...are.com, kys@...rosoft.com, haiyangz@...rosoft.com,
agraf@...e.de, gleb@...hat.com
Subject: Re: [PATCH 11/12] x86 Kconfig: create x86/Kconfig.virt
Il 14/01/2014 00:00, Dave Hansen ha scritto:
>> > Please rename this to "Hypervisor support" or "Virtual guest support" to
>> > avoid confusion with KVM. Note there is a reference to
>> > CONFIG_VIRTUALIZATION in configs/kvm_guest.config.
> I'm not sure I'm following. When this gets done, we have a menu that says:
>
>> > --- Virtualization
>> > <*> Kernel-based Virtual Machine (KVM) support
>> > <*> KVM for Intel processors support
>> > <*> KVM for AMD processors support
>> > [*] Audit KVM MMU
>> > [*] KVM legacy PCI device assignment support
>> > < > Host kernel accelerator for virtio net
>> > [*] Linux guest support --->
Ok, got it now. The diff headers confused me...
I think this is as confusing as before, perhaps worse because it is not
clear that Linux guest support is not limited to KVM. If you really
want a Virtualization menu, you have to clearly separate the guest and host:
--- Virtualization
Linux guest support --->
Virtualization host support --->
with KVM and vhost under the second item.
> So this new menu grouping includes both KVM, Xen, and lguest. It
> includes both the host-side and guest-side support. Are you suggesting
> that we separate out host and guest somehow?
--
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