Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: Gustavo Sousa <gustavo.sousa@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH v3 0/8] Fix rtp when processing OOB workarounds
Date: Fri, 26 Jul 2024 18:58:59 -0700	[thread overview]
Message-ID: <20240727015907.899192-1-lucas.demarchi@intel.com> (raw)

The one line fix has already been merged in v2. This v3 has the
remaining improvements to tests and refactors.

v2:
  - Fix build due to missing change
  - Add tests for xe_rtp_process()
v3:
  - Use same media version as the BMG in CI for testing workarounds
    (Gustavo)
  - Change the loop style when counting rtp entries so there's only one
    variable needed. I went with a while() loop, slightly different than
    the suggested by Gustavo
  - Add 2 patches at the end to unify the ORed entries between the
    normal rtp entries and the ones used by OOB WAs (Gustavo)

Lucas De Marchi (8):
  drm/xe/kunit: Test WAs for BMG
  drm/xe/kunit: Rename count to count_sr_entries
  drm/xe/kunit: Test active rtp entries
  drm/xe/kunit: Rename rtp test cases
  drm/xe/kunit: Test rtp with no actions
  drm/xe/rtp: Simplify marking active workarounds
  drm/xe/rtp: Expand max rules/actions per entry again
  drm/xe: Migrate OOB WAs to OR rules

 drivers/gpu/drm/xe/tests/xe_rtp_test.c | 219 ++++++++++++++++++++++---
 drivers/gpu/drm/xe/tests/xe_wa_test.c  |   1 +
 drivers/gpu/drm/xe/xe_gen_wa_oob.c     |  16 +-
 drivers/gpu/drm/xe/xe_rtp.c            |  42 ++---
 drivers/gpu/drm/xe/xe_rtp.h            |   4 +-
 drivers/gpu/drm/xe/xe_rtp_helpers.h    |   6 +
 6 files changed, 230 insertions(+), 58 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-07-27  1:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-27  1:58 Lucas De Marchi [this message]
2024-07-27  1:59 ` [PATCH v3 1/8] drm/xe/kunit: Test WAs for BMG Lucas De Marchi
2024-07-29 14:28   ` Gustavo Sousa
2024-07-27  1:59 ` [PATCH v3 2/8] drm/xe/kunit: Rename count to count_sr_entries Lucas De Marchi
2024-07-27  1:59 ` [PATCH v3 3/8] drm/xe/kunit: Test active rtp entries Lucas De Marchi
2024-07-27  1:59 ` [PATCH v3 4/8] drm/xe/kunit: Rename rtp test cases Lucas De Marchi
2024-07-27  1:59 ` [PATCH v3 5/8] drm/xe/kunit: Test rtp with no actions Lucas De Marchi
2024-07-27  1:59 ` [PATCH v3 6/8] drm/xe/rtp: Simplify marking active workarounds Lucas De Marchi
2024-07-27  1:59 ` [PATCH v3 7/8] drm/xe/rtp: Expand max rules/actions per entry again Lucas De Marchi
2024-07-29 14:38   ` Gustavo Sousa
2024-07-29 14:42     ` Lucas De Marchi
2024-07-27  1:59 ` [PATCH v3 8/8] drm/xe: Migrate OOB WAs to OR rules Lucas De Marchi
2024-07-29 17:03   ` Gustavo Sousa
2024-07-27  2:57 ` ✓ CI.Patch_applied: success for Fix rtp when processing OOB workarounds (rev4) Patchwork
2024-07-27  2:57 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-27  2:58 ` ✓ CI.KUnit: success " Patchwork
2024-07-27  3:10 ` ✓ CI.Build: " Patchwork
2024-07-27  3:12 ` ✓ CI.Hooks: " Patchwork
2024-07-27  3:14 ` ✓ CI.checksparse: " Patchwork
2024-07-27 13:21 ` ✗ CI.FULL: failure " Patchwork
2024-07-29  5:34 ` ✓ CI.BAT: success " 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=20240727015907.899192-1-lucas.demarchi@intel.com \
    --to=lucas.demarchi@intel.com \
    --cc=gustavo.sousa@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