linux-kernel - Re: [PATCH] pci/x86: try to detect host_bridge pci_cfg

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] [day] [month] [year] [list]

Date:	Thu, 19 Mar 2009 19:02:16 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>, Matthew Wilcox <matthew@....cx>,
	Greg KH <gregkh@...e.de>, Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-pci@...r.kernel.org, stable@...nel.org
Subject: Re: [PATCH] pci/x86: try to detect host_bridge pci_cfg_space -v2

On Sun, 08 Mar 2009 21:35:37 -0700
Yinghai Lu <yinghai@...nel.org> wrote:

> 
> Impact: get correct pci_cfg_size for host_bridge
> 
> more host bridges support 4k cfg, so check them directy instead of
> quirks.
> 
> only need to do this extra check for host_bridge at this point,
> because only host bridges are known to have extended address space
> without also having a PCI-X/PCI-E caps.
> other devices we could still do quirks for them if there is any.
> 
> also remove the quirks for AMD host bridges with family 10h and 11h
> that is not needed any more
> 
> with this patch, we can get correct pci cfg size of new Intel
> CPUs/IOHs with host bridges
> 
> v2: updated commit log.

Applied to my linux-next branch, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/