[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0903260008050.13440@asgard.lang.hm>
Date: Thu, 26 Mar 2009 00:10:23 -0700 (PDT)
From: david@...g.hm
To: Alok Kataria <akataria@...are.com>
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 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
C. has an impact, but is so valuble that it should be on for all systems
(even those that are absolutly not suitable for running virtual machines)
David Lang
--
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