From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: kamil.konieczny@linux.intel.com, adam.miszczak@linux.intel.com,
jakub1.kolakowski@intel.com, lukasz.laguna@intel.com,
michal.wajdeczko@intel.com, michal.winiarski@intel.com,
narasimha.c.v@intel.com, piotr.piorkowski@intel.com,
satyanarayana.k.v.p@intel.com, tomasz.lis@intel.com,
Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
Subject: [PATCH v2 i-g-t 0/3] Improvements for xe_sriov_flr test and xe_mmio lib
Date: Wed, 20 Nov 2024 18:37:46 +0100 [thread overview]
Message-ID: <20241120173749.348843-1-marcin.bernatowicz@linux.intel.com> (raw)
Enhance code maintainability, improve error handling, and provide clearer
debugging information.
lib/xe/xe_mmio: Replace open-coded init/cleanup with existing functions
Use intel_register_access_init and intel_register_access_fini to handle
initialization and cleanup, reducing code duplication. This improves
maintainability and ensures consistency, including handling forcewake
for Xe.
lib/xe/xe_sriov_provisioning: Refactor range handling and logging
Introduce an append_range helper to reduce code duplication in handling
provisioned PTE ranges. Limit debug logs to the first 70 entries for
clarity and improved reasoning. Enhance error handling by propagating
realloc failures.
tests/xe/xe_sriov_flr: Use SKIP for unmet subcheck prerequisites
Handle missing prerequisites by marking subchecks as SKIP instead of FAIL.
This avoids misleading results suggesting FLR issues when tests haven't
started or conditions aren't met.
v2: Handle missing prerequisites by consistently marking subchecks as
SKIP instead of FAIL when conditions aren't met. (Lukasz)
Update range-checking logic to iterate only within valid PTE offsets
based on MAX_WOPCM_SIZE and GUC_GGTT_TOP.
Marcin Bernatowicz (3):
lib/xe/xe_mmio: Replace open-coded init/cleanup with existing
functions
lib/xe/xe_sriov_provisioning: Refactor range handling and logging
tests/xe/xe_sriov_flr: Use SKIP for unmet subcheck prerequisites
lib/xe/xe_mmio.c | 10 +----
lib/xe/xe_sriov_provisioning.c | 78 +++++++++++++++++++++++-----------
tests/intel/xe_sriov_flr.c | 21 +++++----
3 files changed, 68 insertions(+), 41 deletions(-)
--
2.31.1
next reply other threads:[~2024-11-20 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 17:37 Marcin Bernatowicz [this message]
2024-11-20 17:37 ` [PATCH v2 i-g-t 1/3] lib/xe/xe_mmio: Replace open-coded init/cleanup with existing functions Marcin Bernatowicz
2024-11-20 17:37 ` [PATCH v2 i-g-t 2/3] lib/xe/xe_sriov_provisioning: Refactor range handling and logging Marcin Bernatowicz
2024-11-20 17:37 ` [PATCH v2 i-g-t 3/3] tests/xe/xe_sriov_flr: Use SKIP for unmet subcheck prerequisites Marcin Bernatowicz
2024-11-20 19:24 ` ✓ Fi.CI.BAT: success for Improvements for xe_sriov_flr test and xe_mmio lib (rev2) Patchwork
2024-11-21 3:36 ` ✗ Xe.CI.Full: failure " Patchwork
2024-11-23 22:50 ` ✗ i915.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=20241120173749.348843-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=kamil.konieczny@linux.intel.com \
--cc=lukasz.laguna@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@intel.com \
--cc=narasimha.c.v@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=satyanarayana.k.v.p@intel.com \
--cc=tomasz.lis@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