All of lore.kernel.org
 help / color / mirror / Atom feed
From: "K V P, Satyanarayana" <satyanarayana.k.v.p@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] drm/xe/pf: Add the definition of VF resfix abort event
Date: Wed, 24 Jun 2026 17:32:42 +0530	[thread overview]
Message-ID: <19187bf0-1cdc-4e85-8d3f-db5893c5bbcd@intel.com> (raw)
In-Reply-To: <20260624095634.1250956-3-michal.winiarski@intel.com>


On 24-Jun-26 3:26 PM, Michał Winiarski wrote:
> The VF RESFIX_ABORT event is similar to FIXUP_DONE event, in that
> there's no handling required from PF perspective.
> Add the definition to avoid the "unrecognized event" message.
>
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
> ---
>   drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h | 2 ++
>   drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c    | 2 ++
>   2 files changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h b/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
> index 8665b8c5b7336..59c52b7c21ab6 100644
> --- a/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
> +++ b/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
> @@ -230,6 +230,7 @@
>    *  |   |       |   - _`GUC_PF_NOTIFY_VF_PAUSE_DONE` = 3                       |
>    *  |   |       |   - _`GUC_PF_NOTIFY_VF_FIXUP_DONE` = 4                       |
>    *  |   |       |   - _`GUC_PF_NOTIFY_VF_PAUSE_ABORTED` = 5                    |
> + *  |   |       |   - _`GUC_PF_NOTIFY_VF_RESFIX_ABORTED` = 6                   |
>    *  +---+-------+--------------------------------------------------------------+
>    */
>   #define GUC_ACTION_GUC2PF_VF_STATE_NOTIFY		0x5106u
> @@ -244,6 +245,7 @@
>   #define   GUC_PF_NOTIFY_VF_PAUSE_DONE			3u
>   #define   GUC_PF_NOTIFY_VF_FIXUP_DONE			4u
>   #define   GUC_PF_NOTIFY_VF_PAUSE_ABORTED		5u
> +#define   GUC_PF_NOTIFY_VF_RESFIX_ABORTED		6u
>   
>   /**
>    * DOC: VF2GUC_MATCH_VERSION
> 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 82957c596b683..2762fff78f113 100644
> --- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c
> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c
> @@ -1986,6 +1986,8 @@ static int pf_handle_vf_event(struct xe_gt *gt, u32 vfid, u32 eventid)
>   	case GUC_PF_NOTIFY_VF_PAUSE_ABORTED:
>   		pf_handle_vf_pause_aborted(gt, vfid);
>   		break;
> +	case GUC_PF_NOTIFY_VF_RESFIX_ABORTED:
> +		break;
Better to log a message if the event is not handled.
>   	default:
>   		xe_gt_sriov_notice(gt, "unrecognized VF%u event %#x\n", vfid, eventid);
>   	}

  reply	other threads:[~2026-06-24 12:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24  9:56 [PATCH 1/3] drm/xe/pf: Do not return an error for unrecognized VF events Michał Winiarski
2026-06-24  9:56 ` [PATCH 2/3] drm/xe/pf: Add support for VF Pause abort event Michał Winiarski
2026-06-24  9:56 ` [PATCH 3/3] drm/xe/pf: Add the definition of VF resfix " Michał Winiarski
2026-06-24 12:02   ` K V P, Satyanarayana [this message]
2026-06-24 10:02 ` ✗ CI.checkpatch: warning for series starting with [1/3] drm/xe/pf: Do not return an error for unrecognized VF events Patchwork
2026-06-24 10:03 ` ✓ CI.KUnit: success " Patchwork
2026-06-24 11:59 ` [PATCH 1/3] " K V P, Satyanarayana
2026-06-24 12:19 ` ✓ Xe.CI.BAT: success for series starting with [1/3] " Patchwork
2026-06-24 13:32 ` ✗ Xe.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=19187bf0-1cdc-4e85-8d3f-db5893c5bbcd@intel.com \
    --to=satyanarayana.k.v.p@intel.com \
    --cc=intel-xe@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.