From: "Laguna, Lukasz" <lukasz.laguna@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/xe/vf: Don't support changing GuC reset policy
Date: Thu, 3 Apr 2025 17:06:03 +0200 [thread overview]
Message-ID: <bb123841-e6e6-4c55-9003-2762e078c415@intel.com> (raw)
In-Reply-To: <3db59050-da84-4d82-8d09-b610397eda91@intel.com>
On 4/3/2025 12:56, Michal Wajdeczko wrote:
>
> On 03.04.2025 11:41, Lukasz Laguna wrote:
>> VF can't change GuC reset policy. Ensure the driver does not attempt to
>> do so by adding an assertion.
> none of xe_guc_ads() functions are applicable for the VFs by definition,
> since GuC ADS is purely a PF/native responsibility
>
> why do we want to assert just one of these function?
>
> it should either fail (due to use of the privileged H2G action) or crash
> (due to use of previously uninitialized structures)
>
> I'm not sure that we want to annotate/pollute all privileged parts of
> the driver with !IS_SRIOV_VF asserts
Makes sense. I'll drop this patch.
>
>> Signed-off-by: Lukasz Laguna <lukasz.laguna@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_guc_ads.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_guc_ads.c b/drivers/gpu/drm/xe/xe_guc_ads.c
>> index bee4e0cfe7b8..2ea07d28728e 100644
>> --- a/drivers/gpu/drm/xe/xe_guc_ads.c
>> +++ b/drivers/gpu/drm/xe/xe_guc_ads.c
>> @@ -990,6 +990,8 @@ int xe_guc_ads_scheduler_policy_toggle_reset(struct xe_guc_ads *ads)
>> struct xe_bo *bo;
>> int ret = 0;
>>
>> + xe_gt_assert(gt, !IS_SRIOV_VF(gt_to_xe(gt)));
>> +
>> policies = kmalloc(sizeof(*policies), GFP_KERNEL);
>> if (!policies)
>> return -ENOMEM;
next prev parent reply other threads:[~2025-04-03 15:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 9:41 [PATCH 0/2] VF: Don't update GuC reset policy when changing wedged mode Lukasz Laguna
2025-04-03 9:41 ` [PATCH 1/2] drm/xe/vf: Don't support changing GuC reset policy Lukasz Laguna
2025-04-03 10:56 ` Michal Wajdeczko
2025-04-03 15:06 ` Laguna, Lukasz [this message]
2025-04-03 9:41 ` [PATCH 2/2] drm/xe/vf: Don't update GuC reset policy when changing wedged mode Lukasz Laguna
2025-04-03 11:05 ` Michal Wajdeczko
2025-04-03 15:17 ` Laguna, Lukasz
2025-04-03 16:49 ` Michal Wajdeczko
2025-04-04 10:03 ` Laguna, Lukasz
2025-04-03 11:56 ` ✓ CI.Patch_applied: success for VF: " Patchwork
2025-04-03 11:56 ` ✓ CI.checkpatch: " Patchwork
2025-04-03 11:58 ` ✓ CI.KUnit: " Patchwork
2025-04-03 12:26 ` ✓ CI.Build: " Patchwork
2025-04-03 12:28 ` ✓ CI.Hooks: " Patchwork
2025-04-03 12:30 ` ✓ CI.checksparse: " Patchwork
2025-04-03 15:39 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-04 5:04 ` ✓ Xe.CI.BAT: success " Patchwork
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=bb123841-e6e6-4c55-9003-2762e078c415@intel.com \
--to=lukasz.laguna@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.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