Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: [PATCH v5 0/3] GuC CT tweaks
Date: Mon, 22 Jan 2024 13:01:53 -0800	[thread overview]
Message-ID: <20240122210156.1517444-1-matthew.brost@intel.com> (raw)

Address some the issues discussed in [1].

v2: Rebase, address Michal's comments
v3: Rebase, address Michal's comments
v4: Rebase, address Michal's comments
v5: Fix CI

[1] https://patchwork.freedesktop.org/patch/572566/?series=127982&rev=1

Matthew Brost (3):
  drm/xe/guc: Add more GuC CT states
  drm/xe: Move TLB invalidation reset before HW reset
  drm/xe/guc: Flush G2H handler when turning off CTs

 drivers/gpu/drm/xe/xe_gt.c           |  4 +-
 drivers/gpu/drm/xe/xe_guc.c          |  4 +-
 drivers/gpu/drm/xe/xe_guc_ct.c       | 89 ++++++++++++++++++++++------
 drivers/gpu/drm/xe/xe_guc_ct.h       |  8 ++-
 drivers/gpu/drm/xe/xe_guc_ct_types.h | 18 +++++-
 5 files changed, 99 insertions(+), 24 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-01-22 21:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 21:01 Matthew Brost [this message]
2024-01-22 21:01 ` [PATCH v5 1/3] drm/xe/guc: Add more GuC CT states Matthew Brost
2024-01-22 21:01 ` [PATCH v5 2/3] drm/xe: Move TLB invalidation reset before HW reset Matthew Brost
2024-01-22 21:01 ` [PATCH v5 3/3] drm/xe/guc: Flush G2H handler when turning off CTs Matthew Brost
2024-01-22 21:04 ` ✓ CI.Patch_applied: success for GuC CT tweaks Patchwork
2024-01-22 21:04 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-22 21:05 ` ✓ CI.KUnit: success " Patchwork
2024-01-22 21:13 ` ✓ CI.Build: " Patchwork
2024-01-22 21:13 ` ✗ CI.Hooks: failure " Patchwork
2024-01-22 21:14 ` ✓ CI.checksparse: success " Patchwork
2024-01-22 21:38 ` ✓ CI.BAT: " 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=20240122210156.1517444-1-matthew.brost@intel.com \
    --to=matthew.brost@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