Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: fei.yang@intel.com
To: intel-xe@lists.freedesktop.org
Cc: Fei Yang <fei.yang@intel.com>
Subject: [PATCH 0/1 v4] drm/xe: Wait for HW clearance before issuing the next TLB inval.
Date: Wed, 24 Jun 2026 15:51:03 -0700	[thread overview]
Message-ID: <20260624225105.2355641-1-fei.yang@intel.com> (raw)

From: Fei Yang <fei.yang@intel.com>

Attempt again after validating this in the internal tree for a while.
I hope this time it will pass the CI.
I knew Matt Brost wanted to have a GAM port layer for the mmio access,
but not sure if it worth the effort if the only usage is for MMIO-based
TLB invalidation.


Fei Yang (1):
  drm/xe: Wait for HW clearance before issuing the next TLB inval.

 drivers/gpu/drm/xe/xe_guc_tlb_inval.c | 70 +++++++++++++++++++++++++++
 1 file changed, 70 insertions(+)

-- 
2.43.0


             reply	other threads:[~2026-06-24 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24 22:51 fei.yang [this message]
2026-06-24 22:51 ` [PATCH 1/1 v4] drm/xe: Wait for HW clearance before issuing the next TLB inval fei.yang
2026-06-24 23:00 ` ✓ CI.KUnit: success for " Patchwork
2026-06-25  0:37 ` ✗ Xe.CI.BAT: 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=20260624225105.2355641-1-fei.yang@intel.com \
    --to=fei.yang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox