Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH v2 0/4] PF: Add handling for new adverse event thresholds
Date: Mon, 15 Dec 2025 17:19:07 -0800	[thread overview]
Message-ID: <aUCzixblT//8+U3j@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20251215143739.196336-1-michal.wajdeczko@intel.com>

On Mon, Dec 15, 2025 at 03:37:35PM +0100, Michal Wajdeczko wrote:
> We want to extend our macro-based KLV list definitions with new
> information about the version from which given KLV is supported.
> 
> Instead of using magic version like 0.0.0 for legacy KLVs, add
> utility IF_ARGS macro that can be used in code generators to emit
> different code based on the presence of any additional arguments.
> 
> This series cherry-picks one patch from the EGS series [1] and
> can be merged separately.
> 
> v1: https://patchwork.freedesktop.org/series/158874/#rev1
> v2: new patch with GUC_FIRMWARE_VER_AT_LEAST macro
> 
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> 
> [1] https://patchwork.freedesktop.org/series/158142/#rev3
> 
> Daniele Ceraolo Spurio (1):
>   drm/xe/pf: Add handling for MLRC adverse event threshold
> 

For the series:
Acked-by: Matthew Brost <matthew.brost@intel.com>

> Michal Wajdeczko (3):
>   drm/xe: Introduce IF_ARGS macro utility
>   drm/xe/guc: Introduce GUC_FIRMWARE_VER_AT_LEAST helper
>   drm/xe/pf: Prepare for new threshold KLVs
> 
>  drivers/gpu/drm/xe/abi/guc_klvs_abi.h         |  9 ++++
>  drivers/gpu/drm/xe/tests/xe_args_test.c       | 53 +++++++++++++++++++
>  drivers/gpu/drm/xe/xe_args.h                  | 18 +++++++
>  drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c    | 19 ++++---
>  drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c   |  9 ++--
>  drivers/gpu/drm/xe/xe_gt_sriov_pf_migration.c |  2 +-
>  drivers/gpu/drm/xe/xe_guc.h                   | 21 ++++++++
>  drivers/gpu/drm/xe/xe_guc_ads.c               |  4 +-
>  .../drm/xe/xe_guc_klv_thresholds_set_types.h  |  6 +++
>  9 files changed, 128 insertions(+), 13 deletions(-)
> 
> -- 
> 2.47.1
> 

      parent reply	other threads:[~2025-12-16  1:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 14:37 [PATCH v2 0/4] PF: Add handling for new adverse event thresholds Michal Wajdeczko
2025-12-15 14:37 ` [PATCH v2 1/4] drm/xe: Introduce IF_ARGS macro utility Michal Wajdeczko
2025-12-15 15:50   ` Michal Wajdeczko
2025-12-15 14:37 ` [PATCH v2 2/4] drm/xe/guc: Introduce GUC_FIRMWARE_VER_AT_LEAST helper Michal Wajdeczko
2025-12-15 17:07   ` Michal Wajdeczko
2025-12-15 18:25   ` Daniele Ceraolo Spurio
2025-12-15 14:37 ` [PATCH v2 3/4] drm/xe/pf: Prepare for new threshold KLVs Michal Wajdeczko
2025-12-15 18:28   ` Daniele Ceraolo Spurio
2025-12-15 14:37 ` [PATCH v2 4/4] drm/xe/pf: Add handling for MLRC adverse event threshold Michal Wajdeczko
2025-12-15 14:57 ` ✗ CI.checkpatch: warning for PF: Add handling for new adverse event thresholds (rev2) Patchwork
2025-12-15 14:59 ` ✓ CI.KUnit: success " Patchwork
2025-12-15 16:03 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-15 19:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-12-16  1:19 ` Matthew Brost [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=aUCzixblT//8+U3j@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=daniele.ceraolospurio@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