[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1238085621.21971.3.camel@alok-dev1>
Date: Thu, 26 Mar 2009 09:40:21 -0700
From: Alok Kataria <akataria@...are.com>
To: "david@...g.hm" <david@...g.hm>
Cc: Jaswinder Singh Rajput <jaswinder@...nel.org>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
x86 maintainers <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip] x86: move vmware to hypervisor
On Thu, 2009-03-26 at 00:10 -0700, david@...g.hm wrote:
> On Wed, 25 Mar 2009, Alok Kataria wrote:
>
> > On Wed, 2009-03-25 at 10:38 -0700, Jaswinder Singh Rajput wrote:
> >> I am not saying we should not hide this behind a config at all. The
> >> point is there is nothing that we save by adding a new config, so what's
> >> the point at all. If you can give me a solid reason like, say, you save
> >> 1% code space with this config option, or 'n' sec in the boottime, I am
> >> all ears for such an argument.
> >>
> >>
> >
> > So, if there are any tangible benefits with doing this I am ok with it,
> > but your current argument about "Freedom to user" doesn't sound too
> > compelling.
>
> isn't it the other way around? you are adding this in, it should be up to
> you to show that it
>
> A. has no impact
>
> B. has a small enough impact that it's not worth the config option
This is what exactly I have mentioned in a mail earlier in this thread.
http://lkml.org/lkml/2009/3/25/333
Alok
--
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