From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <freedreno@lists.freedesktop.org>,
Rob Clark <robdclark@gmail.com>, "Sean Paul" <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
"David Airlie" <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
<dri-devel@lists.freedesktop.org>, <seanpaul@chromium.org>,
<swboyd@chromium.org>, <dianders@chromium.org>,
<quic_jesszhan@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/4] drm/msm: register a fault handler for display mmu faults
Date: Fri, 21 Jun 2024 16:31:48 -0700 [thread overview]
Message-ID: <70942425-af39-4bbc-4ab4-8124e336b666@quicinc.com> (raw)
In-Reply-To: <cwo63ra2ogrdr3ywmiuxewzuxzsyozyqfcict7xs5kp6uwy2qp@7e6fgb7oyszc>
On 5/19/2024 1:31 AM, Dmitry Baryshkov wrote:
> On Fri, May 17, 2024 at 04:37:56PM -0700, Abhinav Kumar wrote:
>> In preparation to register a iommu fault handler for display
>> related modules, register a fault handler for the backing
>> mmu object of msm_kms.
>>
>> Currently, the fault handler only captures the display snapshot
>> but we can expand this later if more information needs to be
>> added to debug display mmu faults.
>>
>> Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
>> ---
>> drivers/gpu/drm/msm/msm_kms.c | 25 +++++++++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/msm/msm_kms.c b/drivers/gpu/drm/msm/msm_kms.c
>> index af6a6fcb1173..62c8e6163e81 100644
>> --- a/drivers/gpu/drm/msm/msm_kms.c
>> +++ b/drivers/gpu/drm/msm/msm_kms.c
>> @@ -200,6 +200,28 @@ struct msm_gem_address_space *msm_kms_init_aspace(struct drm_device *dev)
>> return aspace;
>> }
>>
>> +static int msm_kms_fault_handler(void *arg, unsigned long iova, int flags, void *data)
>> +{
>> + struct msm_kms *kms = arg;
>> + struct msm_disp_state *state;
>> + int ret;
>> +
>> + ret = mutex_lock_interruptible(&kms->dump_mutex);
>> + if (ret)
>> + return ret;
>> +
>> + state = msm_disp_snapshot_state_sync(kms);
>> +
>> + mutex_unlock(&kms->dump_mutex);
>> +
>> + if (IS_ERR(state)) {
>> + DRM_DEV_ERROR(kms->dev->dev, "failed to capture snapshot\n");
>> + return PTR_ERR(state);
>> + }
>> +
>> + return 0;
>> +}
>> +
>> void msm_drm_kms_uninit(struct device *dev)
>> {
>> struct platform_device *pdev = to_platform_device(dev);
>> @@ -261,6 +283,9 @@ int msm_drm_kms_init(struct device *dev, const struct drm_driver *drv)
>> goto err_msm_uninit;
>> }
>>
>> + if (kms->aspace)
>> + msm_mmu_set_fault_handler(kms->aspace->mmu, kms, msm_kms_fault_handler);
>> +
>
> Can we move this to msm_kms_init_aspace() instead of checking for
> kms->aspace?
Ack.
>
>> drm_helper_move_panel_connectors_to_head(ddev);
>>
>> drm_for_each_crtc(crtc, ddev) {
>> --
>> 2.44.0
>>
>
next prev parent reply other threads:[~2024-06-21 23:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240517233801.4071868-1-quic_abhinavk@quicinc.com>
2024-05-17 23:37 ` Abhinav Kumar
2024-05-19 8:31 ` Dmitry Baryshkov
2024-06-21 23:31 ` Abhinav Kumar [this message]
2024-05-19 8:38 ` Dmitry Baryshkov
2024-06-21 23:35 ` Abhinav Kumar
2024-06-22 2:05 ` Abhinav Kumar
2024-05-21 4:12 ` Stephen Boyd
2024-06-22 1:54 ` Abhinav Kumar
2024-05-17 23:37 ` [RFC PATCH 2/4] drm/msm/iommu: rename msm_fault_handler to msm_gpu_fault_handler Abhinav Kumar
2024-05-19 8:32 ` Dmitry Baryshkov
2024-05-17 23:37 ` [RFC PATCH 3/4] drm/msm/iommu: introduce msm_iommu_disp_new() for msm_kms Abhinav Kumar
2024-05-19 8:38 ` Dmitry Baryshkov
2024-05-17 23:37 ` [RFC PATCH 4/4] drm/msm: switch msm_kms to use msm_iommu_disp_new() Abhinav Kumar
2024-05-19 8:39 ` 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=70942425-af39-4bbc-4ab4-8124e336b666@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=seanpaul@chromium.org \
--cc=swboyd@chromium.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
all inboxes | Powered by JetHome®