From: "Yong Wu (吴勇)" <Yong.Wu@mediatek.com> To: "laura.nao@collabora.com" <laura.nao@collabora.com> Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-mediatek@lists.infradead.org" <linux-mediatek@lists.infradead.org>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "Jianjiao Zeng (曾健姣)" <Jianjiao.Zeng@mediatek.com>, "kernel@collabora.com" <kernel@collabora.com>, "robin.murphy@arm.com" <robin.murphy@arm.com>, "joro@8bytes.org" <joro@8bytes.org>, "Chengci Xu (许承赐)" <Chengci.Xu@mediatek.com>, "YF Wang (王云飞)" <YF.Wang@mediatek.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "krzysztof.kozlowski+dt@linaro.org" <krzysztof.kozlowski+dt@linaro.org>, "iommu@lists.linux.dev" <iommu@lists.linux.dev>, "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>, "Mingyuan Ma (马鸣远)" <Mingyuan.Ma@mediatek.com>, "angelogioacchino.delregno@collabora.com" <angelogioacchino.delregno@collabora.com>, "will@kernel.org" <will@kernel.org> Subject: Re: [PATCH v12 2/7] iommu/mediatek: Fix two IOMMU share pagetable issue Date: Sat, 19 Aug 2023 08:45:32 +0000 [thread overview] Message-ID: <12c6d8c39b402b63c57800189c18bffcf091e52f.camel@mediatek.com> (raw) In-Reply-To: <20230818154156.314742-1-laura.nao@collabora.com> Hi Laura, Thanks very much for your testing. On Fri, 2023-08-18 at 17:41 +0200, Laura Nao wrote: > Hello, > > This patch is causing fluster tests to fail on MT8192, IOMMU read and > write faults are reported in the log. Here's an extract is from the > VP9 tests: > > mtk-iommu 1401d000.m4u: fault type=0x280 iova=0x1ff7c0000 pa=0x0 > master=0x5000480(larb=5 port=0) layer=0 read > mtk-iommu 1401d000.m4u: fault type=0x280 iova=0x1fe3ee000 pa=0x0 > master=0x5000492(larb=5 port=4) layer=0 write > > Tests are failing for H264, VP8 and VP9 decoding on next-20230817 > with fluster in the same way, complete logs can be found here: > - H264: > https://urldefense.com/v3/__https://storage.kernelci.org/next/master/next-20230817/arm64/defconfig*arm64-chromebook*videodec/gcc-10/lab-collabora/v4l2-decoder-conformance-h264-mt8192-asurada-spherion-r0.html__;Kys!!CTRNKA9wMg0ARbw!g5CkV4Tmx8gZ_Ll6AMpoEosTjSgKbdfG2RNwJJFdnpX4g-MW0IdAmt3bXphiIIfSPmGbbPO1tFM4b8wSlrgogw$ > > - VP8: > https://urldefense.com/v3/__https://storage.kernelci.org/next/master/next-20230817/arm64/defconfig*arm64-chromebook*videodec/gcc-10/lab-collabora/v4l2-decoder-conformance-vp8-mt8192-asurada-spherion-r0.html__;Kys!!CTRNKA9wMg0ARbw!g5CkV4Tmx8gZ_Ll6AMpoEosTjSgKbdfG2RNwJJFdnpX4g-MW0IdAmt3bXphiIIfSPmGbbPO1tFM4b8wa_83EZw$ > > - VP9: > https://urldefense.com/v3/__https://storage.kernelci.org/next/master/next-20230817/arm64/defconfig*arm64-chromebook*videodec/gcc-10/lab-collabora/v4l2-decoder-conformance-vp9-mt8192-asurada-spherion-r0.html__;Kys!!CTRNKA9wMg0ARbw!g5CkV4Tmx8gZ_Ll6AMpoEosTjSgKbdfG2RNwJJFdnpX4g-MW0IdAmt3bXphiIIfSPmGbbPO1tFM4b8xaOT2SLw$ > > > Reverting this patch fixes the issue. > > From my understanding, on MT8192 the 16GB iova space is partitioned > between display, vcodec and camera. The iommu domain configuration > for vcodec was loaded from frstdata->bank[0]->m4u_dom (vcodec is > preassigned to a specific iova range), while after this patch a new > pagetable is created instead. Exactly Right. It creates a new pagetable for this case. I sent a patch for this. Could you also help confirm? Thanks. https://lore.kernel.org/linux-mediatek/20230819081443.8333-1-yong.wu@mediatek.com/ > > Do you have any insight on how to fix this while keeping > compatibility with MT8188 and MT8195? > > Best, > > Laura
WARNING: multiple messages have this Message-ID (diff)
From: "Yong Wu (吴勇)" <Yong.Wu@mediatek.com> To: "laura.nao@collabora.com" <laura.nao@collabora.com> Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-mediatek@lists.infradead.org" <linux-mediatek@lists.infradead.org>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "Jianjiao Zeng (曾健姣)" <Jianjiao.Zeng@mediatek.com>, "kernel@collabora.com" <kernel@collabora.com>, "robin.murphy@arm.com" <robin.murphy@arm.com>, "joro@8bytes.org" <joro@8bytes.org>, "Chengci Xu (许承赐)" <Chengci.Xu@mediatek.com>, "YF Wang (王云飞)" <YF.Wang@mediatek.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "krzysztof.kozlowski+dt@linaro.org" <krzysztof.kozlowski+dt@linaro.org>, "iommu@lists.linux.dev" <iommu@lists.linux.dev>, "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>, "Mingyuan Ma (马鸣远)" <Mingyuan.Ma@mediatek.com>, "angelogioacchino.delregno@collabora.com" <angelogioacchino.delregno@collabora.com>, "will@kernel.org" <will@kernel.org> Subject: Re: [PATCH v12 2/7] iommu/mediatek: Fix two IOMMU share pagetable issue Date: Sat, 19 Aug 2023 08:45:32 +0000 [thread overview] Message-ID: <12c6d8c39b402b63c57800189c18bffcf091e52f.camel@mediatek.com> (raw) In-Reply-To: <20230818154156.314742-1-laura.nao@collabora.com> Hi Laura, Thanks very much for your testing. On Fri, 2023-08-18 at 17:41 +0200, Laura Nao wrote: > Hello, > > This patch is causing fluster tests to fail on MT8192, IOMMU read and > write faults are reported in the log. Here's an extract is from the > VP9 tests: > > mtk-iommu 1401d000.m4u: fault type=0x280 iova=0x1ff7c0000 pa=0x0 > master=0x5000480(larb=5 port=0) layer=0 read > mtk-iommu 1401d000.m4u: fault type=0x280 iova=0x1fe3ee000 pa=0x0 > master=0x5000492(larb=5 port=4) layer=0 write > > Tests are failing for H264, VP8 and VP9 decoding on next-20230817 > with fluster in the same way, complete logs can be found here: > - H264: > https://urldefense.com/v3/__https://storage.kernelci.org/next/master/next-20230817/arm64/defconfig*arm64-chromebook*videodec/gcc-10/lab-collabora/v4l2-decoder-conformance-h264-mt8192-asurada-spherion-r0.html__;Kys!!CTRNKA9wMg0ARbw!g5CkV4Tmx8gZ_Ll6AMpoEosTjSgKbdfG2RNwJJFdnpX4g-MW0IdAmt3bXphiIIfSPmGbbPO1tFM4b8wSlrgogw$ > > - VP8: > https://urldefense.com/v3/__https://storage.kernelci.org/next/master/next-20230817/arm64/defconfig*arm64-chromebook*videodec/gcc-10/lab-collabora/v4l2-decoder-conformance-vp8-mt8192-asurada-spherion-r0.html__;Kys!!CTRNKA9wMg0ARbw!g5CkV4Tmx8gZ_Ll6AMpoEosTjSgKbdfG2RNwJJFdnpX4g-MW0IdAmt3bXphiIIfSPmGbbPO1tFM4b8wa_83EZw$ > > - VP9: > https://urldefense.com/v3/__https://storage.kernelci.org/next/master/next-20230817/arm64/defconfig*arm64-chromebook*videodec/gcc-10/lab-collabora/v4l2-decoder-conformance-vp9-mt8192-asurada-spherion-r0.html__;Kys!!CTRNKA9wMg0ARbw!g5CkV4Tmx8gZ_Ll6AMpoEosTjSgKbdfG2RNwJJFdnpX4g-MW0IdAmt3bXphiIIfSPmGbbPO1tFM4b8xaOT2SLw$ > > > Reverting this patch fixes the issue. > > From my understanding, on MT8192 the 16GB iova space is partitioned > between display, vcodec and camera. The iommu domain configuration > for vcodec was loaded from frstdata->bank[0]->m4u_dom (vcodec is > preassigned to a specific iova range), while after this patch a new > pagetable is created instead. Exactly Right. It creates a new pagetable for this case. I sent a patch for this. Could you also help confirm? Thanks. https://lore.kernel.org/linux-mediatek/20230819081443.8333-1-yong.wu@mediatek.com/ > > Do you have any insight on how to fix this while keeping > compatibility with MT8188 and MT8195? > > Best, > > Laura _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-19 8:48 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-02 9:02 [PATCH v12 0/7] MT8188 IOMMU SUPPORT Yong Wu 2023-06-02 9:02 ` Yong Wu 2023-06-02 9:02 ` [PATCH v12 1/7] dt-bindings: mediatek: mt8188: Add binding for MM & INFRA IOMMU Yong Wu 2023-06-02 9:02 ` Yong Wu 2023-08-17 8:21 ` Chen-Yu Tsai 2023-08-17 8:21 ` Chen-Yu Tsai 2023-06-02 9:02 ` [PATCH v12 2/7] iommu/mediatek: Fix two IOMMU share pagetable issue Yong Wu 2023-06-02 9:02 ` Yong Wu 2023-06-06 13:59 ` Alexandre Mergnat 2023-06-06 13:59 ` Alexandre Mergnat 2023-08-18 15:41 ` Laura Nao 2023-08-18 15:41 ` Laura Nao 2023-08-19 8:45 ` Yong Wu (吴勇) [this message] 2023-08-19 8:45 ` Yong Wu (吴勇) 2023-06-02 9:02 ` [PATCH v12 3/7] iommu/mediatek: Adjust mtk_iommu_config flow Yong Wu 2023-06-02 9:02 ` Yong Wu 2023-06-06 14:00 ` Alexandre Mergnat 2023-06-06 14:00 ` Alexandre Mergnat 2023-06-02 9:02 ` [PATCH v12 4/7] iommu/mediatek: Add enable IOMMU SMC command for INFRA masters Yong Wu 2023-06-02 9:02 ` Yong Wu 2023-06-06 14:04 ` Alexandre Mergnat 2023-06-06 14:04 ` Alexandre Mergnat 2023-06-02 9:02 ` [PATCH v12 5/7] iommu/mediatek: Add MT8188 IOMMU Support Yong Wu 2023-06-02 9:02 ` Yong Wu 2023-06-06 14:16 ` Alexandre Mergnat 2023-06-06 14:16 ` Alexandre Mergnat 2023-08-08 9:53 ` Chen-Yu Tsai 2023-08-08 9:53 ` Chen-Yu Tsai 2023-08-10 12:22 ` Yong Wu (吴勇) 2023-08-10 12:22 ` Yong Wu (吴勇) 2023-08-11 3:30 ` Chen-Yu Tsai 2023-08-11 3:30 ` Chen-Yu Tsai 2023-08-14 7:14 ` Yong Wu (吴勇) 2023-08-14 7:14 ` Yong Wu (吴勇) 2023-08-14 8:21 ` Chen-Yu Tsai 2023-08-14 8:21 ` Chen-Yu Tsai 2023-08-17 8:01 ` Yong Wu (吴勇) 2023-08-17 8:01 ` Yong Wu (吴勇) 2023-08-17 8:10 ` Chen-Yu Tsai 2023-08-17 8:10 ` Chen-Yu Tsai 2023-06-02 9:02 ` [PATCH v12 6/7] iommu/mediatek: mt8188: Add iova_region_larb_msk Yong Wu 2023-06-02 9:02 ` Yong Wu 2023-06-06 14:19 ` Alexandre Mergnat 2023-06-06 14:19 ` Alexandre Mergnat 2023-06-02 9:02 ` [PATCH v12 7/7] MAINTAINERS: iommu/mediatek: Update the header file name Yong Wu 2023-06-02 9:02 ` Yong Wu 2023-07-25 7:59 ` [PATCH v12 0/7] MT8188 IOMMU SUPPORT Fei Shao [not found] ` <cc910b5c3ec130f092a37049d71bb35c20b278a6.camel@mediatek.com> 2023-08-07 12:17 ` joro 2023-08-07 12:17 ` joro 2023-08-07 12:17 ` joro
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=12c6d8c39b402b63c57800189c18bffcf091e52f.camel@mediatek.com \ --to=yong.wu@mediatek.com \ --cc=Chengci.Xu@mediatek.com \ --cc=Jianjiao.Zeng@mediatek.com \ --cc=Mingyuan.Ma@mediatek.com \ --cc=YF.Wang@mediatek.com \ --cc=angelogioacchino.delregno@collabora.com \ --cc=devicetree@vger.kernel.org \ --cc=iommu@lists.linux.dev \ --cc=joro@8bytes.org \ --cc=kernel@collabora.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=laura.nao@collabora.com \ --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=robh+dt@kernel.org \ --cc=robin.murphy@arm.com \ --cc=will@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: linkBe 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.