From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH] drm/xe/vf: Skip attempt to start GuC PC if VF
Date: Sat, 22 Jun 2024 11:34:46 +0200 [thread overview]
Message-ID: <18cd3da8-60d7-453b-8fcf-4105cdae7665@intel.com> (raw)
In-Reply-To: <96af4bbc-255e-47e2-b038-8c0d4bc21320@intel.com>
On 22.06.2024 00:44, Belgaumkar, Vinay wrote:
>
> On 6/21/2024 10:00 AM, Michal Wajdeczko wrote:
>> We have already marked the GuC PC feature as not applicable for
>> VF devices, but we missed the fact that there may be still some
>> privileged activities performed by this component, who does much
>> more than its name suggests.
>>
>> Explicitly skip xe_guc_pc_start() if running as a VF driver and
>> use a GT oriented message to report any error.
>
> We may need to skip in the xe_guc_stop function as well..
>
> void xe_guc_stop_prepare(struct xe_guc *guc)
> {
> XE_WARN_ON(xe_guc_pc_stop(&guc->pc));
> }
hmm, in xe_guc_pc_stop() we defer to gtidle if skip_guc_pc flag is set,
where we already have a VF guard, so it should be harmless, but yeah,
maybe for the completeness we should skip that call here too
Thanks
>
> Thanks,
>
> Vinay.
>
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>> Cc: Matthew Brost <matthew.brost@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_guc.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
>> index 172b65a50e31..79931466e479 100644
>> --- a/drivers/gpu/drm/xe/xe_guc.c
>> +++ b/drivers/gpu/drm/xe/xe_guc.c
>> @@ -1125,10 +1125,13 @@ void xe_guc_stop(struct xe_guc *guc)
>> int xe_guc_start(struct xe_guc *guc)
>> {
>> - int ret;
>> + if (!IS_SRIOV_VF(guc_to_xe(guc))) {
>> + int err;
>> - ret = xe_guc_pc_start(&guc->pc);
>> - XE_WARN_ON(ret);
>> + err = xe_guc_pc_start(&guc->pc);
>> + xe_gt_WARN(guc_to_gt(guc), err, "Failed to start GuC PC: %pe\n",
>> + ERR_PTR(err));
>> + }
>> return xe_guc_submit_start(guc);
>> }
prev parent reply other threads:[~2024-06-22 9:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 17:00 [PATCH] drm/xe/vf: Skip attempt to start GuC PC if VF Michal Wajdeczko
2024-06-21 17:05 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-21 17:05 ` ✓ CI.checkpatch: " Patchwork
2024-06-21 17:06 ` ✓ CI.KUnit: " Patchwork
2024-06-21 17:18 ` ✓ CI.Build: " Patchwork
2024-06-21 17:21 ` ✗ CI.Hooks: failure " Patchwork
2024-06-21 17:22 ` ✓ CI.checksparse: success " Patchwork
2024-06-21 17:45 ` ✓ CI.BAT: " Patchwork
2024-06-21 18:42 ` ✗ CI.FULL: failure " Patchwork
2024-06-21 22:44 ` [PATCH] " Belgaumkar, Vinay
2024-06-22 9:34 ` Michal Wajdeczko [this message]
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=18cd3da8-60d7-453b-8fcf-4105cdae7665@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=vinay.belgaumkar@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