From: "H. Peter Anvin" <hpa@zytor.com>
To: akataria@vmware.com
Cc: "david@lang.hm" <david@lang.hm>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: move vmware to hypervisor
Date: Thu, 26 Mar 2009 17:10:02 -0700 [thread overview]
Message-ID: <49CC195A.8060100@zytor.com> (raw)
In-Reply-To: <1238085621.21971.3.camel@alok-dev1>
Alok Kataria wrote:
>>>>
>>> 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
>
It sounds to me like the kind of things that gets buried under
CONFIG_EMBEDDED for the people who are absolutely paranoid (sometimes
even for very good reasons) about every additional byte in the kernel.
-hpa
next prev parent reply other threads:[~2009-03-27 0:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 9:19 [PATCH -tip] x86: move vmware to hypervisor Jaswinder Singh Rajput
2009-03-17 9:39 ` Ingo Molnar
2009-03-17 9:48 ` Jaswinder Singh Rajput
2009-03-17 15:50 ` H. Peter Anvin
2009-03-25 5:29 ` Jaswinder Singh Rajput
2009-03-25 12:59 ` Ingo Molnar
2009-03-25 16:52 ` Alok Kataria
2009-03-25 17:07 ` Jaswinder Singh Rajput
2009-03-25 17:24 ` Alok Kataria
2009-03-25 17:38 ` Jaswinder Singh Rajput
2009-03-25 18:18 ` Alok Kataria
2009-03-26 7:10 ` david
2009-03-26 16:40 ` Alok Kataria
2009-03-27 0:10 ` H. Peter Anvin [this message]
2009-03-25 13:38 ` Mark Lord
2009-03-17 17:28 ` Alok Kataria
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49CC195A.8060100@zytor.com \
--to=hpa@zytor.com \
--cc=akataria@vmware.com \
--cc=david@lang.hm \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox