[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2b8697b5-3bbc-4ca1-808c-0adf6e6099ff@email.android.com>
Date: Fri, 03 May 2013 08:06:28 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Borislav Petkov <bp@...en8.de>,
Randy Dunlap <rdunlap@...radead.org>
CC: Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
David Rientjes <rientjes@...gle.com>,
linux-kernel@...r.kernel.org, penberg@...nel.org,
levinsasha928@...il.com, mtosatti@...hat.com, tglx@...utronix.de,
bp@...e.de, fengguang.wu@...el.com,
linux-tip-commits@...r.kernel.org, Michal Marek <mmarek@...e.cz>
Subject: Re: [tip:x86/urgent] x86/kconfig: Add a Kconfig shortcut for building working KVM guest kernels
We can put a config file upstream, too.
Borislav Petkov <bp@...en8.de> wrote:
>On Fri, May 03, 2013 at 07:54:36AM -0700, Randy Dunlap wrote:
>> Could you alternately have a kvm_guest.config that should always work
>> for you?
>
>I could, and I do. The idea, however, is to have this option upstream
>so that people don't have to go search for every relevant option for
>running the kernel a kvm guest.
>
>Which reminds me: Pekka had a 'make kvmconfig' functionality in
>the kvmtool too. Which, TBH, is even better than having a Kconfig
>option with a bunch of selects. So, come to think of it, after all
>the controversy with such an option, having a 'make kvmconfig' do
>scripts/config -e <option> where <option> is in that list we select
>would be much better.
>
>This won't break randconfigs at all, btw. :-)
>
>Michal?
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
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