All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>,
	Jakub Kolakowski <jakub1.kolakowski@intel.com>,
	Riana Tauro <riana.tauro@intel.com>,
	Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Subject: [PATCH i-g-t 0/2] tests/intel/xe_pmu: Improve VF setup and cleanup
Date: Tue,  6 May 2025 12:15:52 +0200	[thread overview]
Message-ID: <20250506101554.629218-1-marcin.bernatowicz@linux.intel.com> (raw)

Improve VF-related setup and teardown in the xe_pmu test.
The changes ensure a clean environment before and after test execution.

Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
Cc: Riana Tauro <riana.tauro@intel.com>
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>

Marcin Bernatowicz (2):
  tests/intel/xe_pmu: Unprovision VFs on cleanup
  tests/intel/xe_pmu: Check default scheduling attributes before test

 tests/intel/xe_pmu.c | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

-- 
2.31.1


             reply	other threads:[~2025-05-06 10:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 10:15 Marcin Bernatowicz [this message]
2025-05-06 10:15 ` [PATCH i-g-t 1/2] tests/intel/xe_pmu: Unprovision VFs on cleanup Marcin Bernatowicz
2025-05-06 12:51   ` K V P, Satyanarayana
2025-05-06 13:05     ` Bernatowicz, Marcin
2025-05-06 13:37       ` K V P, Satyanarayana
2025-05-06 10:15 ` [PATCH i-g-t 2/2] tests/intel/xe_pmu: Check default scheduling attributes before test Marcin Bernatowicz
2025-05-06 12:53   ` K V P, Satyanarayana
2025-05-06 11:27 ` ✗ i915.CI.BAT: failure for tests/intel/xe_pmu: Improve VF setup and cleanup Patchwork
2025-05-06 11:32 ` ✓ Xe.CI.BAT: success " Patchwork
2025-05-06 13:00 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-12  8:07   ` Bernatowicz, Marcin

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=20250506101554.629218-1-marcin.bernatowicz@linux.intel.com \
    --to=marcin.bernatowicz@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=satyanarayana.k.v.p@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.