From: Andrzej Hajda <andrzej.hajda@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Kamil Konieczny" <kamil.konieczny@linux.intel.com>,
"Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>
Subject: [PATCH 0/2] lib/gpgpu_shader: GPU asm related changes
Date: Thu, 07 May 2026 17:15:39 +0200 [thread overview]
Message-ID: <20260507-switch_asms_to_raw_strings-v1-0-487fa0f9ea2f@intel.com> (raw)
Nothing fancy, just upstreaming.
Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
Andrzej Hajda (2):
scripts/generate_iga64_codes: add env variable to force asm rebuild
lib/gpgpu_shader: use raw strings in all asms
lib/gpgpu_fill.c | 86 ++--
lib/gpgpu_fill.c.gen.iga64_codes.c | 2 +-
lib/gpgpu_shader.c | 492 +++++++++++-----------
lib/gpgpu_shader.c.gen.iga64_codes.c | 2 +-
scripts/generate_iga64_codes | 2 +-
tests/intel/xe_prefetch_fault.c | 60 +--
tests/intel/xe_prefetch_fault.c.gen.iga64_codes.c | 2 +-
7 files changed, 323 insertions(+), 323 deletions(-)
---
base-commit: 3e5747e536f148bf232049e49a00e2b683f91a83
change-id: 20260507-switch_asms_to_raw_strings-0ee09dbb9971
Best regards,
--
Andrzej Hajda <andrzej.hajda@intel.com>
next reply other threads:[~2026-05-07 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 15:15 Andrzej Hajda [this message]
2026-05-07 15:15 ` [PATCH 1/2] scripts/generate_iga64_codes: add env variable to force asm rebuild Andrzej Hajda
2026-05-11 7:37 ` Zbigniew Kempczyński
2026-05-07 15:15 ` [PATCH 2/2] lib/gpgpu_shader: use raw strings in all asms Andrzej Hajda
2026-05-11 7:38 ` Zbigniew Kempczyński
2026-05-07 21:37 ` ✓ i915.CI.BAT: success for lib/gpgpu_shader: GPU asm related changes Patchwork
2026-05-07 22:01 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-08 9:55 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-08 14:00 ` ✓ i915.CI.Full: 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=20260507-switch_asms_to_raw_strings-v1-0-487fa0f9ea2f@intel.com \
--to=andrzej.hajda@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