From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Yong Wu <yong.wu@mediatek.com>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
iommu@lists.linux.dev, linux-mediatek@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mingyuan.ma@mediatek.com,
yf.wang@mediatek.com, jianjiao.zeng@mediatek.com,
chengci.xu@mediatek.com
Subject: Re: [PATCH v9 2/7] iommu/mediatek: Fix two IOMMU share pagetable issue
Date: Fri, 17 Mar 2023 10:34:00 +0100 [thread overview]
Message-ID: <47cac7a6-c069-64a2-7979-b879b075058f@collabora.com> (raw)
In-Reply-To: <20230317085541.20447-3-yong.wu@mediatek.com>
Il 17/03/23 09:55, Yong Wu ha scritto:
> From: "Chengci.Xu" <chengci.xu@mediatek.com>
>
> Prepare for mt8188 to fix a two IOMMU HWs share pagetable issue.
>
> We have two MM IOMMU HWs in mt8188, one is VPP-IOMMU, another is VDO-IOMMU.
> The 2 MM IOMMU HWs share pagetable don't work in this case:
> a) VPP-IOMMU probe firstly.
> b) VDO-IOMMU probe.
> c) The master for VDO-IOMMU probe (means frstdata is vpp-iommu).
> d) The master in another domain probe. No matter it is vdo or vpp.
> Then it still create a new pagetable in step d). The problem is
> "frstdata->bank[0]->m4u_dom" was not initialized. Then when d) enter, it
> still create a new one.
>
> In this patch, we create a new variable "share_dom" for this share
> pgtable case, it should be helpful for readable. and put all the share
> pgtable logic in the mtk_iommu_domain_finalise.
>
> In mt8195, the master of VPP-IOMMU probes before than VDO-IOMMU
> from its dtsi node sequence, we don't see this issue in it. Prepare for
> mt8188.
>
> Signed-off-by: Chengci.Xu <chengci.xu@mediatek.com>
> Signed-off-by: Yong Wu <yong.wu@mediatek.com>
I'm not sure whether this is *not* a fix... if a specific platform wasn't
affected, this may still be a logic mistake... to be cautious, I would
still add a Fixes tag to this one.
Otherwise, I would reword the commit title and remove the "Fix" word, so
that it would look something like...
iommu/mediatek: Prepare for pagetables domain sharing
I'm sorry for noticing that only at v9, but the previous versions had a bit
more stuff to address and couldn't really focus on analyzing this one.
If there's anything I've misunderstood about this patch, please feel free
to explain.
Regards,
Angelo
next prev parent reply other threads:[~2023-03-17 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 8:55 [PATCH v9 0/7] MT8188 IOMMU SUPPORT Yong Wu
2023-03-17 8:55 ` [PATCH v9 1/7] dt-bindings: mediatek: mt8188: Add binding for MM & INFRA IOMMU Yong Wu
2023-03-17 8:59 ` Krzysztof Kozlowski
2023-03-17 8:55 ` [PATCH v9 2/7] iommu/mediatek: Fix two IOMMU share pagetable issue Yong Wu
2023-03-17 9:34 ` AngeloGioacchino Del Regno [this message]
2023-03-21 6:50 ` Yong Wu (吴勇)
2023-03-21 8:52 ` AngeloGioacchino Del Regno
2023-03-17 8:55 ` [PATCH v9 3/7] iommu/mediatek: Adjust mtk_iommu_config flow Yong Wu
2023-03-17 9:34 ` AngeloGioacchino Del Regno
2023-03-17 8:55 ` [PATCH v9 4/7] iommu/mediatek: Add enable IOMMU SMC command for INFRA masters Yong Wu
2023-03-17 9:35 ` AngeloGioacchino Del Regno
2023-03-17 8:55 ` [PATCH v9 5/7] iommu/mediatek: Add MT8188 IOMMU Support Yong Wu
2023-03-17 8:55 ` [PATCH v9 6/7] iommu/mediatek: mt8188: Add iova_region_larb_msk Yong Wu
2023-03-17 8:55 ` [PATCH v9 7/7] MAINTAINERS: iommu/mediatek: Update the header file name Yong Wu
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=47cac7a6-c069-64a2-7979-b879b075058f@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=chengci.xu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jianjiao.zeng@mediatek.com \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mingyuan.ma@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yf.wang@mediatek.com \
--cc=yong.wu@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®