All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Summers <stuart.summers@intel.com>
Cc: piotr.piorkowski@intel.com, michal.wajdeczko@intel.com,
	michal.winiarski@intel.com, intel-xe@lists.freedesktop.org,
	niranjana.vishwanathapura@intel.com,
	Stuart Summers <stuart.summers@intel.com>
Subject: [PATCH 0/2] Add support for LMTT specific invalidation
Date: Thu, 19 Mar 2026 21:31:04 +0000	[thread overview]
Message-ID: <20260319213110.259170-1-stuart.summers@intel.com> (raw)

Split this into a series from [1] to separate out the op
assert to apply to all TLB invalidation operations.

[1]: https://patchwork.freedesktop.org/series/163541/

Stuart Summers (2):
  drm/xe: Add an assert that the TLB invalidation op is available
  drm/xe: Add LMTT invalidation to VF provisioning flow

 drivers/gpu/drm/xe/abi/guc_actions_abi.h   |  2 ++
 drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c |  6 +++---
 drivers/gpu/drm/xe/xe_guc_tlb_inval.c      | 18 ++++++++++++++++++
 drivers/gpu/drm/xe/xe_lmtt.c               | 16 +++++++++++-----
 drivers/gpu/drm/xe/xe_lmtt.h               |  2 +-
 drivers/gpu/drm/xe/xe_tlb_inval.c          | 21 +++++++++++++++++++++
 drivers/gpu/drm/xe/xe_tlb_inval.h          |  3 +++
 drivers/gpu/drm/xe/xe_tlb_inval_types.h    | 12 ++++++++++++
 8 files changed, 71 insertions(+), 9 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-03-19 21:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 21:31 Stuart Summers [this message]
2026-03-19 21:31 ` [PATCH 1/2] drm/xe: Add an assert that the TLB invalidation op is available Stuart Summers
2026-03-19 21:31 ` [PATCH 2/2] drm/xe: Add LMTT invalidation to VF provisioning flow Stuart Summers
2026-03-19 22:51 ` ✓ CI.KUnit: success for Add support for LMTT specific invalidation Patchwork
2026-03-19 23:25 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-20 21:54 ` ✗ Xe.CI.FULL: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2026-03-20 20:54 [PATCH 0/2] " Stuart Summers

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=20260319213110.259170-1-stuart.summers@intel.com \
    --to=stuart.summers@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=niranjana.vishwanathapura@intel.com \
    --cc=piotr.piorkowski@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 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.