From: Akhil P Oommen <quic_akhilpo@quicinc.com>
To: Rob Clark <robdclark@gmail.com>, <iommu@lists.linux.dev>
Cc: <linux-arm-msm@vger.kernel.org>,
<freedreno@lists.freedesktop.org>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>, Rob Clark <robdclark@chromium.org>,
Joerg Roedel <joro@8bytes.org>,
"moderated list:ARM SMMU DRIVERS"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iommu/arm-smmu-qcom: Only enable stall on smmu-v2
Date: Tue, 7 Jan 2025 01:40:47 +0530 [thread overview]
Message-ID: <48373519-2867-419d-9f51-e7bd330b311c@quicinc.com> (raw)
In-Reply-To: <76b822f0-c4c5-4d47-8e0b-c1eee513e228@quicinc.com>
On 1/3/2025 1:00 AM, Akhil P Oommen wrote:
> On 1/3/2025 12:02 AM, Rob Clark wrote:
>> From: Rob Clark <robdclark@chromium.org>
>>
>> On mmu-500, stall-on-fault seems to stall all context banks, causing the
>> GMU to misbehave. So limit this feature to smmu-v2 for now.
>>
>> This fixes an issue with an older mesa bug taking outo the system
>> because of GMU going off into the weeds.
>>
>> What we _think_ is happening is that, if the GPU generates 1000's of
>> faults at ~once (which is something that GPUs can be good at), it can
>> result in a sufficient number of stalled translations preventing other
>> transactions from entering the same TBU.
>>
>> Signed-off-by: Rob Clark <robdclark@chromium.org>
>
> Reviewed-by: Akhil P Oommen <quic_akhilpo@quicinc.com>
>
Btw, if stall is not enabled, I think there is no point in capturing
coredump from adreno pagefault handler. By the time we start coredump,
gpu might have switched context.
-Akhil.
> -Akhil
>
next prev parent reply other threads:[~2025-01-06 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 18:32 [PATCH v2] iommu/arm-smmu-qcom: Only enable stall on smmu-v2 Rob Clark
2025-01-02 19:30 ` Akhil P Oommen
2025-01-06 20:10 ` Akhil P Oommen [this message]
2025-01-06 20:59 ` Rob Clark
2025-01-06 21:00 ` Rob Clark
2025-01-07 12:57 ` Will Deacon
2025-01-07 15:26 ` Rob Clark
2025-01-07 22:43 ` Dmitry Baryshkov
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=48373519-2867-419d-9f51-e7bd330b311c@quicinc.com \
--to=quic_akhilpo@quicinc.com \
--cc=freedreno@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--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: 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