From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Ruhl, Michael J" <michael.j.ruhl@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Scarbrough, Frank" <frank.scarbrough@intel.com>,
"david.e.box@linux.intel.com" <david.e.box@linux.intel.com>
Subject: Re: [PATCH i-g-t 0/2] Support PMT for BMG and CRI devices
Date: Thu, 22 Oct 2026 08:32:23 -0400 [thread overview]
Message-ID: <atoCV6hhnFIB_fiq@intel.com> (raw)
In-Reply-To: <CH3PR11MB04614921246BC82520BDD5AAD6C1662@CH3PR11MB046149.namprd11.prod.outlook.com>
On Wed, Oct 21, 2026 at 08:52:45PM +0000, Ruhl, Michael J wrote:
> Ping?
>
> Not sure what the sequencing is here...
>
> Is this IGT reasonable?
we definitely need to include these tests.
The biggest problem I see is the crashlog one. Because it puts us in a undefined
state until the cold boot and we don't save the part, that will likely impact
the full CI... (if we have bmg in shards)
Or we find a way to restore to a clean state afterwords or we find a way
to only run this manually and not on the pmt-bmg-all...
>
> Thanks,
>
> Mike
>
>
> >-----Original Message-----
> >From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of Michael J.
> >Ruhl
> >Sent: Wednesday, October 14, 2026 12:05 PM
> >To: igt-dev@lists.freedesktop.org; Scarbrough, Frank
> ><frank.scarbrough@intel.com>; david.e.box@linux.intel.com
> >Subject: [PATCH i-g-t 0/2] Support PMT for BMG and CRI devices
> >
> >BMG and CRI devices have PMT functionality.
> >
> >Provide tests to exercise that functionality.
> >
> >Michael J. Ruhl (2):
> > test/intel/xe_pmt: Add testing for BMG PMT features
> > test/intel/xe_pmt: Support CRI PMT
> >
> > tests/intel/xe_pmt.c | 645
> >+++++++++++++++++++++++++++++++++++++++++++
> > tests/meson.build | 1 +
> > 2 files changed, 646 insertions(+)
> > create mode 100644 tests/intel/xe_pmt.c
> >
> >--
> >2.43.0
>
next prev parent reply other threads:[~2026-10-22 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 16:05 [PATCH i-g-t 0/2] Support PMT for BMG and CRI devices Michael J. Ruhl
2026-10-14 16:05 ` [PATCH i-g-t 1/2] test/intel/xe_pmt: Add testing for BMG PMT features Michael J. Ruhl
2026-10-14 16:05 ` [PATCH i-g-t 2/2] test/intel/xe_pmt: Support CRI PMT Michael J. Ruhl
2026-10-22 12:35 ` Rodrigo Vivi
2026-10-22 12:39 ` Ruhl, Michael J
2026-10-14 21:03 ` ✓ i915.CI.BAT: success for Support PMT for BMG and CRI devices Patchwork
2026-10-15 4:13 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-15 7:09 ` ✗ i915.CI.Full: failure " Patchwork
2026-10-15 15:09 ` ✗ Xe.CI.FULL: " Patchwork
2026-10-21 20:52 ` [PATCH i-g-t 0/2] " Ruhl, Michael J
2026-10-22 12:32 ` Rodrigo Vivi [this message]
2026-10-22 12:38 ` Ruhl, Michael J
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=atoCV6hhnFIB_fiq@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=david.e.box@linux.intel.com \
--cc=frank.scarbrough@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=michael.j.ruhl@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