linux-kernel - Re: PCI MMCONFIG aperture size

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060822145802.GR16573@google.com>
Date:	Tue, 22 Aug 2006 07:58:02 -0700
From:	Tim Hockin <thockin@...gle.com>
To:	Andi Kleen <ak@...e.de>
Cc:	matthew@....cx, greg@...ah.com,
	Linux Kernel mailing list <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...gle.com>
Subject: Re: PCI MMCONFIG aperture size

On Tue, Aug 22, 2006 at 09:55:31AM +0200, Andi Kleen wrote:
> 
> > This says to me that (as long as the MCFG table has an End Bus Number of
> > 31) a 32 MB decode area (32 MB aligned, too) is valid.
> > 
> > Would something like the below patch be accepted?  It makes my system
> > work...
> 
> I already got a patch to remove the complete e820 validation code because
> it broke far more than it fixed. That should fix your problem too.

Great!  Coming in 2.6.18?

> > Also, why are we forcing 32 bit base addresses?  ACPI defines it to be a
> > 64 bit base...
> 
> Where do you think we do that?

Looking at 2.6.17, we always have u32 base_address and u32
base_reserved.  base_address is the only one ever referenced, that I can
see.  I guess I should grab 2.6.18 pre-releases and recheck.

Thanks
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/