From: Sasha Levin <levinsasha928@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Pekka Enberg <penberg@kernel.org>, Ingo Molnar <mingo@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Fengguang Wu <fengguang.wu@intel.com>,
lkml <linux-kernel@vger.kernel.org>, x86-ml <x86@kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH] x86: Add a Kconfig shortcut for a kvm-bootable kernel
Date: Tue, 16 Apr 2013 20:38:56 -0400 [thread overview]
Message-ID: <516DEF20.9060303@gmail.com> (raw)
In-Reply-To: <20130416161852.GH5332@pd.tnic>
On 04/16/2013 12:18 PM, Borislav Petkov wrote:
> On Sun, Apr 14, 2013 at 01:03:20PM +0200, Borislav Petkov wrote:
>> On Sun, Apr 14, 2013 at 12:31:12PM +0300, Pekka Enberg wrote:
>>> I obviously support having something like this in mainline. I wonder
>>> though if we could just call this "default standalone KVM guest
>>> config" instead of emphasizing testing angle.
>>
>> /me nods agreeingly...
>>
>> And it should be unter HYPERVISOR_GUEST where the rest of this stuff
>> resides. Good point.
>
> Sanity check question:
>
> Why not add the select stuff, i.e. this:
>
> select NET
> select NETDEVICES
> select PCI
> select BLOCK
> select BLK_DEV
> select NETWORK_FILESYSTEMS
> select INET
> select EXPERIMENTAL
> select TTY
> select SERIAL_8250
> select SERIAL_8250_CONSOLE
> select IP_PNP
> select IP_PNP_DHCP
> select BINFMT_ELF
> select PCI_MSI
> select HAVE_ARCH_KGDB
> select DEBUG_KERNEL
> select KGDB
> select KGDB_SERIAL_CONSOLE
> select VIRTUALIZATION
> select VIRTIO
> select VIRTIO_RING
> select VIRTIO_PCI
> select VIRTIO_BLK
> select VIRTIO_CONSOLE
> select VIRTIO_NET
> select 9P_FS
> select NET_9P
> select NET_9P_VIRTIO
>
> to the option below which we already have. It is in the same sense a KVM
> guest support deal.
>
> Hmm.
>
> KVM people, any objections?
>
> config KVM_GUEST
> bool "KVM Guest support (including kvmclock)"
> depends on PARAVIRT
> select PARAVIRT_CLOCK
> default y
> ---help---
> This option enables various optimizations for running under the KVM
> hypervisor. It includes a paravirtualized clock, so that instead
> of relying on a PIT (or probably other) emulation by the
> underlying device model, the host provides the guest with
> timing infrastructure such as time of day, and system time
KVM guests don't need a serial device, KGDB, DEBUG_KERNEL or 9p in particular.
Thanks,
Sasha
next prev parent reply other threads:[~2013-04-17 0:39 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 18:19 [PATCH] x86: Add a Kconfig shortcut for a kvm-bootable kernel Borislav Petkov
2013-04-12 20:08 ` Randy Dunlap
2013-04-14 9:31 ` Pekka Enberg
2013-04-14 11:03 ` Borislav Petkov
2013-04-16 16:18 ` Borislav Petkov
2013-04-17 0:38 ` Sasha Levin [this message]
2013-04-17 7:50 ` Borislav Petkov
2013-04-17 23:25 ` Marcelo Tosatti
2013-04-18 9:46 ` Borislav Petkov
2013-04-18 9:55 ` Geert Uytterhoeven
2013-04-18 10:18 ` Borislav Petkov
2013-04-18 13:36 ` Marcelo Tosatti
2013-04-19 10:35 ` Borislav Petkov
2013-04-26 0:05 ` [PATCH -v2] x86: Add a Kconfig shortcut for kvm guest kernel Borislav Petkov
2013-04-26 6:42 ` Ingo Molnar
2013-04-26 9:51 ` [PATCH -v2.1] " Borislav Petkov
2013-04-30 16:49 ` [tip:x86/urgent] x86/kconfig: Add a Kconfig shortcut for building working KVM guest kernels tip-bot for Borislav Petkov
2013-05-01 19:53 ` David Rientjes
2013-05-01 20:35 ` Borislav Petkov
2013-05-01 21:00 ` David Rientjes
2013-05-01 21:10 ` Borislav Petkov
2013-05-01 21:30 ` David Rientjes
2013-05-01 21:56 ` Borislav Petkov
2013-05-01 22:09 ` David Rientjes
2013-05-01 22:28 ` Borislav Petkov
2013-05-01 22:37 ` David Rientjes
2013-05-01 23:02 ` Borislav Petkov
2013-05-01 23:04 ` H. Peter Anvin
2013-05-01 23:09 ` Borislav Petkov
2013-05-01 23:16 ` H. Peter Anvin
2013-05-01 23:23 ` Borislav Petkov
2013-05-02 7:06 ` Ingo Molnar
2013-05-02 17:31 ` H. Peter Anvin
2013-05-02 19:43 ` Ingo Molnar
2013-05-02 19:48 ` Borislav Petkov
2013-05-01 23:16 ` David Rientjes
2013-05-01 23:35 ` Borislav Petkov
2013-05-02 0:07 ` David Rientjes
2013-05-02 7:08 ` Ingo Molnar
2013-05-02 7:16 ` David Rientjes
2013-05-01 13:19 ` [PATCH -v2.1] x86: Add a Kconfig shortcut for kvm guest kernel Marcelo Tosatti
2013-05-01 23:21 ` Borislav Petkov
2013-05-02 17:23 ` [tip:x86/urgent] x86/kconfig: Add a Kconfig shortcut for building working KVM guest kernels tip-bot for Borislav Petkov
2013-05-02 18:06 ` David Rientjes
2013-05-02 18:07 ` H. Peter Anvin
2013-05-02 18:19 ` David Rientjes
2013-05-02 19:45 ` Ingo Molnar
2013-05-02 20:07 ` Borislav Petkov
2013-05-03 14:29 ` Borislav Petkov
2013-05-03 14:54 ` Randy Dunlap
2013-05-03 15:08 ` Borislav Petkov
2013-05-03 15:06 ` H. Peter Anvin
2013-05-03 15:10 ` Michal Marek
2013-05-03 15:31 ` Borislav Petkov
2013-05-03 16:53 ` David Rientjes
2013-05-03 17:10 ` H. Peter Anvin
2013-05-03 17:19 ` David Rientjes
2013-05-03 19:09 ` H. Peter Anvin
2013-05-03 23:36 ` Borislav Petkov
2013-05-22 14:46 ` [PATCH -v2] x86: Add a kvm config file Borislav Petkov
2013-05-22 17:55 ` Pekka Enberg
2013-05-28 13:39 ` [tip:x86/platform] x86, platform, kvm, kconfig: Turn existing .config's into KVM-capable configs tip-bot for Borislav Petkov
2013-06-21 8:04 ` [PATCH] x86/platform: Add kvmconfig to the phony targets Borislav Petkov
2013-06-23 11:02 ` [tip:x86/platform] " tip-bot for Borislav Petkov
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=516DEF20.9060303@gmail.com \
--to=levinsasha928@gmail.com \
--cc=bp@alien8.de \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=penberg@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;
as well as URLs for NNTP newsgroup(s).