From: Andrzej Hajda <andrzej.hajda@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Kamil Konieczny" <kamil.konieczny@linux.intel.com>,
"Dominik Grzegorzek" <dominik.grzegorzek@intel.com>,
"Christoph Manszewski" <christoph.manszewski@intel.com>,
"Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>
Subject: [PATCH v2 0/5] lib/gpgpu: add shader support
Date: Wed, 15 May 2024 11:14:59 +0200 [thread overview]
Message-ID: <20240515-iga64_inline_ups-v2-0-693743cb0985@intel.com> (raw)
This patchset adds shader support to mainline IGT.
Together with iga64 inline assembly and demo test using both.
The patches were cherry-picked/trimmed from internal branch,
quite painful process. I hope I have not cut off too much :)
To: igt-dev@lists.freedesktop.org
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: Dominik Grzegorzek <dominik.grzegorzek@intel.com>
Cc: Christoph Manszewski <christoph.manszewski@intel.com>
Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
Changes in v2:
- described in patches
- Link to v1: https://lore.kernel.org/r/20240429-iga64_inline_ups-v1-0-2e9ac46cf6ba@intel.com
---
Andrzej Hajda (5):
lib/gpu_cmds: add Xe_LP version of emit_vfe_state
lib/gpgpu_shader: tooling for preparing and running gpgpu shaders
lib/gpgpu_shader: add inline support for iga64 assembly
lib/igt_sysfs: add helpers to access engine sysfs directory
intel/xe_exec_sip: port test for shader sanity check
lib/generate_iga64_codes | 115 ++++++++++++++++
lib/gpgpu_shader.c | 313 ++++++++++++++++++++++++++++++++++++++++++++
lib/gpgpu_shader.h | 63 +++++++++
lib/gpu_cmds.c | 29 +++-
lib/gpu_cmds.h | 6 +
lib/iga64_generated_codes.c | 87 ++++++++++++
lib/iga64_macros.h | 11 ++
lib/igt_sysfs.c | 71 ++++++++++
lib/igt_sysfs.h | 3 +
lib/meson.build | 19 +++
tests/intel/xe_exec_sip.c | 195 +++++++++++++++++++++++++++
tests/meson.build | 1 +
12 files changed, 907 insertions(+), 6 deletions(-)
---
base-commit: be9b9992805df48e785b40ac2c4d001fb680a2c1
change-id: 20240425-iga64_inline_ups-438ddfd6023f
Best regards,
--
Andrzej Hajda <andrzej.hajda@intel.com>
next reply other threads:[~2024-05-15 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 9:14 Andrzej Hajda [this message]
2024-05-15 9:15 ` [PATCH v2 1/5] lib/gpu_cmds: add Xe_LP version of emit_vfe_state Andrzej Hajda
2024-05-15 9:15 ` [PATCH v2 2/5] lib/gpgpu_shader: tooling for preparing and running gpgpu shaders Andrzej Hajda
2024-05-15 9:15 ` [PATCH v2 3/5] lib/gpgpu_shader: add inline support for iga64 assembly Andrzej Hajda
2024-05-15 9:15 ` [PATCH v2 4/5] lib/igt_sysfs: add helpers to access engine sysfs directory Andrzej Hajda
2024-05-15 9:15 ` [PATCH v2 5/5] intel/xe_exec_sip: port test for shader sanity check Andrzej Hajda
2024-05-15 10:52 ` ✗ GitLab.Pipeline: warning for lib/gpgpu: add shader support (rev2) Patchwork
2024-05-16 12:34 ` Andrzej Hajda
2024-05-15 11:08 ` ✓ CI.xeBAT: success " Patchwork
2024-05-15 11:25 ` ✓ Fi.CI.BAT: " Patchwork
2024-05-15 12:07 ` ✗ CI.xeFULL: failure " Patchwork
2024-05-16 3:09 ` ✗ 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=20240515-iga64_inline_ups-v2-0-693743cb0985@intel.com \
--to=andrzej.hajda@intel.com \
--cc=christoph.manszewski@intel.com \
--cc=dominik.grzegorzek@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--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