From: Anna Karas <anna.karas@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Joonas Lahtinen <joonas.lahtinen@intel.com>,
Maarten Lankhorst <maarten.lankhorst@intel.com>
Subject: [igt-dev] [RFC 0/2] lib/xe_gpu: Introduce xe_gpu library
Date: Thu, 20 Apr 2023 21:14:52 +0200 [thread overview]
Message-ID: <20230420191454.497237-1-anna.karas@intel.com> (raw)
OPENS:
1. Lack of wedged concept in XE: @Matthew informed me that there is no
intent to have reporting wedged device in XE. However, @Joonas believes
that it may be useful - "it's used at least in specific diagnostics and
hardware repair flows for PVC and FLR for all platforms, where we
prevent further accesses to the hardware. So an alternative mechanism is
needed for those". Since xe_require_gpu() is a direct port of i915's
igt_require_gem() stripped of wedged device reporting, this could be a
good opportunity to discuss this.
2. igt_require_gem() was also responsible for restoring reset and
enable_hangcheck modparams. Do we need those parameters here? Do/will we
need different ones do restore?
3. Would you find adding equivalent of gem_quiescent_gpu here worth?
Reference: Jira VLK-46235
Signed-off-by: Anna Karas <anna.karas@intel.com>
Anna Karas (2):
lib/xe_gpu: Introduce xe_gpu library
tests/xe: Use xe_require_gpu() in existing tests
lib/meson.build | 1 +
lib/xe/xe_gpu.c | 136 ++++++++++++++++++++++++++++++++
lib/xe/xe_gpu.h | 19 +++++
tests/xe/xe_compute.c | 2 +
tests/xe/xe_create.c | 2 +
tests/xe/xe_debugfs.c | 2 +
tests/xe/xe_dma_buf_sync.c | 2 +
tests/xe/xe_evict.c | 2 +
tests/xe/xe_exec_balancer.c | 2 +
tests/xe/xe_exec_basic.c | 2 +
tests/xe/xe_exec_compute_mode.c | 2 +
tests/xe/xe_exec_fault_mode.c | 2 +
tests/xe/xe_exec_reset.c | 2 +
tests/xe/xe_exec_threads.c | 2 +
tests/xe/xe_guc_pc.c | 2 +
tests/xe/xe_huc_copy.c | 2 +
tests/xe/xe_mmap.c | 2 +
tests/xe/xe_mmio.c | 2 +
tests/xe/xe_noexec_ping_pong.c | 2 +
tests/xe/xe_pm.c | 2 +
tests/xe/xe_prime_self_import.c | 2 +
tests/xe/xe_query.c | 2 +
tests/xe/xe_vm.c | 2 +
tests/xe/xe_waitfence.c | 2 +
24 files changed, 198 insertions(+)
create mode 100644 lib/xe/xe_gpu.c
create mode 100644 lib/xe/xe_gpu.h
--
2.25.1
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
Spolka oswiadcza, ze posiada status duzego przedsiebiorcy w rozumieniu ustawy z dnia 8 marca 2013 r. o przeciwdzialaniu nadmiernym opoznieniom w transakcjach handlowych.
Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.
next reply other threads:[~2023-04-20 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 19:14 Anna Karas [this message]
2023-04-20 19:14 ` [igt-dev] [RFC 1/2] lib/xe_gpu: Introduce xe_gpu library Anna Karas
2023-04-21 7:56 ` Zbigniew Kempczyński
2023-05-15 9:51 ` Manszewski, Christoph
2023-05-15 18:01 ` Karas, Anna
2023-04-20 19:14 ` [igt-dev] [RFC 2/2] tests/xe: Use xe_require_gpu() in existing tests Anna Karas
2023-04-20 20:38 ` [igt-dev] [RFC 0/2] lib/xe_gpu: Introduce xe_gpu library Souza, Jose
2023-04-24 11:38 ` Karas, Anna
2023-04-25 3:41 ` Zbigniew Kempczyński
2023-04-20 20:58 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-21 5:28 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20230420191454.497237-1-anna.karas@intel.com \
--to=anna.karas@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=joonas.lahtinen@intel.com \
--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