From: Vinod Koul <vinod.koul@intel.com>
To: Sricharan R <sricharan@codeaurora.org>
Cc: jcrouse@codeaurora.org, pdaly@codeaurora.org,
jgebben@codeaurora.org, joro@8bytes.org,
linux-kernel@vger.kernel.org, pratikp@codeaurora.org,
iommu@lists.linux-foundation.org, robin.murphy@arm.com,
tzeng@codeaurora.org, linux-arm-kernel@lists.infradead.org,
will.deacon@arm.com, mitchelh@codeaurora.org
Subject: Re: [RESEND PATCH V6 5/6] dmaengine: pl330: Make sure microcode is privileged
Date: Tue, 6 Dec 2016 10:31:15 +0530 [thread overview]
Message-ID: <20161206050115.GP6408@localhost> (raw)
In-Reply-To: <1480690509-13490-6-git-send-email-sricharan@codeaurora.org>
On Fri, Dec 02, 2016 at 08:25:08PM +0530, Sricharan R wrote:
> From: Mitchel Humpherys <mitchelh@codeaurora.org>
>
> The PL330 performs privileged instruction fetches. This can result in
> SMMU permission faults on SMMUs that implement the ARMv8 VMSA, which
> specifies that mappings that are writeable at one execution level shall
> not be executable at any higher-privileged level. Fix this by using the
> DMA_ATTR_PRIVILEGED attribute, which will ensure that the microcode
> IOMMU mapping is only accessible to the privileged level.
Acked-by: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Sricharan R <sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: pdaly-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
pratikp-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
will.deacon-5wv7dgnIgG8@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
jgebben-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
tzeng-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [RESEND PATCH V6 5/6] dmaengine: pl330: Make sure microcode is privileged
Date: Tue, 6 Dec 2016 10:31:15 +0530 [thread overview]
Message-ID: <20161206050115.GP6408@localhost> (raw)
In-Reply-To: <1480690509-13490-6-git-send-email-sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
On Fri, Dec 02, 2016 at 08:25:08PM +0530, Sricharan R wrote:
> From: Mitchel Humpherys <mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
>
> The PL330 performs privileged instruction fetches. This can result in
> SMMU permission faults on SMMUs that implement the ARMv8 VMSA, which
> specifies that mappings that are writeable at one execution level shall
> not be executable at any higher-privileged level. Fix this by using the
> DMA_ATTR_PRIVILEGED attribute, which will ensure that the microcode
> IOMMU mapping is only accessible to the privileged level.
Acked-by: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH V6 5/6] dmaengine: pl330: Make sure microcode is privileged
Date: Tue, 6 Dec 2016 10:31:15 +0530 [thread overview]
Message-ID: <20161206050115.GP6408@localhost> (raw)
In-Reply-To: <1480690509-13490-6-git-send-email-sricharan@codeaurora.org>
On Fri, Dec 02, 2016 at 08:25:08PM +0530, Sricharan R wrote:
> From: Mitchel Humpherys <mitchelh@codeaurora.org>
>
> The PL330 performs privileged instruction fetches. This can result in
> SMMU permission faults on SMMUs that implement the ARMv8 VMSA, which
> specifies that mappings that are writeable at one execution level shall
> not be executable at any higher-privileged level. Fix this by using the
> DMA_ATTR_PRIVILEGED attribute, which will ensure that the microcode
> IOMMU mapping is only accessible to the privileged level.
Acked-by: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
next prev parent reply other threads:[~2016-12-06 4:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 14:55 [RESEND PATCH V6 0/6] Add support for privileged mappings Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` [RESEND PATCH V6 1/6] iommu: add IOMMU_PRIV attribute Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` [RESEND PATCH V6 2/6] iommu/io-pgtable-arm: add support for the IOMMU_PRIV flag Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` [RESEND PATCH V6 3/6] common: DMA-mapping: add DMA_ATTR_PRIVILEGED attribute Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` [RESEND PATCH V6 4/6] arm64/dma-mapping: Implement DMA_ATTR_PRIVILEGED Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` [RESEND PATCH V6 5/6] dmaengine: pl330: Make sure microcode is privileged Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-06 5:01 ` Vinod Koul [this message]
2016-12-06 5:01 ` Vinod Koul
2016-12-06 5:01 ` Vinod Koul
2016-12-02 14:55 ` [PATCH V6 6/6] iommu/arm-smmu: Set privileged attribute to 'default' instead of 'unprivileged' Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-02 14:55 ` Sricharan R
2016-12-06 17:31 ` Will Deacon
2016-12-06 17:31 ` Will Deacon
2016-12-06 17:31 ` Will Deacon
2016-12-02 16:16 ` [RESEND PATCH V6 0/6] Add support for privileged mappings Robin Murphy
2016-12-02 16:16 ` Robin Murphy
2016-12-02 16:16 ` Robin Murphy
2016-12-04 7:48 ` Sricharan
2016-12-04 7:48 ` Sricharan
2016-12-04 7:48 ` Sricharan
2016-12-06 19:14 ` Robin Murphy
2016-12-06 19:14 ` Robin Murphy
2016-12-06 19:14 ` Robin Murphy
2016-12-07 9:44 ` Sricharan
2016-12-07 9:44 ` Sricharan
2016-12-07 9:44 ` Sricharan
2016-12-12 19:34 ` Sricharan
2016-12-12 19:34 ` Sricharan
2016-12-12 19:34 ` Sricharan
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=20161206050115.GP6408@localhost \
--to=vinod.koul@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jcrouse@codeaurora.org \
--cc=jgebben@codeaurora.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitchelh@codeaurora.org \
--cc=pdaly@codeaurora.org \
--cc=pratikp@codeaurora.org \
--cc=robin.murphy@arm.com \
--cc=sricharan@codeaurora.org \
--cc=tzeng@codeaurora.org \
--cc=will.deacon@arm.com \
/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.