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: Lucas De Marchi <lucas.demarchi@intel.com>, maarten.lankhorst@intel.com
Subject: [Intel-xe] [PATCH 0/7] Unit tests for rtp and GT wa/tuning
Date: Tue, 21 Mar 2023 15:05:20 -0700	[thread overview]
Message-ID: <20230321220527.595462-1-lucas.demarchi@intel.com> (raw)

Add tests for the RTP infra and for the GT workaround/tuning
programming, while building the unit test infra to be able to test with
fake devices. This supersedes previous patch with only the rtp
tests (https://lore.kernel.org/intel-xe/20230316210341.3547058-1-lucas.demarchi@intel.com/T/#m1fd17b976409805f74aaeb565a441d7d63e0553d)

Notes:

- I debated a little bit whether we should use "mock" or "fake" to name
  these helpers for running without real hardware.  Here it's using
  "fake" since it's not a proper mock framework, and it seems to be what
  kunit itself uses in the documentation and examples.
- The tests themselves are "unit tests", for the
  software part, testing the implementation for the rtp,
  reg-save-restore and WA infrastructure.
- Last patch is the big improvement functonality-wise, which will help
  us detect wrong updates in the workaround tables, without running in
  real hardware.  That patches should be followed up with similar ones
  for the other WAs: engine and LRC.

Lucas De Marchi (7):
  drm/xe: Add basic unit tests for rtp
  drm/xe: Extract function to initialize xe->info
  drm/xe: Move test infra out of xe_pci.[ch]
  drm/xe: Use XE_KUNIT for symbol namespace
  drm/xe: Generalize fake device creation
  drm/xe/reg_sr: Save errors for kunit integration
  drm/xe: Add test for GT workarounds and tunings

 drivers/gpu/drm/xe/Kconfig.debug           |   1 +
 drivers/gpu/drm/xe/tests/Makefile          |   8 +-
 drivers/gpu/drm/xe/tests/xe_bo.c           |   6 +-
 drivers/gpu/drm/xe/tests/xe_bo_test.c      |   1 +
 drivers/gpu/drm/xe/tests/xe_dma_buf.c      |   3 +-
 drivers/gpu/drm/xe/tests/xe_dma_buf_test.c |   1 +
 drivers/gpu/drm/xe/tests/xe_migrate.c      |   3 +-
 drivers/gpu/drm/xe/tests/xe_migrate_test.c |   1 +
 drivers/gpu/drm/xe/tests/xe_pci.c          | 108 +++++++++++
 drivers/gpu/drm/xe/tests/xe_pci_test.h     |  31 ++++
 drivers/gpu/drm/xe/tests/xe_rtp.c          | 201 +++++++++++++++++++++
 drivers/gpu/drm/xe/tests/xe_rtp_test.c     |  64 +++++++
 drivers/gpu/drm/xe/tests/xe_rtp_test.h     |  15 ++
 drivers/gpu/drm/xe/tests/xe_wa_test.c      | 136 ++++++++++++++
 drivers/gpu/drm/xe/xe_pci.c                | 150 ++++++---------
 drivers/gpu/drm/xe/xe_pci.h                |   9 -
 drivers/gpu/drm/xe/xe_reg_sr.c             |   9 +
 drivers/gpu/drm/xe/xe_reg_sr_types.h       |   4 +
 drivers/gpu/drm/xe/xe_rtp.c                |   4 +
 drivers/gpu/drm/xe/xe_tuning.c             |   1 +
 drivers/gpu/drm/xe/xe_wa.c                 |   1 +
 21 files changed, 647 insertions(+), 110 deletions(-)
 create mode 100644 drivers/gpu/drm/xe/tests/xe_pci.c
 create mode 100644 drivers/gpu/drm/xe/tests/xe_pci_test.h
 create mode 100644 drivers/gpu/drm/xe/tests/xe_rtp.c
 create mode 100644 drivers/gpu/drm/xe/tests/xe_rtp_test.c
 create mode 100644 drivers/gpu/drm/xe/tests/xe_rtp_test.h
 create mode 100644 drivers/gpu/drm/xe/tests/xe_wa_test.c

-- 
2.39.0


             reply	other threads:[~2023-03-21 22:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 22:05 Lucas De Marchi [this message]
2023-03-21 22:05 ` [Intel-xe] [PATCH 1/7] drm/xe: Add basic unit tests for rtp Lucas De Marchi
2023-03-27 17:56   ` Michał Winiarski
2023-03-31 13:43     ` Lucas De Marchi
2023-04-01  8:59       ` Lucas De Marchi
2023-04-01 18:54         ` Michał Winiarski
2023-04-02  1:24           ` Lucas De Marchi
2023-04-02 10:51             ` Michal Wajdeczko
2023-03-31 14:34     ` Lucas De Marchi
2023-04-01  8:54       ` Lucas De Marchi
2023-04-01 18:26         ` Michał Winiarski
2023-04-02  1:34           ` Lucas De Marchi
2023-04-02 11:17             ` Michal Wajdeczko
2023-04-02 21:54               ` Lucas De Marchi
2023-04-03  7:38                 ` Michal Wajdeczko
2023-04-03 13:02                   ` Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 2/7] drm/xe: Extract function to initialize xe->info Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 3/7] drm/xe: Move test infra out of xe_pci.[ch] Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 4/7] drm/xe: Use XE_KUNIT for symbol namespace Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 5/7] drm/xe: Generalize fake device creation Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 6/7] drm/xe/reg_sr: Save errors for kunit integration Lucas De Marchi
2023-03-27 18:29   ` Michał Winiarski
2023-03-31 14:43     ` Lucas De Marchi
2023-03-21 22:05 ` [Intel-xe] [PATCH 7/7] drm/xe: Add test for GT workarounds and tunings Lucas De Marchi
2023-03-21 22:08 ` [Intel-xe] ✓ CI.Patch_applied: success for Unit tests for rtp and GT wa/tuning Patchwork
2023-03-31 15:14   ` Lucas De Marchi
2023-04-03  6:08     ` Mauro Carvalho Chehab
2023-03-21 22:09 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-21 22:13 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-21 22:25 ` [Intel-xe] ○ CI.BAT: info " 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=20230321220527.595462-1-lucas.demarchi@intel.com \
    --to=lucas.demarchi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten.lankhorst@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