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: <86802c440807181054p422a77bdv901ebdc44a8d1b43@mail.gmail.com>
Date:	Fri, 18 Jul 2008 10:54:28 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>, jbarnes@...tuousgeek.org,
	"Jack Howarth" <howarth@...mo.msbb.uc.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf

On Fri, Jul 18, 2008 at 10:49 AM, H. Peter Anvin <hpa@...or.com> wrote:
> Yinghai Lu wrote:
>>
>> On Fri, Jul 18, 2008 at 10:44 AM, H. Peter Anvin <hpa@...or.com> wrote:
>>>
>>> Yinghai Lu wrote:
>>>>
>>>> change the mconf bus range from [0,0xff] to to [0, 0x3f]
>>>> to match range [0xf0000000, 0xf4000000) in e820 tables.
>>>>
>>>> Signed-off-by: Yinghai Lu <yhlu.kernel@...il.com>
>>>> Tested-by: Jack Howarth <howarth@...mo.msbb.uc.edu>
>>>
>>> Why is this hard-coded instead of discovered dynamically?
>>
>> you mean according to the range reserved in e820 to find out bus range
>> that should be used for mmconf?
>
> That would make sense, since you're truncating the mmconf range based on
> some arbitrary limit.  Even better would be to query the hardware register
> which is responsible for the truncation.

OK

will rework pci_mmcfg_reject_broken to
reduce size and check with is_acpi_reserved/e820_mapped to update end_bus_number

YH
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ