From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: Jonathan Cavitt <jonathan.cavitt@intel.com>
Subject: Re: [PATCH 2/2] drm/xe/guc_pc: Remove duplicated pc_start call
Date: Thu, 13 Feb 2025 16:31:45 -0800 [thread overview]
Message-ID: <c458f5c6-6c54-46f1-b4a7-610d82600a73@intel.com> (raw)
In-Reply-To: <20250211200911.199213-2-rodrigo.vivi@intel.com>
On 2/11/2025 12:09 PM, Rodrigo Vivi wrote:
> xe_guc_pc_start() was getting called from both
> xe_uc_init_hw() and from xe_guc_start().
>
> But both are called from do_gt_restart() and only
> xe_uc_init_hw() is called at initialization.
>
> So, let's remove the duplication in the regular gt_restart
> path.
>
> The only place where xe_guc_pc_start() won't get called now
> is on the gt_reset failure path. However, if gt_reset has
> failed, it is really unlikely that the PC start will work
> or is desired.
LGTM,
Reviewed-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>
> Cc: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 1619c0a52db9..eaa035b25aa8 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -1491,14 +1491,6 @@ void xe_guc_stop(struct xe_guc *guc)
>
> int xe_guc_start(struct xe_guc *guc)
> {
> - if (!IS_SRIOV_VF(guc_to_xe(guc))) {
> - int err;
> -
> - 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);
> }
>
next prev parent reply other threads:[~2025-02-14 0:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 20:09 [PATCH 1/2] drm/xe/guc_pc: Do not stop probe or resume if GuC PC fails Rodrigo Vivi
2025-02-11 20:09 ` [PATCH 2/2] drm/xe/guc_pc: Remove duplicated pc_start call Rodrigo Vivi
2025-02-14 0:31 ` Belgaumkar, Vinay [this message]
2025-02-11 20:17 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe/guc_pc: Do not stop probe or resume if GuC PC fails Patchwork
2025-02-11 20:18 ` ✓ CI.checkpatch: " Patchwork
2025-02-11 20:19 ` ✓ CI.KUnit: " Patchwork
2025-02-11 20:35 ` ✓ CI.Build: " Patchwork
2025-02-11 20:37 ` ✓ CI.Hooks: " Patchwork
2025-02-11 20:39 ` ✓ CI.checksparse: " Patchwork
2025-02-11 20:59 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-12 1:19 ` [PATCH 1/2] " Belgaumkar, Vinay
2025-02-12 18:15 ` Rodrigo Vivi
2025-02-14 1:37 ` Belgaumkar, Vinay
2025-02-14 15:00 ` Rodrigo Vivi
2025-02-14 17:22 ` Belgaumkar, Vinay
2025-02-12 4:48 ` ✗ Xe.CI.Full: failure for series starting with [1/2] " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-02-14 17:25 [PATCH 1/2] " Rodrigo Vivi
2025-02-14 17:25 ` [PATCH 2/2] drm/xe/guc_pc: Remove duplicated pc_start call Rodrigo Vivi
2025-02-10 21:07 [PATCH 1/2] drm/xe/guc_pc: Do not stop probe or resume if GuC PC fails Rodrigo Vivi
2025-02-10 21:07 ` [PATCH 2/2] drm/xe/guc_pc: Remove duplicated pc_start call Rodrigo Vivi
2025-02-10 22:04 ` Cavitt, Jonathan
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=c458f5c6-6c54-46f1-b4a7-610d82600a73@intel.com \
--to=vinay.belgaumkar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=rodrigo.vivi@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