linux-kernel - Re: [PATCH] x86/PCI: parse additional host bridge window resource types

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]

Message-ID: <20100422161749.5e8af128@virtuousgeek.org>
Date:	Thu, 22 Apr 2010 16:17:49 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	linux-pci@...r.kernel.org, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org, Thomas Renninger <trenn@...e.de>
Subject: Re: [PATCH] x86/PCI: parse additional host bridge window resource
 types

On Tue, 20 Apr 2010 13:52:41 -0600
Bjorn Helgaas <bjorn.helgaas@...com> wrote:

> 
> This adds support for Memory24, Memory32, and Memory32Fixed descriptors in
> PCI host bridge _CRS.
> 
> I experimentally determined that Windows (2008 R2) accepts these descriptors
> and treats them as windows that are forwarded to the PCI bus, e.g., if
> it finds any PCI devices with BARs outside the windows, it moves them into
> the windows.
> 
> I don't know whether any machines actually use these descriptors in PCI
> host bridge _CRS methods, but if any exist and they're new enough that we
> automatically turn on "pci=use_crs", they will work with Windows but not
> with Linux.
> 
> Here are the details: https://bugzilla.kernel.org/show_bug.cgi?id=15817
> 
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@...com>
> ---

Applied to for-linus, 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/