From: Ingo Molnar <mingo@elte.hu>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: "Pan, Jacob jun" <jacob.jun.pan@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 2/9] x86: introduce a set of platform feature flags
Date: Fri, 26 Jun 2009 21:13:45 +0200 [thread overview]
Message-ID: <20090626191345.GA3061@elte.hu> (raw)
In-Reply-To: <4A451BA4.4090000@linux.intel.com>
* H. Peter Anvin <hpa@linux.intel.com> wrote:
> Ingo Molnar wrote:
> >
> > Btw., this enumeration of basic PC features isnt bad in itself - and
> > if there's a boot-flag based detection method (like on MRST) then
> > this can convey a 'should this platform driver attempt to
> > initialize' information to the driver, and rather cleanly so.
> >
>
> That is the whole point of this, yes. [...]
Except that about half of all the actual uses of platform_has() are
all but related to the "should this driver initialize" question ;-)
They are more used as "fudge platform code a bit here and there to
meet the limited constraints of the platform".
And that kind of fudging is a problem, obviously.
> [...] Furthermore, it is expected that we *also* would be able to
> set platform flags based on early probes.
Yeah.
> > But there's bad uses of this as well, and those bad uses seem to
> > dominate this patch-set.
>
> Not entirely surprising, since this stuff is more or less randomly
> sprinkled through the existing code. We have a huge bunch of
> legacy code and yes, it needs cleanup.
>
> This is a huge opportunity, of course, but it's going to be a lot
> of work. A lot of this is likely to overlap directly with the
> needs of Xen, too.
Correct.
Ingo
next prev parent reply other threads:[~2009-06-26 19:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 0:14 [PATCH 2/9] x86: introduce a set of platform feature flags Pan, Jacob jun
2009-06-26 7:22 ` Ingo Molnar
2009-06-26 9:14 ` Alan Cox
2009-06-26 9:45 ` Ingo Molnar
2009-06-26 10:17 ` Alan Cox
2009-06-26 10:47 ` Ingo Molnar
2009-06-26 11:41 ` Alan Cox
2009-06-26 15:47 ` Ingo Molnar
2009-06-26 19:04 ` H. Peter Anvin
2009-06-26 19:13 ` Ingo Molnar [this message]
2009-06-30 6:32 ` Pavel Machek
2009-07-02 23:09 ` Pan, Jacob jun
2009-07-02 23:25 ` H. Peter Anvin
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=20090626191345.GA3061@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