From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] IOMMU: arm-smmu-v3: Fix broken STE.VALID check in Broadcom Vulcan
Date: Thu, 17 Dec 2015 11:42:17 +0000 [thread overview]
Message-ID: <20151217114216.GB11456@arm.com> (raw)
In-Reply-To: <1450346376-30920-1-git-send-email-pmallapp@broadcom.com>
Hi Prem,
Thanks for the update. I still have a few questions though.
On Thu, Dec 17, 2015 at 03:29:35PM +0530, Prem Mallappa wrote:
> Vulcan SMMUv3 looks into more bits than necessary to validate the STE
> entry (including EATS, S2PS, AARCH64), which is a overkill, but without
> the proper encoding; the SMMU stops processing PCIe read/write requests.
> Giving the h/w what it wants.
>
> Signed-off-by: Prem Mallappa <pmallapp@broadcom.com>
> ---
> drivers/iommu/arm-smmu-v3.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/iommu/arm-smmu-v3.c b/drivers/iommu/arm-smmu-v3.c
> index 359190b..9886d2d 100644
> --- a/drivers/iommu/arm-smmu-v3.c
> +++ b/drivers/iommu/arm-smmu-v3.c
> @@ -260,6 +260,7 @@
> #define STRTAB_STE_2_S2VMID_MASK 0xffffUL
> #define STRTAB_STE_2_VTCR_SHIFT 32
> #define STRTAB_STE_2_VTCR_MASK 0x7ffffUL
> +#define STRTAB_STE_2_S2PS_SHIFT 48
> #define STRTAB_STE_2_S2AA64 (1UL << 51)
> #define STRTAB_STE_2_S2ENDI (1UL << 52)
> #define STRTAB_STE_2_S2PTW (1UL << 54)
> @@ -579,6 +580,7 @@ struct arm_smmu_device {
> u32 features;
>
> #define ARM_SMMU_OPT_SKIP_PREFETCH (1 << 0)
> +#define ARM_SMMU_OPT_BRCM_BROKEN_STE_VALID (1 << 1)
> u32 options;
>
> struct arm_smmu_cmdq cmdq;
> @@ -643,6 +645,7 @@ struct arm_smmu_option_prop {
>
> static struct arm_smmu_option_prop arm_smmu_options[] = {
> { ARM_SMMU_OPT_SKIP_PREFETCH, "hisilicon,broken-prefetch-cmd" },
> + { ARM_SMMU_OPT_BRCM_BROKEN_STE_VALID, "broadcom,broken-ste-valid-check" },
> { 0, NULL},
> };
>
> @@ -1053,6 +1056,13 @@ static void arm_smmu_write_strtab_ent(struct arm_smmu_device *smmu, u32 sid,
> : STRTAB_STE_0_CFG_BYPASS;
> dst[0] = cpu_to_le64(val);
> dst[2] = 0; /* Nuke the VMID */
> +
> + if (smmu && (smmu->options & ARM_SMMU_OPT_BRCM_BROKEN_STE_VALID)) {
> + WARN_ON(smmu->oas != 44);
Do we really need this WARN_ON?
> + dst[1] = STRTAB_STE_1_EATS_TRANS << STRTAB_STE_1_EATS_SHIFT;
cpu_to_le64 here too.
> + dst[2] |= cpu_to_le64(STRTAB_STE_2_S2AA64);
> + }
> +
Is this workaround only needed for bypass STEs? If not, we have a problem
when we install a stage-1 entry, because we'll clear the EATS bits as
it stands.
Will
next prev parent reply other threads:[~2015-12-17 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 9:59 [PATCH v2 1/2] IOMMU: arm-smmu-v3: Fix broken STE.VALID check in Broadcom Vulcan Prem Mallappa
2015-12-17 9:59 ` [PATCH v2 2/2] Documentation: dt-bindings: Add option to workaround STE.VALID " Prem Mallappa
2015-12-17 11:51 ` Will Deacon
2015-12-17 12:00 ` Mark Rutland
2015-12-17 11:42 ` Will Deacon [this message]
2015-12-19 4:47 ` [PATCH v2 1/2] IOMMU: arm-smmu-v3: Fix broken STE.VALID check " Prem (Premachandra) Mallappa
2015-12-21 9:55 ` 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=20151217114216.GB11456@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).