From: Christoph Manszewski <christoph.manszewski@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Christoph Manszewski" <christoph.manszewski@intel.com>
Subject: [PATCH i-g-t 0/2] Execute and validate 'write_on_exception' shader
Date: Wed, 25 Sep 2024 15:30:01 +0200 [thread overview]
Message-ID: <20240925133003.41959-1-christoph.manszewski@intel.com> (raw)
Hi,
this is a followup to the 'Test coverage for GPU debug support' series
which addresses the review feedback about 'write_on_excepton' shader
usage. Currently it is only used in a negative way thus we don't
ensure that it actually works as expected. This series changes that.
Thanks,
Christoph
Christoph Manszewski (2):
lib/gpgpu_shader: Add x_offset parameter for
gpgpu_shader__write_on_exception
tests/xe_exec_sip: Write on invalidinstr
lib/gpgpu_shader.c | 29 ++++++++------
lib/gpgpu_shader.h | 4 +-
lib/iga64_generated_codes.c | 77 ++++++++++++++++++-----------------
tests/intel/xe_exec_sip.c | 80 +++++++++++++++++++++++--------------
4 files changed, 108 insertions(+), 82 deletions(-)
--
2.34.1
next reply other threads:[~2024-09-25 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 13:30 Christoph Manszewski [this message]
2024-09-25 13:30 ` [PATCH i-g-t 1/2] lib/gpgpu_shader: Add x_offset parameter for gpgpu_shader__write_on_exception Christoph Manszewski
2024-10-01 15:07 ` Zbigniew Kempczyński
2024-10-04 12:24 ` Manszewski, Christoph
2024-10-14 13:49 ` Hajda, Andrzej
2024-10-16 5:09 ` Zbigniew Kempczyński
2024-09-25 13:30 ` [PATCH i-g-t 2/2] tests/xe_exec_sip: Write on invalidinstr Christoph Manszewski
2024-10-02 7:50 ` Zbigniew Kempczyński
2024-10-04 12:26 ` Manszewski, Christoph
2024-09-26 6:37 ` ✗ Fi.CI.BAT: failure for Execute and validate 'write_on_exception' shader Patchwork
2024-09-26 6:55 ` ✗ CI.xeBAT: " Patchwork
2024-09-26 18:59 ` ✗ CI.xeFULL: " 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=20240925133003.41959-1-christoph.manszewski@intel.com \
--to=christoph.manszewski@intel.com \
--cc=andrzej.hajda@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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