From: Joerg Roedel <joro@8bytes.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: iommu@lists.linux-foundation.org,
linux-samsung-soc@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] iommu/exynos: Block SYSMMU while invalidating FLPD cache
Date: Wed, 22 Mar 2017 15:51:28 +0100 [thread overview]
Message-ID: <20170322145128.GB7315@8bytes.org> (raw)
In-Reply-To: <1490001484-18890-1-git-send-email-m.szyprowski@samsung.com>
On Mon, Mar 20, 2017 at 10:17:56AM +0100, Marek Szyprowski wrote:
> Documentation specifies that SYSMMU should be in blocked state while
> performing TLB/FLPD cache invalidation, so add needed calls to
> sysmmu_block/unblock.
>
> Fixes: 66a7ed84b345d ("iommu/exynos: Apply workaround of caching fault page table entries")
> CC: stable@vger.kernel.org # v4.10+
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> This issue has been introduced long time ago, but this fix applies only for
> v4.10+ kernels due to other changes in the surrounding code.
> ---
> drivers/iommu/exynos-iommu.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
Applied both patches to iommu/fixes, thanks.
prev parent reply other threads:[~2017-03-22 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170320091820eucas1p22b62f2d7e089cd997aecc62a4c5b7730@eucas1p2.samsung.com>
2017-03-20 9:17 ` [PATCH 1/2] iommu/exynos: Block SYSMMU while invalidating FLPD cache Marek Szyprowski
2017-03-20 9:17 ` [PATCH 2/2] iommu/exynos: Workaround FLPD cache flush issues for SYSMMU v5 Marek Szyprowski
2017-03-20 10:31 ` Andrzej Hajda
2017-03-22 14:51 ` 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=20170322145128.GB7315@8bytes.org \
--to=joro@8bytes.org \
--cc=a.hajda@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=iommu@lists.linux-foundation.org \
--cc=krzk@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=stable@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).