public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Pan, Jacob jun" <jacob.jun.pan@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags
Date: Fri, 26 Jun 2009 14:51:11 +0200	[thread overview]
Message-ID: <20090626125111.GA11575@elte.hu> (raw)
In-Reply-To: <20090626133318.5b8de81b@lxorguk.ukuu.org.uk>


* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > That's a pretty bogus claim - on x86 a bootloader generally 
> > knows very little about 'what it is running on'. We do most of 
> > the enumeration in early platform code and retrieve information 
> > via standard BIOS interfaces.
> 
> Stop thinking about existing x86 PC systems running grub for a 
> bit. [...]

You are talking to the wrong person then i guess, i'm not going to 
ignore 95% of our installed base. ;-)

We will gladly take clean x86 patches that abstract away lowlevel 
details of x86 platforms, and have been taking them and have been 
writing them for a long time. If this patch-set can shape itself in 
such a way (as i requested), without hindering the common case, it 
is certainly welcome.

Generally, if you try to deviate from de facto standards then you 
better show a very good reason and much cleaner code than this 
deficient v1 patch-set.

Yes, platform abstraction is good if it's necessary and if it's done 
cleanly, and x86 certainly has a few things to learn in that area 
(it still has way too much platform spaghetti), but i'm not 
convinced here at all that it's necessary, and it's certainly not 
cleanly done at all. As i pointed it out in my review in detail, 
it's full of 'if (feature)' crap invading core platform code for 
example.

There's good examples as well, from the same quarters of Intel: for 
example i reviewed and commented on the related SFI patches a few 
days ago, and they looked distinctly clean and desirable.

Thanks,

	Ingo

  reply	other threads:[~2009-06-26 12:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  0:14 [PATCH 3/9] x86/moorestown: add moorestown platform flags Pan, Jacob jun
2009-06-26  7:19 ` Ingo Molnar
2009-06-26  9:13   ` Alan Cox
2009-06-26  9:38     ` Ingo Molnar
2009-06-26 10:16       ` Alan Cox
2009-06-26 11:04         ` Ingo Molnar
2009-06-26 11:56           ` Alan Cox
2009-06-26 12:22             ` Ingo Molnar
2009-06-26 12:33               ` Alan Cox
2009-06-26 12:51                 ` Ingo Molnar [this message]
2009-06-26 13:34                   ` Alan Cox
2009-06-26 14:44                     ` Ingo Molnar
2009-06-26 14:29                 ` Ingo Molnar
2009-06-26 16:32                   ` Thomas Gleixner
2009-06-26 16:54                     ` Jesse Barnes
2009-06-30  6:35                       ` Pavel Machek
2009-07-01 17:25                         ` Jesse Barnes
2009-07-01 20:48                           ` Ingo Molnar
2009-06-26 15:00           ` Ingo Molnar
2009-06-26 16:51   ` Jesse Barnes
2009-06-26 18:45     ` Ingo Molnar

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=20090626125111.GA11575@elte.hu \
    --to=mingo@elte.hu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@linux.intel.com \
    --cc=jacob.jun.pan@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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