From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Aleksey Makarov
<aleksey.makarov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Tomasz Nowicki
<tnowicki-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@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 v4] iommu/arm-smmu: Support for Extended Stream ID (16 bit)
Date: Thu, 19 Jan 2017 16:13:31 +0000 [thread overview]
Message-ID: <20170119161331.GG31594@arm.com> (raw)
In-Reply-To: <20170119143653.7576-1-aleksey.makarov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On Thu, Jan 19, 2017 at 05:36:36PM +0300, Aleksey Makarov wrote:
> It is the time we have the real 16-bit Stream ID user, which is the
> ThunderX. Its IO topology uses 1:1 map for Requester ID to Stream ID
> translation for each root complex which allows to get full 16-bit
> Stream ID. Firmware assigns bus IDs that are greater than 128 (0x80)
> to some buses under PEM (external PCIe interface). Eventually SMMU
> drops devices on that buses because their Stream ID is out of range:
>
> pci 0006:90:00.0: stream ID 0x9000 out of range for SMMU (0x7fff)
>
> To fix above issue enable the Extended Stream ID optional feature
> when available.
>
> Reviewed-by: Tomasz Nowicki <tomasz.nowicki-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
> Signed-off-by: Aleksey Makarov <aleksey.makarov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> Tested-by: Tomasz Nowicki <tomasz.nowicki-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
> ---
> v4:
> change the commit message:
> - explain the reason why the warning happens (Tomasz Nowicki)
> - add 'Reviewed-by' and 'Tested-by' from Tomasz Nowicki
Thanks, I'll queue this for 4.11.
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 v4] iommu/arm-smmu: Support for Extended Stream ID (16 bit)
Date: Thu, 19 Jan 2017 16:13:31 +0000 [thread overview]
Message-ID: <20170119161331.GG31594@arm.com> (raw)
In-Reply-To: <20170119143653.7576-1-aleksey.makarov@linaro.org>
On Thu, Jan 19, 2017 at 05:36:36PM +0300, Aleksey Makarov wrote:
> It is the time we have the real 16-bit Stream ID user, which is the
> ThunderX. Its IO topology uses 1:1 map for Requester ID to Stream ID
> translation for each root complex which allows to get full 16-bit
> Stream ID. Firmware assigns bus IDs that are greater than 128 (0x80)
> to some buses under PEM (external PCIe interface). Eventually SMMU
> drops devices on that buses because their Stream ID is out of range:
>
> pci 0006:90:00.0: stream ID 0x9000 out of range for SMMU (0x7fff)
>
> To fix above issue enable the Extended Stream ID optional feature
> when available.
>
> Reviewed-by: Tomasz Nowicki <tomasz.nowicki@caviumnetworks.com>
> Signed-off-by: Aleksey Makarov <aleksey.makarov@linaro.org>
> Tested-by: Tomasz Nowicki <tomasz.nowicki@caviumnetworks.com>
> ---
> v4:
> change the commit message:
> - explain the reason why the warning happens (Tomasz Nowicki)
> - add 'Reviewed-by' and 'Tested-by' from Tomasz Nowicki
Thanks, I'll queue this for 4.11.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Aleksey Makarov <aleksey.makarov@linaro.org>
Cc: iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
Tomasz Nowicki <tnowicki@caviumnetworks.com>,
Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH v4] iommu/arm-smmu: Support for Extended Stream ID (16 bit)
Date: Thu, 19 Jan 2017 16:13:31 +0000 [thread overview]
Message-ID: <20170119161331.GG31594@arm.com> (raw)
In-Reply-To: <20170119143653.7576-1-aleksey.makarov@linaro.org>
On Thu, Jan 19, 2017 at 05:36:36PM +0300, Aleksey Makarov wrote:
> It is the time we have the real 16-bit Stream ID user, which is the
> ThunderX. Its IO topology uses 1:1 map for Requester ID to Stream ID
> translation for each root complex which allows to get full 16-bit
> Stream ID. Firmware assigns bus IDs that are greater than 128 (0x80)
> to some buses under PEM (external PCIe interface). Eventually SMMU
> drops devices on that buses because their Stream ID is out of range:
>
> pci 0006:90:00.0: stream ID 0x9000 out of range for SMMU (0x7fff)
>
> To fix above issue enable the Extended Stream ID optional feature
> when available.
>
> Reviewed-by: Tomasz Nowicki <tomasz.nowicki@caviumnetworks.com>
> Signed-off-by: Aleksey Makarov <aleksey.makarov@linaro.org>
> Tested-by: Tomasz Nowicki <tomasz.nowicki@caviumnetworks.com>
> ---
> v4:
> change the commit message:
> - explain the reason why the warning happens (Tomasz Nowicki)
> - add 'Reviewed-by' and 'Tested-by' from Tomasz Nowicki
Thanks, I'll queue this for 4.11.
Will
next prev parent reply other threads:[~2017-01-19 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 14:36 [PATCH v4] iommu/arm-smmu: Support for Extended Stream ID (16 bit) Aleksey Makarov
2017-01-19 14:36 ` Aleksey Makarov
2017-01-19 14:36 ` Aleksey Makarov
[not found] ` <20170119143653.7576-1-aleksey.makarov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-01-19 16:13 ` Will Deacon [this message]
2017-01-19 16:13 ` Will Deacon
2017-01-19 16:13 ` Will Deacon
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=20170119161331.GG31594@arm.com \
--to=will.deacon-5wv7dgnigg8@public.gmane.org \
--cc=aleksey.makarov-QSEj5FYQhm4dnm+yROfE0A@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=tnowicki-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@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.