From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>
Cc: freedreno@lists.freedesktop.org, quic_sbillaka@quicinc.com,
airlied@gmail.com, andersson@kernel.org, robdclark@gmail.com,
dri-devel@lists.freedesktop.org, dianders@chromium.org,
vkoul@kernel.org, agross@kernel.org, daniel@ffwll.ch,
linux-arm-msm@vger.kernel.org, swboyd@chromium.org,
sean@poorly.run, linux-kernel@vger.kernel.org
Subject: Re: [Freedreno] [PATCH] drm/msm/dpu: add DSC range checking during resource reservation
Date: Wed, 12 Apr 2023 04:06:48 +0300 [thread overview]
Message-ID: <24c5aa23-9b3c-787c-10aa-e9d5ad91512b@linaro.org> (raw)
In-Reply-To: <96416911-bca3-b007-b036-1c4463e83aaa@quicinc.com>
On 12/04/2023 01:32, Abhinav Kumar wrote:
> Hi Marijn
>
> On 4/11/2023 3:24 PM, Marijn Suijten wrote:
>> Again, don't forget to include previous reviewers in cc, please :)
>>
>> On 2023-04-11 14:09:40, Kuogee Hsieh wrote:
>>> Perform DSC range checking to make sure correct DSC is requested before
>>> reserve resource for it.
nit: reserving
>>
>> This isn't performing any range checking for resource reservations /
>> requests: this is only validating the constants written in our catalog
>> and seems rather useless. It isn't fixing any real bug either, so the
>> Fixes: tag below seems extraneous.
>>
>> Given prior comments from Abhinav that "the kernel should be trusted",
>> we should remove this validation for all the other blocks instead.
>>
>
> The purpose of this check is that today all our blocks in RM use the
> DSC_* enum as the size.
>
> struct dpu_hw_blk *dsc_blks[DSC_MAX - DSC_0];
>
> If the device tree ends up with more DSC blocks than the DSC_* enum, how
> can we avoid this issue today? Not because its a bug in device tree but
> how many static number of DSCs are hard-coded in RM.
We don't have these blocks in device tree. And dpu_hw_catalog shouldn't
use indices outside of enum dpu_dsc.
Marijn proposed to pass struct dpu_foo_cfg directly to
dpu_hw_foo_init(). This will allow us to drop these checks completely.
For the time being, I think it might be better to add these checks for
DSC for the sake of uniformity.
>
> And like you said, this is not specific to DSC. Such checks are present
> for other blocks too.
>
>>> Fixes: c985d7bb64ff ("drm/msm/disp/dpu1: Add DSC support in RM")
>>> Signed-off-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
>>> ---
>>> drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 10 +++++++++-
>>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
>>> b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
>>> index f4dda88..95e58f1 100644
>>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
>>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
>>> @@ -1,6 +1,7 @@
>>> // SPDX-License-Identifier: GPL-2.0-only
>>> /*
>>> * Copyright (c) 2016-2018, The Linux Foundation. All rights reserved.
>>> + * Copyright (c) 2023 Qualcomm Innovation Center, Inc. All rights
>>> reserved.
>>> */
>>> #define pr_fmt(fmt) "[drm:%s] " fmt, __func__
>>> @@ -250,6 +251,11 @@ int dpu_rm_init(struct dpu_rm *rm,
>>> struct dpu_hw_dsc *hw;
>>> const struct dpu_dsc_cfg *dsc = &cat->dsc[i];
>>> + if (dsc->id < DSC_0 || dsc->id >= DSC_MAX) {
>>> + DPU_ERROR("skip dsc %d with invalid id\n", dsc->id);
>>> + continue;
>>> + }
>>> +
>>> hw = dpu_hw_dsc_init(dsc->id, mmio, cat);
>>> if (IS_ERR_OR_NULL(hw)) {
>>> rc = PTR_ERR(hw);
>>> @@ -557,8 +563,10 @@ static int _dpu_rm_make_reservation(
>>> }
>>> ret = _dpu_rm_reserve_dsc(rm, global_state, enc,
>>> &reqs->topology);
>>> - if (ret)
>>> + if (ret) {
>>> + DPU_ERROR("unable to find appropriate DSC\n");
>>
>> This, while a nice addition, should go in a different patch.
I'd agree here, a separate patch.
>>
>> Thanks!
>>
>> - Marijn
>>
>>> return ret;
>>> + }
>>> return ret;
>>> }
>>> --
>>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>>> Forum,
>>> a Linux Foundation Collaborative Project
>>>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-04-12 1:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 21:09 Kuogee Hsieh
2023-04-11 21:36 ` Abhinav Kumar
2023-04-11 22:22 ` Dmitry Baryshkov
2023-04-11 22:24 ` Marijn Suijten
2023-04-11 22:32 ` [Freedreno] " Abhinav Kumar
2023-04-12 1:06 ` Dmitry Baryshkov [this message]
2023-04-12 1:50 ` Abhinav Kumar
2023-04-12 7:38 ` Marijn Suijten
2023-04-12 17:48 ` Abhinav Kumar
2023-04-12 18:50 ` Marijn Suijten
2023-04-12 18:56 ` Dmitry Baryshkov
2023-04-12 18:59 ` Abhinav Kumar
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=24c5aa23-9b3c-787c-10aa-e9d5ad91512b@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.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_abhinavk@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®