Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 03/12] drm/xe/pf: Drop GuC notifications for non-existing VF
Date: Thu, 22 Aug 2024 12:48:40 +0200	[thread overview]
Message-ID: <20240822104840.u2gb5wlvfjhgx3yc@intel.com> (raw)
In-Reply-To: <de0bdc3e-d01b-4988-b369-99b7883b6416@intel.com>

Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on pon [2024-sie-19 19:51:28 +0200]:
> 
> 
> On 16.08.2024 15:01, Piotr Piórkowski wrote:
> > Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on pią [2024-sie-09 18:51:50 +0200]:
> >> It is unlikely that GuC will ever send a G2H notification with an
> >> invalid VFID and it is currently harmless if that actually happen.
> >> But in upcoming patches we will start using that VFID as an index
> >> and we must be sure it is a valid to avoid a crash due to a buggy
> >> firmware or a currupted G2H message.
> >>
> >> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> >> ---
> >>  drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c | 6 ++++++
> >>  1 file changed, 6 insertions(+)
> >>
> >> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c
> >> index d11839d9e7d4..ad447d867e51 100644
> >> --- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c
> >> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c
> >> @@ -8,6 +8,7 @@
> >>  #include "xe_device.h"
> >>  #include "xe_gt.h"
> >>  #include "xe_gt_sriov_pf_control.h"
> >> +#include "xe_gt_sriov_pf_helpers.h"
> >>  #include "xe_gt_sriov_printk.h"
> >>  #include "xe_guc_ct.h"
> >>  #include "xe_sriov.h"
> >> @@ -212,6 +213,11 @@ static void pf_handle_vf_flr_done(struct xe_gt *gt, u32 vfid)
> >>  
> >>  static int pf_handle_vf_event(struct xe_gt *gt, u32 vfid, u32 eventid)
> >>  {
> >> +	xe_gt_sriov_dbg_verbose(gt, "received VF%u event %#x\n", vfid, eventid);
> >> +
> >> +	if (vfid > xe_gt_sriov_pf_get_totalvfs(gt))
> >> +		return -EPROTO;
> > 
> > I would probably add some log here.
> > I'm afraid that during debug the information about the last event is not enough
> 
> it should be the CTB layer responsibility to print an error message and
> dump this invalid or corrupted or unexpected G2H message, no point in
> doing this in every possible G2H message handler; note that 'silent'
> return is aligned with the existing code in this file.
> 
> for now CTB will just report:
> 
> 	xe_gt_err(gt, "G2H action 0x%04x failed (%pe)\n",
> 		  action, ERR_PTR(ret));
> 
> but it should be easy to add (what we had in i915) full dump of the
> problematic G2H message in case of at least the EPROTO error


This sounds reasonable to me:
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
> 
> > 
> > Thanks,
> > Piotr
> >> +
> >>  	switch (eventid) {
> >>  	case GUC_PF_NOTIFY_VF_FLR:
> >>  		pf_handle_vf_flr(gt, vfid);
> >> -- 
> >> 2.43.0
> >>
> > 

-- 

  reply	other threads:[~2024-08-22 10:48 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09 16:51 [PATCH 00/12] PF: Improve VF control Michal Wajdeczko
2024-08-09 16:51 ` [PATCH 01/12] drm/xe/pf: Add function to sanitize VF resources Michal Wajdeczko
2024-08-16 12:58   ` Piotr Piórkowski
2024-08-19 20:47   ` Lucas De Marchi
2024-08-20  9:38     ` Michal Wajdeczko
2024-08-20 13:16       ` Lucas De Marchi
2024-09-05 18:07         ` Rodrigo Vivi
2024-08-09 16:51 ` [PATCH 02/12] drm/xe/pf: Fix documentation formatting Michal Wajdeczko
2024-08-16 12:59   ` Piotr Piórkowski
2024-08-09 16:51 ` [PATCH 03/12] drm/xe/pf: Drop GuC notifications for non-existing VF Michal Wajdeczko
2024-08-16 13:01   ` Piotr Piórkowski
2024-08-19 17:51     ` Michal Wajdeczko
2024-08-22 10:48       ` Piotr Piórkowski [this message]
2024-08-09 16:51 ` [PATCH 04/12] drm/xe/pf: Improve VF control Michal Wajdeczko
2024-08-16 13:06   ` Piotr Piórkowski
2024-08-19 17:52     ` Michal Wajdeczko
2024-08-20  7:56   ` Piotr Piórkowski
2024-08-20 10:04     ` Michal Wajdeczko
2024-08-09 16:51 ` [PATCH 05/12] drm/xe/tests: Allow deferred function call during KUnit test Michal Wajdeczko
2024-08-19 21:38   ` Lucas De Marchi
2024-08-20 10:23     ` Michal Wajdeczko
2024-08-20 13:21       ` Lucas De Marchi
2024-08-20 13:27       ` Lucas De Marchi
2024-08-09 16:51 ` [PATCH 06/12] drm/xe/tests: Add helper macro to detect if KUnit is running Michal Wajdeczko
2024-08-09 16:51 ` [PATCH 07/12] drm/xe/tests: Add helpers to call stubs out of KUnit context Michal Wajdeczko
2024-08-19 21:52   ` Lucas De Marchi
2024-08-20 10:31     ` Michal Wajdeczko
2024-08-09 16:51 ` [PATCH 08/12] drm/xe/guc: Define stub for xe_guc_ct_send_recv() Michal Wajdeczko
2024-08-09 16:51 ` [PATCH 09/12] drm/xe/pf: Define stub for pf_sanitize_vf_resources() Michal Wajdeczko
2024-08-09 16:51 ` [PATCH 10/12] drm/xe/pf: Define stub for pf_send_vf_control_cmd() Michal Wajdeczko
2024-08-09 16:51 ` [PATCH 11/12] drm/xe/tests: Add KUnit tests for VF control state machines Michal Wajdeczko
2024-08-09 17:23   ` [PATCH v2 " Michal Wajdeczko
2024-08-22 10:51     ` Piotr Piórkowski
2024-08-22 10:47   ` [PATCH " Piotr Piórkowski
2024-08-09 16:51 ` [PATCH 12/12] drm/xe/tests: Add KUnit tests for VF control GuC messages Michal Wajdeczko
2024-08-23 13:18   ` Piotr Piórkowski
2024-08-09 16:57 ` ✓ CI.Patch_applied: success for PF: Improve VF control Patchwork
2024-08-09 16:58 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-09 16:58 ` ✗ CI.KUnit: failure " Patchwork
2024-08-09 17:28 ` ✓ CI.Patch_applied: success for PF: Improve VF control (rev2) Patchwork
2024-08-09 17:29 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-09 17:30 ` ✓ CI.KUnit: success " Patchwork
2024-08-09 17:42 ` ✓ CI.Build: " Patchwork
2024-08-09 17:44 ` ✗ CI.Hooks: failure " Patchwork
2024-08-09 17:46 ` ✓ CI.checksparse: success " Patchwork
2024-08-09 18:06 ` ✓ CI.BAT: " Patchwork
2024-08-09 20:35 ` ✗ CI.FULL: failure " 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=20240822104840.u2gb5wlvfjhgx3yc@intel.com \
    --to=piotr.piorkowski@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