On Fri, Jan 11, 2008 at 12:27:06PM -0800, Linus Torvalds wrote:
quoted text
> On Fri, 11 Jan 2008, Matthew Wilcox wrote:
> > 
> > Ivan's patch doesn't start enabling MMCONFIG in more places than we
> > currently do.  It makes us use conf1 accesses for all accesses below
> > 256 bytes.  That fixes all known problems to date.
> 
> .. and I agree with that patch. But there will be people who try to access 
> extended space by mistake, and they'll have a hard-locked machine or 
> something.

But they can't.  We limit the size they can access to 256 bytes, unless
the kernel probed address 256 and it worked.

quoted text
> > The armour plating that already exists -- pci=nommconf.
> 
> No. It needs to be automatic, OR THE OTHER WAY AROUND.
> 
> Ie we disable the unsafe feature on purpose, and then force people who 
> access it to do so *consciously*.

I'd be fine with making mmconfig off by default.  Make people pass
pci=mmconf to activate it.

quoted text
> Extended config space is different, for chissake! It's not even like it's 
> just a bigger normal config space where normal config accesses just 
> overflow into it. It really does have different rules etc.

Yes, but it's also important to enable some of the PCIe features.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/