lkml.org 
[lkml]   [2007]   [Dec]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue


On Sat, 22 Dec 2007, Jeff Garzik wrote:
>
> Jeff Garzik wrote:
> > Maybe that day will never come, but it is nonetheless quite possible without
> > today's PCI Express spec for this to happen.
>
> er, s/without/within/

You're talking specs. I'm talking machines.

I agree with you 100% that as per specs, you need to support MMCONFIG,
because anything can happen.

As per *reality*, though, machines sold today simply don't need it. So
there is no upside, and there is definitely downside.

I want to limit that downside. Right now, the easiest way to limit it
seems to be to say that those (very very few) drivers that actually care
could enable it. That way, we automatically limit it to only those
machines that have hardware that cares.

And yes, if you want the capability following to notice automatically when
capabilities really do go into the 0x100+ range, that's fine. I suspect
that there aren't really very many cards that do that (because they
wouldn't work with WinXP etc), so I doubt it will actually enable MMCONFIG
for any noticeable amount of hardware sold today. Which is exactly what I
want. I do *not* want to enable MMCONFIG unless it is shown to actually be
needed.

And no, "specs" do not show it is needed. MMCONFIG is needed depending on
the actual *hardware* the kernel runs on, not based on some external
specs.

Linus


\
 
 \ /
  Last update: 2007-12-23 06:13    [W:0.111 / U:1.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site