public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH -mm] 0/2: PCI MMCONFIG-related updates
@ 2007-05-30  4:01 Robert Hancock
  2007-05-30 15:21 ` Jesse Barnes
  0 siblings, 1 reply; 3+ messages in thread
From: Robert Hancock @ 2007-05-30  4:01 UTC (permalink / raw)
  To: linux-kernel, Andrew Morton; +Cc: Jesse Barnes, Linus Torvalds

These two patches implement some changes in behavior related to PCI
MMCONFIG configuration space access. One changes the way in which we
validate the MCFG table provided by the BIOS by checking it against
ACPI motherboard resources instead of the E820 table. The BIOS is not
required to reserve this area in the E820 table, so checking that
results in MMCONFIG being unnecessarily disabled on some machines.

Some Intel chipsets where MMCONFIG was being disabled previously
(but won't be with the first patch) had problems, not due to the
MCFG table being broken, but because the access was hosed by the way
in which we do PCI BAR sizing. The second patch fixes this problem.

This is requested for inclusion in the -mm tree for testing.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH -mm] 0/2: PCI MMCONFIG-related updates
  2007-05-30  4:01 [PATCH -mm] 0/2: PCI MMCONFIG-related updates Robert Hancock
@ 2007-05-30 15:21 ` Jesse Barnes
  2007-05-30 23:31   ` Robert Hancock
  0 siblings, 1 reply; 3+ messages in thread
From: Jesse Barnes @ 2007-05-30 15:21 UTC (permalink / raw)
  To: Robert Hancock; +Cc: linux-kernel, Andrew Morton, Linus Torvalds

On Tuesday, May 29, 2007 9:01:22 Robert Hancock wrote:
> These two patches implement some changes in behavior related to PCI
> MMCONFIG configuration space access. One changes the way in which we
> validate the MCFG table provided by the BIOS by checking it against
> ACPI motherboard resources instead of the E820 table. The BIOS is not
> required to reserve this area in the E820 table, so checking that
> results in MMCONFIG being unnecessarily disabled on some machines.
>
> Some Intel chipsets where MMCONFIG was being disabled previously
> (but won't be with the first patch) had problems, not due to the
> MCFG table being broken, but because the access was hosed by the way
> in which we do PCI BAR sizing. The second patch fixes this problem.
>
> This is requested for inclusion in the -mm tree for testing.

Robert, should we also pull in the 915 and 965 chipset specific register 
poking code?  It might be a good sanity check against ACPI (i.e. if ACPI and 
the actual register window disagree, we can assume the BIOS is broken and 
MCFG is not safe to use).  If so, I'll update and repost them against your 
patchset.

Thanks,
Jesse

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH -mm] 0/2: PCI MMCONFIG-related updates
  2007-05-30 15:21 ` Jesse Barnes
@ 2007-05-30 23:31   ` Robert Hancock
  0 siblings, 0 replies; 3+ messages in thread
From: Robert Hancock @ 2007-05-30 23:31 UTC (permalink / raw)
  To: Jesse Barnes; +Cc: linux-kernel, Andrew Morton, Linus Torvalds

Jesse Barnes wrote:
> On Tuesday, May 29, 2007 9:01:22 Robert Hancock wrote:
>> These two patches implement some changes in behavior related to PCI
>> MMCONFIG configuration space access. One changes the way in which we
>> validate the MCFG table provided by the BIOS by checking it against
>> ACPI motherboard resources instead of the E820 table. The BIOS is not
>> required to reserve this area in the E820 table, so checking that
>> results in MMCONFIG being unnecessarily disabled on some machines.
>>
>> Some Intel chipsets where MMCONFIG was being disabled previously
>> (but won't be with the first patch) had problems, not due to the
>> MCFG table being broken, but because the access was hosed by the way
>> in which we do PCI BAR sizing. The second patch fixes this problem.
>>
>> This is requested for inclusion in the -mm tree for testing.
> 
> Robert, should we also pull in the 915 and 965 chipset specific register 
> poking code?  It might be a good sanity check against ACPI (i.e. if ACPI and 
> the actual register window disagree, we can assume the BIOS is broken and 
> MCFG is not safe to use).  If so, I'll update and repost them against your 
> patchset.

Probably not a bad idea..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-05-30 23:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-30  4:01 [PATCH -mm] 0/2: PCI MMCONFIG-related updates Robert Hancock
2007-05-30 15:21 ` Jesse Barnes
2007-05-30 23:31   ` Robert Hancock

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox