From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ed Swierk <eswierk@aristanetworks.com>
Cc: Ingo Molnar <mingo@elte.hu>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, lenb@kernel.org,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [RFC] [PATCH] PCI mmconfig without ACPI
Date: Tue, 5 May 2009 10:57:44 -0700 [thread overview]
Message-ID: <20090505105744.4268e341@hobbes> (raw)
In-Reply-To: <1234812741.28801.4.camel@localhost.localdomain>
On Mon, 16 Feb 2009 11:32:21 -0800
Ed Swierk <eswierk@aristanetworks.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
next prev parent reply other threads:[~2009-05-05 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 16:59 [RFC] [PATCH] PCI mmconfig without ACPI Ed Swierk
2009-02-04 18:17 ` Ingo Molnar
2009-02-13 20:40 ` Jesse Barnes
2009-02-16 19:32 ` Ed Swierk
2009-05-05 17:57 ` Jesse Barnes [this message]
2009-05-05 20:09 ` Ed Swierk
2009-05-05 20:32 ` Jesse Barnes
2009-02-21 5:55 ` Len Brown
2009-02-22 9:22 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090505105744.4268e341@hobbes \
--to=jbarnes@virtuousgeek.org \
--cc=eswierk@aristanetworks.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox