From: Paolo Bonzini <pbonzini@redhat.com>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, bp@suse.de,
dtor@vmware.com, kys@microsoft.com, haiyangz@microsoft.com,
agraf@suse.de, gleb@redhat.com
Subject: Re: [PATCH 11/12] x86 Kconfig: create x86/Kconfig.virt
Date: Tue, 14 Jan 2014 00:12:45 +0100 [thread overview]
Message-ID: <52D472ED.3050303@redhat.com> (raw)
In-Reply-To: <52D47020.6050306@sr71.net>
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?
next prev parent reply other threads:[~2014-01-13 23:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 19:22 [PATCH 00/12] [v2] Reorganize x86 Kconfig menu Dave Hansen
2014-01-13 19:22 ` [PATCH 01/12] x86 Kconfig: create extended platforms menu Dave Hansen
2014-01-13 19:22 ` [PATCH 02/12] x86 Kconfig: memory options Dave Hansen
2014-01-13 19:22 ` [PATCH 03/12] x86 Kconfig: move highmem Dave Hansen
2014-01-13 19:22 ` [PATCH 04/12] x86 Kconfig: processor options menu Dave Hansen
2014-01-13 19:22 ` [PATCH 05/12] x86 Kconfig: processor drivers Dave Hansen
2014-01-13 19:22 ` [PATCH 06/12] x86 Kconfig: scheduler options Dave Hansen
2014-01-13 19:22 ` [PATCH 07/12] x86 Kconfig: move memtest Dave Hansen
2014-01-13 19:22 ` [PATCH 08/12] x86 Kconfig: bury obscure options Dave Hansen
2014-01-13 19:22 ` [PATCH 09/12] x86 Kconfig: create mtrr menu under processsor options Dave Hansen
2014-01-13 19:22 ` [PATCH 10/12] x86 Kconfig: MCE menu Dave Hansen
2014-01-13 19:22 ` [PATCH 11/12] x86 Kconfig: create x86/Kconfig.virt Dave Hansen
2014-01-13 22:46 ` Paolo Bonzini
2014-01-13 23:00 ` Dave Hansen
2014-01-13 23:12 ` Paolo Bonzini [this message]
2014-01-14 0:04 ` Dave Hansen
2014-01-13 19:23 ` [PATCH 12/12] x86 Kconfig: move paravirt under "Virtualization" Dave Hansen
2014-01-14 14:25 ` [PATCH 00/12] [v2] Reorganize x86 Kconfig menu Borislav Petkov
2014-01-14 22:12 ` Dave Hansen
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=52D472ED.3050303@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=bp@suse.de \
--cc=dave@sr71.net \
--cc=dtor@vmware.com \
--cc=gleb@redhat.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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