From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Allen Kay <allen.m.kay@intel.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
matthew@wil.cx, chrisw@sous-sol.org, jeremy@goop.org,
donald.d.dugger@intel.com, joerg.roedel@amd.com,
dwmw2@infradead.org, iommu@lists.linux-foundation.org
Subject: Re: [PATCH] pci: add pci_request_acs
Date: Fri, 4 Dec 2009 16:19:47 -0800 [thread overview]
Message-ID: <20091204161947.67e18073@jbarnes-piketon> (raw)
In-Reply-To: <20091204201521.GJ21174@sequoia.sous-sol.org>
On Fri, 4 Dec 2009 12:15:21 -0800
Chris Wright <chrisw@sous-sol.org> wrote:
> Commit ae21ee65e8bc228416bbcc8a1da01c56a847a60c "PCI: acs p2p upsteram
> forwarding enabling" doesn't actually enable ACS.
>
> Add a function to pci core to allow an IOMMU to request that ACS
> be enabled. The existing mechanism of using iommu_found() in the pci
> core to know when ACS should be enabled doesn't actually work due to
> initialization order; iommu has only been detected not initialized.
>
> Have Intel and AMD IOMMUs request ACS, and Xen does as well during
> early init of dom0.
>
> Cc: Allen Kay <allen.m.kay@intel.com>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Jeremy Fitzhardinge <jeremy@goop.org>
> Cc: Joerg Roedel <joerg.roedel@amd.com>
> Signed-off-by: Chris Wright <chrisw@sous-sol.org>
Applied this one, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-12-05 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 17:27 [ACS PATCH v5 1/2] acs p2p upsteram forwarding enabling Allen Kay
2009-12-04 19:17 ` Chris Wright
2009-12-04 20:15 ` [PATCH] pci: add pci_request_acs Chris Wright
2009-12-05 0:19 ` Jesse Barnes [this message]
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=20091204161947.67e18073@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=allen.m.kay@intel.com \
--cc=chrisw@sous-sol.org \
--cc=donald.d.dugger@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jeremy@goop.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/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
all inboxes | Powered by JetHome®