[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1402391628.29980.15.camel@kazak.uk.xensource.com>
Date: Tue, 10 Jun 2014 10:13:48 +0100
From: Ian Campbell <Ian.Campbell@...rix.com>
To: Borislav Petkov <bp@...e.de>
CC: "Luis R. Rodriguez" <mcgrof@...e.com>,
"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
<tglx@...utronix.de>, <mingo@...hat.com>, <hpa@...or.com>,
<x86@...nel.org>, <linux-kernel@...r.kernel.org>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Michal Marek <mmarek@...e.cz>,
Randy Dunlap <rdunlap@...radead.org>,
<levinsasha928@...il.com>, <mtosatti@...hat.com>,
<fengguang.wu@...el.com>, "David Vrabel" <david.vrabel@...rix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
<xen-devel@...ts.xenproject.org>
Subject: Re: [PATCH 3/3] x86, platform, kconfig: add virtconfig defconfig
helper
On Tue, 2014-06-10 at 11:01 +0200, Borislav Petkov wrote:
> On Tue, Jun 10, 2014 at 09:35:39AM +0100, Ian Campbell wrote:
> > Actually what I meant was to *replace* kvmconfig with virtconfig and
> > then add the Xen stuff to it, i.e. to have a single thing to maintain
> > for all virt platforms, rather than end up with all 3 options.
> >
> > I think the overhead of having some Xen stuff enabled in .config when
> > running on KVM and vice versa is small.
>
> Hmm, no. I'm running my kvm-enabled configs on baremetal too and I
> wouldn't want any overhead at all. So kvmconfig and xenconfig should be
> separate targets with separate config files please.
NB the overhead I meant was a few kbs of .text and modules, not runtime
overhead.
Ian.
--
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