From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Wei Chen <Wei.Chen-5wv7dgnIgG8@public.gmane.org>
Cc: steve.capper-5wv7dgnIgG8@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] iommu/arm-smmu: request pcie devices to enable ACS
Date: Mon, 13 Jun 2016 13:45:32 +0100 [thread overview]
Message-ID: <20160613124531.GE1605@arm.com> (raw)
In-Reply-To: <1465809617-13003-1-git-send-email-Wei.Chen-5wv7dgnIgG8@public.gmane.org>
On Mon, Jun 13, 2016 at 05:20:17PM +0800, Wei Chen wrote:
> The PCIe ACS capability will affect the layout of iommu groups.
> Generally speaking, if the path from root port to the PCIe device
> is ACS enabled, the iommu will create a single iommu group for this
> PCIe device. If all PCIe devices on the path are ACS enabled then
> Linux can determine this path is ACS enabled.
>
> Linux use two PCIe configuration registers to determine the ACS
> status of PCIe devices:
> ACS Capability Register and ACS Control Register.
>
> The first register is used to check the implementation of ACS function
> of a PCIe device, the second register is used to check the enable status
> of ACS function. If one PCIe device has implemented and enabled the ACS
> function then Linux will determine this PCIe device enabled ACS.
>
> From the Chapter:6.12 of PCI Express Base Specification Revision 3.1a,
> we can find that when a PCIe device implements ACS function, the enable
> status is set to disabled by default and can be enabled by ACS-aware
> software.
>
> ACS will affect the iommu groups topology, so, the iommu driver is
> ACS-aware software. This patch adds a call to pci_request_acs() to the
> arm-smmu driver to enable the ACS function in PCIe devices that support
> it.
>
> Signed-off-by: Wei Chen <Wei.Chen-5wv7dgnIgG8@public.gmane.org>
> ---
> drivers/iommu/arm-smmu-v3.c | 2 ++
> drivers/iommu/arm-smmu.c | 4 +++-
> 2 files changed, 5 insertions(+), 1 deletion(-)
Thanks, queued for 4.8 w/ Robin and Eric's reviewed-by tags and the minor
commit wording change.
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iommu/arm-smmu: request pcie devices to enable ACS
Date: Mon, 13 Jun 2016 13:45:32 +0100 [thread overview]
Message-ID: <20160613124531.GE1605@arm.com> (raw)
In-Reply-To: <1465809617-13003-1-git-send-email-Wei.Chen@arm.com>
On Mon, Jun 13, 2016 at 05:20:17PM +0800, Wei Chen wrote:
> The PCIe ACS capability will affect the layout of iommu groups.
> Generally speaking, if the path from root port to the PCIe device
> is ACS enabled, the iommu will create a single iommu group for this
> PCIe device. If all PCIe devices on the path are ACS enabled then
> Linux can determine this path is ACS enabled.
>
> Linux use two PCIe configuration registers to determine the ACS
> status of PCIe devices:
> ACS Capability Register and ACS Control Register.
>
> The first register is used to check the implementation of ACS function
> of a PCIe device, the second register is used to check the enable status
> of ACS function. If one PCIe device has implemented and enabled the ACS
> function then Linux will determine this PCIe device enabled ACS.
>
> From the Chapter:6.12 of PCI Express Base Specification Revision 3.1a,
> we can find that when a PCIe device implements ACS function, the enable
> status is set to disabled by default and can be enabled by ACS-aware
> software.
>
> ACS will affect the iommu groups topology, so, the iommu driver is
> ACS-aware software. This patch adds a call to pci_request_acs() to the
> arm-smmu driver to enable the ACS function in PCIe devices that support
> it.
>
> Signed-off-by: Wei Chen <Wei.Chen@arm.com>
> ---
> drivers/iommu/arm-smmu-v3.c | 2 ++
> drivers/iommu/arm-smmu.c | 4 +++-
> 2 files changed, 5 insertions(+), 1 deletion(-)
Thanks, queued for 4.8 w/ Robin and Eric's reviewed-by tags and the minor
commit wording change.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Wei Chen <Wei.Chen@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
robin.murphy@arm.com, joro@8bytes.org, steve.capper@arm.com
Subject: Re: [PATCH] iommu/arm-smmu: request pcie devices to enable ACS
Date: Mon, 13 Jun 2016 13:45:32 +0100 [thread overview]
Message-ID: <20160613124531.GE1605@arm.com> (raw)
In-Reply-To: <1465809617-13003-1-git-send-email-Wei.Chen@arm.com>
On Mon, Jun 13, 2016 at 05:20:17PM +0800, Wei Chen wrote:
> The PCIe ACS capability will affect the layout of iommu groups.
> Generally speaking, if the path from root port to the PCIe device
> is ACS enabled, the iommu will create a single iommu group for this
> PCIe device. If all PCIe devices on the path are ACS enabled then
> Linux can determine this path is ACS enabled.
>
> Linux use two PCIe configuration registers to determine the ACS
> status of PCIe devices:
> ACS Capability Register and ACS Control Register.
>
> The first register is used to check the implementation of ACS function
> of a PCIe device, the second register is used to check the enable status
> of ACS function. If one PCIe device has implemented and enabled the ACS
> function then Linux will determine this PCIe device enabled ACS.
>
> From the Chapter:6.12 of PCI Express Base Specification Revision 3.1a,
> we can find that when a PCIe device implements ACS function, the enable
> status is set to disabled by default and can be enabled by ACS-aware
> software.
>
> ACS will affect the iommu groups topology, so, the iommu driver is
> ACS-aware software. This patch adds a call to pci_request_acs() to the
> arm-smmu driver to enable the ACS function in PCIe devices that support
> it.
>
> Signed-off-by: Wei Chen <Wei.Chen@arm.com>
> ---
> drivers/iommu/arm-smmu-v3.c | 2 ++
> drivers/iommu/arm-smmu.c | 4 +++-
> 2 files changed, 5 insertions(+), 1 deletion(-)
Thanks, queued for 4.8 w/ Robin and Eric's reviewed-by tags and the minor
commit wording change.
Will
next prev parent reply other threads:[~2016-06-13 12:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 9:20 [PATCH] iommu/arm-smmu: request pcie devices to enable ACS Wei Chen
2016-06-13 9:20 ` Wei Chen
2016-06-13 9:20 ` Wei Chen
[not found] ` <1465809617-13003-1-git-send-email-Wei.Chen-5wv7dgnIgG8@public.gmane.org>
2016-06-13 11:18 ` Robin Murphy
2016-06-13 11:18 ` Robin Murphy
2016-06-13 11:18 ` Robin Murphy
[not found] ` <575E969A.6070400-5wv7dgnIgG8@public.gmane.org>
2016-06-13 12:41 ` Auger Eric
2016-06-13 12:41 ` Auger Eric
2016-06-13 12:41 ` Auger Eric
2016-06-13 12:45 ` Will Deacon [this message]
2016-06-13 12:45 ` Will Deacon
2016-06-13 12:45 ` Will Deacon
2016-06-14 3:11 ` Wei Chen
2016-06-14 3:11 ` Wei Chen
[not found] ` <CANta1d-wRGcU51P3Av7EXbvu7hJfUBk_Kd5p=7RDMW6u+v0gvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-14 8:56 ` Will Deacon
2016-06-14 8:56 ` Will Deacon
2016-06-14 8:56 ` Will Deacon
[not found] ` <20160614085627.GA19407-5wv7dgnIgG8@public.gmane.org>
2016-06-14 10:00 ` Wei Chen
2016-06-14 10:00 ` Wei Chen
2016-06-14 10:00 ` Wei Chen
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=20160613124531.GE1605@arm.com \
--to=will.deacon-5wv7dgnigg8@public.gmane.org \
--cc=Wei.Chen-5wv7dgnIgG8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=steve.capper-5wv7dgnIgG8@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.