Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: vitaly prosyak <vprosyak@amd.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: RE: [igt-dev] [PATCH] tests/amdgpu: Add KFD IOCTL fuzzing test - Apologies for build failures
Date: Thu, 7 May 2026 00:08:18 -0400	[thread overview]
Message-ID: <a243c8c9-7681-4633-a25a-2b01fa33a53a@amd.com> (raw)

Hi Kamil,

I apologize for the build failures in my recent amd_fuzzing_kfd patch series and the need for 3 additional fixup patches to address ARM cross-compilation issues.

The failures were due to:
1. Missing drm/drm.h include dependency on some systems
2. Incomplete KFD IOCTL struct definitions on ARM (forward declarations only)
3. KFD being x86/x86_64 specific (AMD GPUs not supported on ARM)

I've now submitted fixes that:
- Add proper header dependencies and guards
- Restrict KFD tests to x86/x86_64 architectures only in meson.build
- Follow the same pattern as amd_kfd_dmabuf_unload.c

I'm curious - is there a way to see build failure results from patchwork.freedesktop.org before patches are merged? I couldn't find build status information on the patchwork interface, but I'd like to catch these issues earlier in the future. If you could point me to where CI build results are posted, I would greatly appreciate it.

Sorry again for the extra churn, and thank you for maintaining IGT!

Best regards,
Vitaly 


             reply	other threads:[~2026-05-07  4:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07  4:08 vitaly prosyak [this message]
2026-05-14 15:06 ` [igt-dev] [PATCH] tests/amdgpu: Add KFD IOCTL fuzzing test - Apologies for build failures Kamil Konieczny
2026-05-14 17:59   ` vitaly prosyak

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=a243c8c9-7681-4633-a25a-2b01fa33a53a@amd.com \
    --to=vprosyak@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.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