From: Chris Wright <chrisw@sous-sol.org>
To: Allen Kay <allen.m.kay@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
jbarnes@virtuousgeek.org, matthew@wil.cx, chris@sous-sol.org,
jeremy@goop.org
Subject: Re: [PATCH ACS v4 1/1] Enabling PCI ACS P2P upstream forwarding
Date: Tue, 6 Oct 2009 16:42:08 -0700 [thread overview]
Message-ID: <20091006234208.GB23140@sequoia.sous-sol.org> (raw)
In-Reply-To: <1254861226-18376-1-git-send-email-allen.m.kay@intel.com>
* Allen Kay (allen.m.kay@intel.com) wrote:
> +#ifdef CONFIG_DMAR
> +extern int iommu_detected;
> +#endif
This should not be needed.
> +
> +#ifdef CONFIG_XEN
> +extern int xen_domain_type;
> +#endif
Nor this (there's already a check for is dom0 called xen_initial_domain(),
but unclear it's relevant yet for this patch).
> +
> + /* Enable ACS P2P upstream forwarding if HW iommu is detected */
> + if (iommu_detected)
I think you'd want iommu_found() instead. To avoid, e.g., GART
triggering this one.
> + pci_enable_acs(dev);
> +
> +#ifdef CONFIG_XEN
> + /* HW iommu is not visible in xen dom0 */
> + if (xen_domain_type)
> + pci_enable_acs(dev);
could do this (xen_initial_domain()) above, but it's only relevant for
dom0 (so not needed yet?), and really seems to like it should be done by hv.
thanks,
-chris
next prev parent reply other threads:[~2009-10-06 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 20:33 Allen Kay
2009-10-06 21:37 ` Jeremy Fitzhardinge
2009-10-06 21:47 ` Kay, Allen M
2009-10-06 22:01 ` Kay, Allen M
2009-10-06 22:05 ` Jeremy Fitzhardinge
2009-10-06 22:37 ` Kay, Allen M
2009-10-06 22:11 ` [PATCH] xen: move Xen-testing predicates to common header Jeremy Fitzhardinge
2009-10-06 23:42 ` Chris Wright [this message]
2009-10-06 23:58 ` [PATCH ACS v4 1/1] Enabling PCI ACS P2P upstream forwarding Chris Wright
2009-10-07 0:17 ` Kay, Allen M
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=20091006234208.GB23140@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=allen.m.kay@intel.com \
--cc=chris@sous-sol.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jeremy@goop.org \
--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®