linux-kernel - Re: [RFC] [PATCH] PCI mmconfig without ACPI

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]

Date:	Tue, 5 May 2009 10:57:44 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Ed Swierk <eswierk@...stanetworks.com>
Cc:	Ingo Molnar <mingo@...e.hu>, tglx@...utronix.de, mingo@...hat.com,
	hpa@...or.com, linux-kernel@...r.kernel.org, lenb@...nel.org,
	linux-acpi@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [RFC] [PATCH] PCI mmconfig without ACPI

On Mon, 16 Feb 2009 11:32:21 -0800
Ed Swierk <eswierk@...stanetworks.com> wrote:

> Here's another attempt at decoupling the setup of memory-mapped PCI
> configuration space from ACPI.  I implemented your suggestions for
> moving the ACPI-specific code to a separate file.  I left the
> definition of struct acpi_mcfg_allocation alone, and created a new
> struct pci_mcfg_allocation.  The former is now used only for parsing
> the actual ACPI MCFG table, while the latter is used to store
> information about mmcfg regions regardless of where they came from.
> 
> (This is still an RFC; the code is pretty much untested.)
> 

I'm still a bit dubious about this; does it solve a real issue?  Or
just remove the ACPI dependency for its own sake?

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