[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130503153134.GD3433@pd.tnic>
Date: Fri, 3 May 2013 17:31:34 +0200
From: Borislav Petkov <bp@...en8.de>
To: Michal Marek <mmarek@...e.cz>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
David Rientjes <rientjes@...gle.com>, hpa@...or.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
Subject: Re: [tip:x86/urgent] x86/kconfig: Add a Kconfig shortcut for
building working KVM guest kernels
On Fri, May 03, 2013 at 05:10:15PM +0200, Michal Marek wrote:
> You still risk that you miss some new dependency, but for a normal
> configs as a base, this won't be an issue in most cases. Whether this is
> implemented as a series of scripts/config calls or if there is a
> kvm_guest.config does not matter much, as long as randconfig does not
> see it ;).
Yep, I think we can do something along the lines of what hpa suggested:
* put a kvm_guest.config in arch/x86/configs/
* teach scripts/config/ to parse it and do set_var() for each line in
there.
* yes "" | make oldconfig - because we want to use the current config
as a base.
I think this is the easiest and cleanest of them all.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
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