From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Marcin Bernatowicz" <marcin.bernatowicz@linux.intel.com>,
"Adam Miszczak" <adam.miszczak@linux.intel.com>,
"Jakub Kolakowski" <jakub1.kolakowski@intel.com>,
"Lukasz Laguna" <lukasz.laguna@intel.com>,
"Michał Wajdeczko" <michal.wajdeczko@intel.com>,
"Michał Winiarski" <michal.winiarski@intel.com>,
"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
"Satyanarayana K V P" <satyanarayana.k.v.p@intel.com>,
"Tomasz Lis" <tomasz.lis@intel.com>,
"Zhanjun Dong" <zhanjun.dong@intel.com>
Subject: [PATCH i-g-t 0/2] Add VF detection and skip devcoredump checks on VFs
Date: Wed, 19 Feb 2025 12:53:12 +0100 [thread overview]
Message-ID: <20250219115314.180382-1-marcin.bernatowicz@linux.intel.com> (raw)
This series introduces a helper function to detect whether a device is a
Virtual Function (VF) and updates the xe_exec_capture test to skip
devcoredump validation steps that are not applicable for VF devices.
The first patch adds intel_is_vf_device(), which reads the
VF_CAPABILITY_REGISTER to determine if a device is a VF.
The second patch integrates this check into xe_exec_capture,
ensuring that certain devcoredump checks are skipped on VFs.
These changes align with kernel updates introduced in:
Link: https://patchwork.freedesktop.org/patch/msgid/20241022010116.342240-2-zhanjun.dong@intel.com
Cc: Adam Miszczak <adam.miszczak@linux.intel.com>
Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
Cc: Lukasz Laguna <lukasz.laguna@intel.com>
Cc: Michał Wajdeczko <michal.wajdeczko@intel.com>
Cc: Michał Winiarski <michal.winiarski@intel.com>
Cc: Piotr Piórkowski <piotr.piorkowski@intel.com>
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Cc: Tomasz Lis <tomasz.lis@intel.com>
Cc: Zhanjun Dong <zhanjun.dong@intel.com>
Marcin Bernatowicz (2):
lib/igt_sriov_device: Add intel_is_vf_device helper
tests/xe_exec_capture: Skip checks on VF devices
lib/igt_sriov_device.c | 26 +++++++++++++++++++++++++
lib/igt_sriov_device.h | 1 +
tests/intel/xe_exec_capture.c | 36 ++++++++++++++++++++++-------------
3 files changed, 50 insertions(+), 13 deletions(-)
--
2.31.1
next reply other threads:[~2025-02-19 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 11:53 Marcin Bernatowicz [this message]
2025-02-19 11:53 ` [PATCH i-g-t 1/2] lib/igt_sriov_device: Add intel_is_vf_device helper Marcin Bernatowicz
2025-03-03 8:20 ` Laguna, Lukasz
2025-03-03 15:44 ` Bernatowicz, Marcin
2025-03-04 7:24 ` Laguna, Lukasz
2025-02-19 11:53 ` [PATCH i-g-t 2/2] tests/xe_exec_capture: Skip checks on VF devices Marcin Bernatowicz
2025-02-21 16:45 ` Dong, Zhanjun
2025-02-19 23:33 ` ✓ i915.CI.BAT: success for Add VF detection and skip devcoredump checks on VFs Patchwork
2025-02-19 23:50 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-20 11:30 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-20 21:58 ` ✗ Xe.CI.Full: " 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=20250219115314.180382-1-marcin.bernatowicz@linux.intel.com \
--to=marcin.bernatowicz@linux.intel.com \
--cc=adam.miszczak@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=lukasz.laguna@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=satyanarayana.k.v.p@intel.com \
--cc=tomasz.lis@intel.com \
--cc=zhanjun.dong@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