From: Joerg Roedel <joro@8bytes.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: iommu@lists.linux-foundation.org, dwmw2@infradead.org,
linux-pci@vger.kernel.org, ddutile@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu: amd/intel: Remove multifunction assumption around grouping
Date: Thu, 20 Jun 2013 17:22:48 +0200 [thread overview]
Message-ID: <20130620152248.GF3589@8bytes.org> (raw)
In-Reply-To: <20130530183855.14612.15585.stgit@bling.home>
On Thu, May 30, 2013 at 12:39:18PM -0600, Alex Williamson wrote:
> If a device is multifunction and does not have ACS enabled then we
> assume that the entire package lacks ACS and use function 0 as the
> base of the group. The PCIe spec however states that components are
> permitted to implement ACS on some, none, or all of their applicable
> functions. It's therefore conceivable that function 0 may be fully
> independent and support ACS while other functions do not. Instead
> use the lowest function of the slot that does not have ACS enabled
> as the base of the group. This may be the current device, which is
> intentional. So long as we use a consistent algorithm, all the
> non-ACS functions will be grouped together and ACS functions will
> get separate groups.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
> drivers/iommu/amd_iommu.c | 25 +++++++++++++++++++------
> drivers/iommu/intel-iommu.c | 25 +++++++++++++++++++------
Didn't really fit into any of my existing branches. Applied it to
x86/vt-d because it is probably not worth creating a new x86-specific
branch just for this patch.
Thanks,
Joerg
prev parent reply other threads:[~2013-06-20 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 18:39 [PATCH] iommu: amd/intel: Remove multifunction assumption around grouping Alex Williamson
2013-06-03 7:28 ` Sethi Varun-B16395
[not found] ` <C5ECD7A89D1DC44195F34B25E172658D56A9F4-RL0Hj/+nBVDYdknt8GnhQq4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2013-06-03 15:10 ` Alex Williamson
2013-06-20 15:22 ` Joerg Roedel [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=20130620152248.GF3589@8bytes.org \
--to=joro@8bytes.org \
--cc=alex.williamson@redhat.com \
--cc=ddutile@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).