From: Jani Nikula <jani.nikula@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
vitaly.prosyak@amd.com
Cc: igt-dev@lists.freedesktop.org,
"Jesse Zhang" <jesse.zhang@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>
Subject: Re: [PATCH 3/7] lib/amdgpu: Add AMD platform filtering backend
Date: Thu, 02 Jul 2026 16:48:10 +0300 [thread overview]
Message-ID: <448ec82f897ee4a3f7a2ab9bcae2e1734d9349a2@intel.com> (raw)
In-Reply-To: <20260702134233.joyngzudno5jenk7@kamilkon-DESK.igk.intel.com>
On Thu, 02 Jul 2026, Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
> Hi vitaly.prosyak,
> On 2026-06-29 at 23:23:22 -0400, vitaly.prosyak@amd.com wrote:
>> From: Vitaly Prosyak <vitaly.prosyak@amd.com>
>>
>> Implement the AMD-specific backend for the generic platform filtering
>> framework, providing:
>>
>> - ASIC identification via amdgpu family_id and chip_rev ranges
>> - ASIC name table mapping (navi10, navi48, arcturus, etc.)
>> - AMD-specific built-in skip rules
>> - amd_platform_filter_init() convenience function for AMD tests
>>
>> This is a pluggable backend accessed through platform_filter_ops
>> callbacks. The core framework has zero AMD-specific knowledge.
>>
>> To add support for another vendor (e.g., Intel):
>> 1. Create lib/i915/intel_platform.c/h
>> 2. Implement platform_filter_ops callbacks
>> 3. Define Intel platform data (platform_id, stepping ranges)
>> 4. Call intel_platform_filter_init() from Intel tests
>>
>> Usage in AMD tests:
>> amd_platform_filter_init(&gpu_info);
>> igt_platform_require(igt_test_name(), "my-subtest");
>>
>> Example skip via environment variable:
>> export IGT_PLATFORM_SKIP_CONFIG=navi48:amd_basic:*-UMQ:unstable
>>
>> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: Jesse Zhang <jesse.zhang@amd.com>
>> Cc: Christian König <christian.koenig@amd.com>
>> Cc: Alex Deucher <alexander.deucher@amd.com>
>> Signed-off-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
>> Reviewed-by: Jesse Zhang <jesse.zhang@amd.com>
>> ---
>> lib/amdgpu/amd_platform.c | 318 ++++++++++++++++++++++++++++++++++++++
>> lib/amdgpu/amd_platform.h | 53 +++++++
>> lib/meson.build | 1 +
>> 3 files changed, 372 insertions(+)
>> create mode 100644 lib/amdgpu/amd_platform.c
>> create mode 100644 lib/amdgpu/amd_platform.h
>
> Please make sure that you patch series compile patch after patch,
> so it will not break bisecting. For example run:
>
> git rebase origin -x ./compile.sh
>
> with script which will remove build folder before each build.
Why should the build folder be removed? Is there reason to believe
dependency tracking and incremental builds are failing?
I only ever do git rebase -i origin -x 'ninja -C build'.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-07-02 13:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 3:23 [PATCH 1/7] lib: Add vendor-agnostic platform filtering interface vitaly.prosyak
2026-06-30 3:23 ` [PATCH 2/7] lib: Implement generic platform filtering framework vitaly.prosyak
2026-07-01 14:38 ` Krzysztof Karas
2026-07-02 12:30 ` Kamil Konieczny
2026-07-02 17:25 ` Kamil Konieczny
2026-06-30 3:23 ` [PATCH 3/7] lib/amdgpu: Add AMD platform filtering backend vitaly.prosyak
2026-07-02 13:42 ` Kamil Konieczny
2026-07-02 13:48 ` Jani Nikula [this message]
2026-07-06 13:46 ` Kamil Konieczny
2026-06-30 3:23 ` [PATCH 4/7] lib: Add platform filter initialization check for automatic filtering vitaly.prosyak
2026-06-30 3:23 ` [PATCH 5/7] lib/igt_core: Enable automatic platform filtering in subtest execution vitaly.prosyak
2026-06-30 3:23 ` [PATCH 6/7] docs: Add comprehensive platform filtering documentation vitaly.prosyak
2026-07-02 8:26 ` Krzysztof Karas
2026-06-30 3:23 ` [PATCH 7/7] tests/amdgpu: Integrate platform filtering into amd_basic vitaly.prosyak
2026-06-30 4:06 ` ✓ Xe.CI.BAT: success for series starting with [1/7] lib: Add vendor-agnostic platform filtering interface Patchwork
2026-06-30 4:17 ` ✓ i915.CI.BAT: " Patchwork
2026-06-30 13:14 ` ✗ i915.CI.Full: failure " Patchwork
2026-06-30 17:19 ` ✗ Xe.CI.FULL: " Patchwork
2026-07-02 12:23 ` [PATCH 1/7] " Kamil Konieczny
-- strict thread matches above, loose matches on Subject: below --
2026-07-03 14:08 vitaly.prosyak
2026-07-03 14:08 ` [PATCH 3/7] lib/amdgpu: Add AMD platform filtering backend 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=448ec82f897ee4a3f7a2ab9bcae2e1734d9349a2@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jesse.zhang@amd.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=vitaly.prosyak@amd.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