* [PATCH i-g-t v1 0/2] Allow intel_reg tool to work also with accelerators
@ 2026-06-17 20:25 Kamil Konieczny
2026-06-17 20:25 ` [PATCH i-g-t v1 1/2] lib/intel_chipset: Create intel_get_pci_accelerator_device() function Kamil Konieczny
` (4 more replies)
0 siblings, 5 replies; 10+ messages in thread
From: Kamil Konieczny @ 2026-06-17 20:25 UTC (permalink / raw)
To: igt-dev
Cc: Kamil Konieczny, Ashutosh Dixit, Jani Nikula, Janusz Krzysztofik,
Lukasz Laguna, Zbigniew Kempczyński
An Intel tool for register access could also be used for
accelerators. While the device could be accesed by BDF address
with the help of --pci-slot option, allow a tool to work with
default device found on PCI bus. When no Intel display device
is present then intel_reg will search for Intel accelerator and
it will use it for operations on registers.
For reference please look into https://patchwork.freedesktop.org/series/168385/
lib/intel_chipset: Extend intel_get_pci_device to PCI accelerator class
Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: Lukasz Laguna <lukasz.laguna@intel.com>
Cc: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Kamil Konieczny (2):
lib/intel_chipset: Create intel_get_pci_accelerator_device() function
tools/intel_reg: Create default accelerator access
lib/intel_chipset.c | 47 ++++++++++++++++++++++++++++++++++++---------
lib/intel_chipset.h | 1 +
tools/intel_reg.c | 12 ++++++++++++
3 files changed, 51 insertions(+), 9 deletions(-)
--
2.54.0
^ permalink raw reply [flat|nested] 10+ messages in thread* [PATCH i-g-t v1 1/2] lib/intel_chipset: Create intel_get_pci_accelerator_device() function 2026-06-17 20:25 [PATCH i-g-t v1 0/2] Allow intel_reg tool to work also with accelerators Kamil Konieczny @ 2026-06-17 20:25 ` Kamil Konieczny 2026-06-17 20:25 ` [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access Kamil Konieczny ` (3 subsequent siblings) 4 siblings, 0 replies; 10+ messages in thread From: Kamil Konieczny @ 2026-06-17 20:25 UTC (permalink / raw) To: igt-dev; +Cc: Kamil Konieczny, Ashutosh Dixit Among Intel DRM devices there are also accelerators, so create a new function for searching for them. Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com> --- lib/intel_chipset.c | 47 ++++++++++++++++++++++++++++++++++++--------- lib/intel_chipset.h | 1 + 2 files changed, 39 insertions(+), 9 deletions(-) diff --git a/lib/intel_chipset.c b/lib/intel_chipset.c index 760faede2..9f9643414 100644 --- a/lib/intel_chipset.c +++ b/lib/intel_chipset.c @@ -64,15 +64,14 @@ enum pch_type intel_pch; /** - * intel_get_pci_device: + * intel_get_pci_device_by_class: * * Looks up the main graphics pci device using libpciaccess. * * Returns: - * The pci_device, exits the program on any failures. + * The pci_device, exits the program on probe failure. */ -struct pci_device * -intel_get_pci_device(void) +static struct pci_device *intel_get_pci_device_by_class(unsigned int class) { struct pci_device *pci_dev; int error; @@ -81,7 +80,7 @@ intel_get_pci_device(void) igt_fail_on_f(error != 0, "Couldn't initialize PCI system\n"); - /* Grab the graphics card. Try the canonical slot first, then + /* Grab Intel device by class. Try the canonical slot first, then * walk the entire PCI bus for a matching device. */ pci_dev = pci_device_find_by_slot(0, 0, 2, 0); if (pci_dev == NULL || pci_dev->vendor_id != 0x8086) { @@ -93,7 +92,7 @@ intel_get_pci_device(void) match.subvendor_id = PCI_MATCH_ANY; match.subdevice_id = PCI_MATCH_ANY; - match.device_class = 0x3 << 16; + match.device_class = class << 16; match.device_class_mask = 0xff << 16; match.match_data = 0; @@ -102,18 +101,48 @@ intel_get_pci_device(void) pci_dev = pci_device_next(iter); pci_iterator_destroy(iter); } - igt_require_f(pci_dev, "Couldn't find Intel graphics card\n"); + + if (!pci_dev) + return NULL; error = pci_device_probe(pci_dev); igt_fail_on_f(error != 0, "Couldn't probe graphics card\n"); - if (pci_dev->vendor_id != 0x8086) - errx(1, "Graphics card is non-intel"); + if (pci_dev->vendor_id != 0x8086) /* should not happen */ + errx(1, "PCI device 0x%02x card is non-intel", class); return pci_dev; } +/** + * intel_get_pci_device: + * + * Looks up the main graphics pci device using libpciaccess. + * + * Returns: + * The pci_device or NULL if no Intel GPU card found. + */ +struct pci_device *intel_get_pci_device(void) +{ + /* PCI display (0x03) class devices */ + return intel_get_pci_device_by_class(0x03); +} + +/** + * intel_get_pci_accelerator_device: + * + * Looks up the main accelerator pci device using libpciaccess. + * + * Returns: + * The pci_device or NULL if no Intel accelerator card found. + */ +struct pci_device *intel_get_pci_accelerator_device(void) +{ + /* PCI accelerator (0x12) class devices */ + return intel_get_pci_device_by_class(0x12); +} + static uint32_t __i915_get_drm_devid(int fd) { struct drm_i915_getparam gp; diff --git a/lib/intel_chipset.h b/lib/intel_chipset.h index 98a2a81fc..82c7883ea 100644 --- a/lib/intel_chipset.h +++ b/lib/intel_chipset.h @@ -36,6 +36,7 @@ #define BIT(x) (1ul <<(x)) struct pci_device *intel_get_pci_device(void); +struct pci_device *intel_get_pci_accelerator_device(void); uint32_t intel_get_drm_devid(int fd); struct intel_device_info { -- 2.54.0 ^ permalink raw reply related [flat|nested] 10+ messages in thread
* [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access 2026-06-17 20:25 [PATCH i-g-t v1 0/2] Allow intel_reg tool to work also with accelerators Kamil Konieczny 2026-06-17 20:25 ` [PATCH i-g-t v1 1/2] lib/intel_chipset: Create intel_get_pci_accelerator_device() function Kamil Konieczny @ 2026-06-17 20:25 ` Kamil Konieczny 2026-06-17 22:09 ` Dixit, Ashutosh 2026-06-18 5:50 ` Jani Nikula 2026-06-17 22:14 ` ✓ Xe.CI.BAT: success for Allow intel_reg tool to work also with accelerators Patchwork ` (2 subsequent siblings) 4 siblings, 2 replies; 10+ messages in thread From: Kamil Konieczny @ 2026-06-17 20:25 UTC (permalink / raw) To: igt-dev; +Cc: Kamil Konieczny, Ashutosh Dixit Among computing devices there are GPU and accelerators and the intel_reg tool worked only with former ones. Create new way for finding a compute device and when no Intel GPU is found, then search for Intel accelerator. Also, inform user about which type of device will be accessed. Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com> --- tools/intel_reg.c | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/tools/intel_reg.c b/tools/intel_reg.c index 49afe91c0..b4f8cd0fd 100644 --- a/tools/intel_reg.c +++ b/tools/intel_reg.c @@ -1382,6 +1382,18 @@ int main(int argc, char *argv[]) return EXIT_FAILURE; } else { config.pci_dev = intel_get_pci_device(); + if (config.pci_dev) { + fprintf(stderr, "Found Intel GPU PCI device 0x%x\n", config.pci_dev->device_id); + } else { + config.pci_dev = intel_get_pci_accelerator_device(); + if (config.pci_dev) + fprintf(stderr, "Found Intel accelerator PCI device 0x%x\n", config.pci_dev->device_id); + } + + if (!config.pci_dev) { + fprintf(stderr, "Cannot find Intel GPU nor accelerator device\n"); + return EXIT_FAILURE; + } } config.devid = config.pci_dev->device_id; -- 2.54.0 ^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access 2026-06-17 20:25 ` [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access Kamil Konieczny @ 2026-06-17 22:09 ` Dixit, Ashutosh 2026-06-18 11:50 ` Kamil Konieczny 2026-06-18 5:50 ` Jani Nikula 1 sibling, 1 reply; 10+ messages in thread From: Dixit, Ashutosh @ 2026-06-17 22:09 UTC (permalink / raw) To: Kamil Konieczny; +Cc: igt-dev On Wed, 17 Jun 2026 13:25:58 -0700, Kamil Konieczny wrote: > > Among computing devices there are GPU and accelerators and the > intel_reg tool worked only with former ones. Create new way for > finding a compute device and when no Intel GPU is found, then > search for Intel accelerator. Also, inform user about which type > of device will be accessed. > > Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> > Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com> > --- > tools/intel_reg.c | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/tools/intel_reg.c b/tools/intel_reg.c > index 49afe91c0..b4f8cd0fd 100644 > --- a/tools/intel_reg.c > +++ b/tools/intel_reg.c > @@ -1382,6 +1382,18 @@ int main(int argc, char *argv[]) > return EXIT_FAILURE; > } else { > config.pci_dev = intel_get_pci_device(); > + if (config.pci_dev) { > + fprintf(stderr, "Found Intel GPU PCI device 0x%x\n", config.pci_dev->device_id); > + } else { > + config.pci_dev = intel_get_pci_accelerator_device(); > + if (config.pci_dev) > + fprintf(stderr, "Found Intel accelerator PCI device 0x%x\n", config.pci_dev->device_id); > + } > + > + if (!config.pci_dev) { > + fprintf(stderr, "Cannot find Intel GPU nor accelerator device\n"); > + return EXIT_FAILURE; > + } So what I am not following is why you want to preserve intel_get_pci_device() to just display class devices? In https://patchwork.freedesktop.org/series/168385/ intel_get_pci_device() is extended to both display and acceleretor class devices. So this kind of modification to the individual tools is not needed at all. Note that it is not just intel_reg. Similar modification will need to all tools which currently call intel_get_pci_device(). They will now all have to be changed to add the intel_get_pci_accelerator_device() calls, something which is not needed with https://patchwork.freedesktop.org/series/168385/ (especially rev1 of that series). Because we would want most of these tools to "just work" with any intel device (display or accelerator). See also my comments here: https://lore.kernel.org/igt-dev/87wlvyzbn0.wl-ashutosh.dixit@intel.com/ Anyway, let's see what other reviewers have to say about this. Thanks. -- Ashutosh > } > > config.devid = config.pci_dev->device_id; > -- > 2.54.0 > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access 2026-06-17 22:09 ` Dixit, Ashutosh @ 2026-06-18 11:50 ` Kamil Konieczny 2026-06-18 16:59 ` Dixit, Ashutosh 0 siblings, 1 reply; 10+ messages in thread From: Kamil Konieczny @ 2026-06-18 11:50 UTC (permalink / raw) To: Dixit, Ashutosh; +Cc: igt-dev Hi Dixit,, On 2026-06-17 at 15:09:53 -0700, Dixit, Ashutosh wrote: > On Wed, 17 Jun 2026 13:25:58 -0700, Kamil Konieczny wrote: > > > > Among computing devices there are GPU and accelerators and the > > intel_reg tool worked only with former ones. Create new way for > > finding a compute device and when no Intel GPU is found, then > > search for Intel accelerator. Also, inform user about which type > > of device will be accessed. > > > > Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> > > Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com> > > --- > > tools/intel_reg.c | 12 ++++++++++++ > > 1 file changed, 12 insertions(+) > > > > diff --git a/tools/intel_reg.c b/tools/intel_reg.c > > index 49afe91c0..b4f8cd0fd 100644 > > --- a/tools/intel_reg.c > > +++ b/tools/intel_reg.c > > @@ -1382,6 +1382,18 @@ int main(int argc, char *argv[]) > > return EXIT_FAILURE; > > } else { > > config.pci_dev = intel_get_pci_device(); > > + if (config.pci_dev) { > > + fprintf(stderr, "Found Intel GPU PCI device 0x%x\n", config.pci_dev->device_id); > > + } else { > > + config.pci_dev = intel_get_pci_accelerator_device(); > > + if (config.pci_dev) > > + fprintf(stderr, "Found Intel accelerator PCI device 0x%x\n", config.pci_dev->device_id); > > + } > > + > > + if (!config.pci_dev) { > > + fprintf(stderr, "Cannot find Intel GPU nor accelerator device\n"); > > + return EXIT_FAILURE; > > + } > > So what I am not following is why you want to preserve > intel_get_pci_device() to just display class devices? In > https://patchwork.freedesktop.org/series/168385/ intel_get_pci_device() is > extended to both display and acceleretor class devices. So this kind of > modification to the individual tools is not needed at all. But existing tools willl not work for accelerators? They are meant for display/GPU only. cd tools grep -l intel_get_pci_device *c intel_audio_dump.c intel_backlight.c intel_display_bandwidth.c intel_display_poller.c intel_forcewaked.c intel_gpu_time.c intel_gtt.c intel_infoframes.c intel_lid.c intel_panel_fitter.c intel_reg.c intel_reg_checker.c intel_watermark.c Which ones from above could work? Or can you add to cc few devs from Intel accelerators drivers and ask him/her for opinion? > > Note that it is not just intel_reg. Similar modification will need to all > tools which currently call intel_get_pci_device(). They will now all have > to be changed to add the intel_get_pci_accelerator_device() calls, > something which is not needed with > https://patchwork.freedesktop.org/series/168385/ (especially rev1 of that > series). Because we would want most of these tools to "just work" with any > intel device (display or accelerator). > > See also my comments here: > https://lore.kernel.org/igt-dev/87wlvyzbn0.wl-ashutosh.dixit@intel.com/ > > Anyway, let's see what other reviewers have to say about this. Well, I just do not like indeterminancy of that function, it was returning whatever a first device was on PCI bus. When it searched for display only it was ok, now you never know which one will be. Second no-go is that accelerators could be non-GPU based and then almost all of our tools will not work. Regards, Kamil > > Thanks. > -- > Ashutosh > > > } > > > > config.devid = config.pci_dev->device_id; > > -- > > 2.54.0 > > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access 2026-06-18 11:50 ` Kamil Konieczny @ 2026-06-18 16:59 ` Dixit, Ashutosh 0 siblings, 0 replies; 10+ messages in thread From: Dixit, Ashutosh @ 2026-06-18 16:59 UTC (permalink / raw) To: Kamil Konieczny, Dixit, Ashutosh, igt-dev On Thu, 18 Jun 2026 04:50:36 -0700, Kamil Konieczny wrote: > > Hi Dixit,, > On 2026-06-17 at 15:09:53 -0700, Dixit, Ashutosh wrote: > > On Wed, 17 Jun 2026 13:25:58 -0700, Kamil Konieczny wrote: > > > > > > Among computing devices there are GPU and accelerators and the > > > intel_reg tool worked only with former ones. Create new way for > > > finding a compute device and when no Intel GPU is found, then > > > search for Intel accelerator. Also, inform user about which type > > > of device will be accessed. > > > > > > Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> > > > Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com> > > > --- > > > tools/intel_reg.c | 12 ++++++++++++ > > > 1 file changed, 12 insertions(+) > > > > > > diff --git a/tools/intel_reg.c b/tools/intel_reg.c > > > index 49afe91c0..b4f8cd0fd 100644 > > > --- a/tools/intel_reg.c > > > +++ b/tools/intel_reg.c > > > @@ -1382,6 +1382,18 @@ int main(int argc, char *argv[]) > > > return EXIT_FAILURE; > > > } else { > > > config.pci_dev = intel_get_pci_device(); > > > + if (config.pci_dev) { > > > + fprintf(stderr, "Found Intel GPU PCI device 0x%x\n", config.pci_dev->device_id); > > > + } else { > > > + config.pci_dev = intel_get_pci_accelerator_device(); > > > + if (config.pci_dev) > > > + fprintf(stderr, "Found Intel accelerator PCI device 0x%x\n", config.pci_dev->device_id); > > > + } > > > + > > > + if (!config.pci_dev) { > > > + fprintf(stderr, "Cannot find Intel GPU nor accelerator device\n"); > > > + return EXIT_FAILURE; > > > + } > > > > So what I am not following is why you want to preserve > > intel_get_pci_device() to just display class devices? In > > https://patchwork.freedesktop.org/series/168385/ intel_get_pci_device() is > > extended to both display and acceleretor class devices. So this kind of > > modification to the individual tools is not needed at all. > > But existing tools willl not work for accelerators? > They are meant for display/GPU only. > cd tools > grep -l intel_get_pci_device *c > intel_audio_dump.c > intel_backlight.c > intel_display_bandwidth.c > intel_display_poller.c > intel_forcewaked.c > intel_gpu_time.c > intel_gtt.c > intel_infoframes.c > intel_lid.c > intel_panel_fitter.c > intel_reg.c > intel_reg_checker.c > intel_watermark.c https://patchwork.freedesktop.org/patch/733334/?series=168385&rev=4 According to me only the tools calling intel_get_pci_device_display() work only with display/gpu. See also my comments here: https://lore.kernel.org/igt-dev/87wlvyzbn0.wl-ashutosh.dixit@intel.com/ > Which ones from above could work? Or can you add to cc few devs > from Intel accelerators drivers and ask him/her for opinion? I don't think we should be spending time refining this at this time. If something is not completely right it can be fixed later. We just need to provide the correct lib functions in lib/ at this time. > > > > Note that it is not just intel_reg. Similar modification will need to all > > tools which currently call intel_get_pci_device(). They will now all have > > to be changed to add the intel_get_pci_accelerator_device() calls, > > something which is not needed with > > https://patchwork.freedesktop.org/series/168385/ (especially rev1 of that > > series). Because we would want most of these tools to "just work" with any > > intel device (display or accelerator). > > > > See also my comments here: > > https://lore.kernel.org/igt-dev/87wlvyzbn0.wl-ashutosh.dixit@intel.com/ > > > > Anyway, let's see what other reviewers have to say about this. > > Well, I just do not like indeterminancy of that function, it was > returning whatever a first device was on PCI bus. When it > searched for display only it was ok, now you never know which > one will be. > Second no-go is that accelerators could be non-GPU based and > then almost all of our tools will not work. Note that accelerators are mostly the same as GPU, except maybe for display part, so your assumption "almost all of our tools will not work" is wrong. In any case, if you want to keep intel_get_pci_device() for display, you need to provide a function, such as intel_get_pci_device_any(), which will work for both display and accelerator. We can't have each tool modified to add this code, this should be provided as a function in lib/. I prefer this naming scheme: - intel_get_pci_device() or intel_get_pci_device_any(): for both display and accelerator - intel_get_pci_device_display() for display. - intel_get_pci_device_accelerator() for accelerator (according to me there is no use cases for only accelerator at this time). > > > > Thanks. > > -- > > Ashutosh > > > > > } > > > > > > config.devid = config.pci_dev->device_id; > > > -- > > > 2.54.0 > > > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access 2026-06-17 20:25 ` [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access Kamil Konieczny 2026-06-17 22:09 ` Dixit, Ashutosh @ 2026-06-18 5:50 ` Jani Nikula 1 sibling, 0 replies; 10+ messages in thread From: Jani Nikula @ 2026-06-18 5:50 UTC (permalink / raw) To: Kamil Konieczny, igt-dev; +Cc: Kamil Konieczny, Ashutosh Dixit On Wed, 17 Jun 2026, Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote: > Among computing devices there are GPU and accelerators and the > intel_reg tool worked only with former ones. Create new way for > finding a compute device and when no Intel GPU is found, then > search for Intel accelerator. Also, inform user about which type > of device will be accessed. > > Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> > Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com> > --- > tools/intel_reg.c | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/tools/intel_reg.c b/tools/intel_reg.c > index 49afe91c0..b4f8cd0fd 100644 > --- a/tools/intel_reg.c > +++ b/tools/intel_reg.c > @@ -1382,6 +1382,18 @@ int main(int argc, char *argv[]) > return EXIT_FAILURE; > } else { > config.pci_dev = intel_get_pci_device(); > + if (config.pci_dev) { > + fprintf(stderr, "Found Intel GPU PCI device 0x%x\n", config.pci_dev->device_id); > + } else { > + config.pci_dev = intel_get_pci_accelerator_device(); > + if (config.pci_dev) > + fprintf(stderr, "Found Intel accelerator PCI device 0x%x\n", config.pci_dev->device_id); > + } Please don't print anything on success. It's a distraction. BR, Jani. > + > + if (!config.pci_dev) { > + fprintf(stderr, "Cannot find Intel GPU nor accelerator device\n"); > + return EXIT_FAILURE; > + } > } > > config.devid = config.pci_dev->device_id; -- Jani Nikula, Intel ^ permalink raw reply [flat|nested] 10+ messages in thread
* ✓ Xe.CI.BAT: success for Allow intel_reg tool to work also with accelerators 2026-06-17 20:25 [PATCH i-g-t v1 0/2] Allow intel_reg tool to work also with accelerators Kamil Konieczny 2026-06-17 20:25 ` [PATCH i-g-t v1 1/2] lib/intel_chipset: Create intel_get_pci_accelerator_device() function Kamil Konieczny 2026-06-17 20:25 ` [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access Kamil Konieczny @ 2026-06-17 22:14 ` Patchwork 2026-06-17 22:29 ` ✓ i915.CI.BAT: " Patchwork 2026-06-18 7:46 ` ✗ Xe.CI.FULL: failure " Patchwork 4 siblings, 0 replies; 10+ messages in thread From: Patchwork @ 2026-06-17 22:14 UTC (permalink / raw) To: Kamil Konieczny; +Cc: igt-dev [-- Attachment #1: Type: text/plain, Size: 1076 bytes --] == Series Details == Series: Allow intel_reg tool to work also with accelerators URL : https://patchwork.freedesktop.org/series/168736/ State : success == Summary == CI Bug Log - changes from XEIGT_8971_BAT -> XEIGTPW_15391_BAT ==================================================== Summary ------- **SUCCESS** No regressions found. Participating hosts (13 -> 13) ------------------------------ No changes in participating hosts Changes ------- No changes found Build changes ------------- * IGT: IGT_8971 -> IGTPW_15391 * Linux: xe-5274-f7cb2873b7430d84afd4ad4e4771d3f8ad03fbf9 -> xe-5275-18816557ad112c94f3bf5ee625cd862d8d3f41af IGTPW_15391: 1862c378ecfbf12c2dab61a1c11c7170f516506f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git IGT_8971: 8971 xe-5274-f7cb2873b7430d84afd4ad4e4771d3f8ad03fbf9: f7cb2873b7430d84afd4ad4e4771d3f8ad03fbf9 xe-5275-18816557ad112c94f3bf5ee625cd862d8d3f41af: 18816557ad112c94f3bf5ee625cd862d8d3f41af == Logs == For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/index.html [-- Attachment #2: Type: text/html, Size: 1635 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* ✓ i915.CI.BAT: success for Allow intel_reg tool to work also with accelerators 2026-06-17 20:25 [PATCH i-g-t v1 0/2] Allow intel_reg tool to work also with accelerators Kamil Konieczny ` (2 preceding siblings ...) 2026-06-17 22:14 ` ✓ Xe.CI.BAT: success for Allow intel_reg tool to work also with accelerators Patchwork @ 2026-06-17 22:29 ` Patchwork 2026-06-18 7:46 ` ✗ Xe.CI.FULL: failure " Patchwork 4 siblings, 0 replies; 10+ messages in thread From: Patchwork @ 2026-06-17 22:29 UTC (permalink / raw) To: Kamil Konieczny; +Cc: igt-dev [-- Attachment #1: Type: text/plain, Size: 2917 bytes --] == Series Details == Series: Allow intel_reg tool to work also with accelerators URL : https://patchwork.freedesktop.org/series/168736/ State : success == Summary == CI Bug Log - changes from IGT_8971 -> IGTPW_15391 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_15391/index.html Participating hosts (41 -> 40) ------------------------------ Additional (1): fi-skl-6600u Missing (2): bat-dg2-13 fi-snb-2520m Known issues ------------ Here are the changes found in IGTPW_15391 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@core_hotunplug@unbind-rebind: - fi-bsw-n3050: [PASS][1] -> [DMESG-WARN][2] ([i915#16057]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8971/fi-bsw-n3050/igt@core_hotunplug@unbind-rebind.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_15391/fi-bsw-n3050/igt@core_hotunplug@unbind-rebind.html * igt@gem_huc_copy@huc-copy: - fi-skl-6600u: NOTRUN -> [SKIP][3] ([i915#2190]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_15391/fi-skl-6600u/igt@gem_huc_copy@huc-copy.html * igt@gem_lmem_swapping@random-engines: - fi-skl-6600u: NOTRUN -> [SKIP][4] ([i915#4613]) +3 other tests skip [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_15391/fi-skl-6600u/igt@gem_lmem_swapping@random-engines.html * igt@i915_selftest@live@late_gt_pm: - fi-cfl-8109u: [PASS][5] -> [DMESG-WARN][6] ([i915#13735]) +34 other tests dmesg-warn [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8971/fi-cfl-8109u/igt@i915_selftest@live@late_gt_pm.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_15391/fi-cfl-8109u/igt@i915_selftest@live@late_gt_pm.html * igt@kms_dsc@dsc-basic: - fi-skl-6600u: NOTRUN -> [SKIP][7] +11 other tests skip [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_15391/fi-skl-6600u/igt@kms_dsc@dsc-basic.html [i915#13735]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13735 [i915#16057]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/16057 [i915#2190]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2190 [i915#4613]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4613 Build changes ------------- * CI: CI-20190529 -> None * IGT: IGT_8971 -> IGTPW_15391 * Linux: CI_DRM_18696 -> CI_DRM_18697 CI-20190529: 20190529 CI_DRM_18696: f7cb2873b7430d84afd4ad4e4771d3f8ad03fbf9 @ git://anongit.freedesktop.org/gfx-ci/linux CI_DRM_18697: 18816557ad112c94f3bf5ee625cd862d8d3f41af @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_15391: 1862c378ecfbf12c2dab61a1c11c7170f516506f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git IGT_8971: 8971 == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_15391/index.html [-- Attachment #2: Type: text/html, Size: 3647 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* ✗ Xe.CI.FULL: failure for Allow intel_reg tool to work also with accelerators 2026-06-17 20:25 [PATCH i-g-t v1 0/2] Allow intel_reg tool to work also with accelerators Kamil Konieczny ` (3 preceding siblings ...) 2026-06-17 22:29 ` ✓ i915.CI.BAT: " Patchwork @ 2026-06-18 7:46 ` Patchwork 4 siblings, 0 replies; 10+ messages in thread From: Patchwork @ 2026-06-18 7:46 UTC (permalink / raw) To: Kamil Konieczny; +Cc: igt-dev [-- Attachment #1: Type: text/plain, Size: 27932 bytes --] == Series Details == Series: Allow intel_reg tool to work also with accelerators URL : https://patchwork.freedesktop.org/series/168736/ State : failure == Summary == CI Bug Log - changes from XEIGT_8971_FULL -> XEIGTPW_15391_FULL ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with XEIGTPW_15391_FULL absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in XEIGTPW_15391_FULL, please notify your bug team (I915-ci-infra@lists.freedesktop.org) to allow them to document this new failure mode, which will reduce false positives in CI. Participating hosts (2 -> 2) ------------------------------ No changes in participating hosts Possible new issues ------------------- Here are the unknown changes that may have been introduced in XEIGTPW_15391_FULL: ### IGT changes ### #### Possible regressions #### * igt@xe_exec_threads@threads-multi-queue-cm-userptr: - shard-lnl: NOTRUN -> [SKIP][1] +2 other tests skip [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-3/igt@xe_exec_threads@threads-multi-queue-cm-userptr.html * igt@xe_exec_threads@threads-multi-queue-mixed-shared-vm-userptr-invalidate: - shard-bmg: NOTRUN -> [SKIP][2] +2 other tests skip [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-10/igt@xe_exec_threads@threads-multi-queue-mixed-shared-vm-userptr-invalidate.html * igt@xe_sriov_scheduling@equal-throughput-normal-priority@numvfs-random-gt1-vcs0: - shard-bmg: [PASS][3] -> [FAIL][4] [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-bmg-10/igt@xe_sriov_scheduling@equal-throughput-normal-priority@numvfs-random-gt1-vcs0.html [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-4/igt@xe_sriov_scheduling@equal-throughput-normal-priority@numvfs-random-gt1-vcs0.html Known issues ------------ Here are the changes found in XEIGTPW_15391_FULL that come from known issues: ### IGT changes ### #### Issues hit #### * igt@kms_big_fb@linear-max-hw-stride-32bpp-rotate-180-hflip: - shard-lnl: NOTRUN -> [SKIP][5] ([Intel XE#7059] / [Intel XE#7085]) [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-1/igt@kms_big_fb@linear-max-hw-stride-32bpp-rotate-180-hflip.html - shard-bmg: NOTRUN -> [SKIP][6] ([Intel XE#7059] / [Intel XE#7085]) [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-3/igt@kms_big_fb@linear-max-hw-stride-32bpp-rotate-180-hflip.html * igt@kms_big_fb@y-tiled-64bpp-rotate-180: - shard-lnl: NOTRUN -> [SKIP][7] ([Intel XE#1124]) [7]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-7/igt@kms_big_fb@y-tiled-64bpp-rotate-180.html - shard-bmg: NOTRUN -> [SKIP][8] ([Intel XE#1124]) [8]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-6/igt@kms_big_fb@y-tiled-64bpp-rotate-180.html * igt@kms_big_fb@y-tiled-addfb: - shard-bmg: NOTRUN -> [SKIP][9] ([Intel XE#2328] / [Intel XE#7367]) [9]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-7/igt@kms_big_fb@y-tiled-addfb.html - shard-lnl: NOTRUN -> [SKIP][10] ([Intel XE#1467] / [Intel XE#7367]) [10]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-8/igt@kms_big_fb@y-tiled-addfb.html * igt@kms_bw@linear-tiling-4-displays-target-2560x1440p: - shard-bmg: NOTRUN -> [SKIP][11] ([Intel XE#367]) [11]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-1/igt@kms_bw@linear-tiling-4-displays-target-2560x1440p.html - shard-lnl: NOTRUN -> [SKIP][12] ([Intel XE#8365]) [12]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-5/igt@kms_bw@linear-tiling-4-displays-target-2560x1440p.html * igt@kms_ccs@crc-primary-rotation-180-4-tiled-lnl-ccs@pipe-b-dp-2: - shard-bmg: NOTRUN -> [SKIP][13] ([Intel XE#2652]) +8 other tests skip [13]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-3/igt@kms_ccs@crc-primary-rotation-180-4-tiled-lnl-ccs@pipe-b-dp-2.html * igt@kms_ccs@crc-sprite-planes-basic-y-tiled-ccs: - shard-bmg: NOTRUN -> [SKIP][14] ([Intel XE#2887]) [14]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-10/igt@kms_ccs@crc-sprite-planes-basic-y-tiled-ccs.html * igt@kms_chamelium_color@ctm-limited-range: - shard-lnl: NOTRUN -> [SKIP][15] ([Intel XE#306] / [Intel XE#7358]) [15]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-4/igt@kms_chamelium_color@ctm-limited-range.html - shard-bmg: NOTRUN -> [SKIP][16] ([Intel XE#2325] / [Intel XE#7358]) [16]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-5/igt@kms_chamelium_color@ctm-limited-range.html * igt@kms_content_protection@dp-mst-lic-type-0: - shard-lnl: NOTRUN -> [SKIP][17] ([Intel XE#307] / [Intel XE#6974]) [17]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-4/igt@kms_content_protection@dp-mst-lic-type-0.html - shard-bmg: NOTRUN -> [SKIP][18] ([Intel XE#2390] / [Intel XE#6974]) [18]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-5/igt@kms_content_protection@dp-mst-lic-type-0.html * igt@kms_cursor_crc@cursor-rapid-movement-32x32: - shard-bmg: NOTRUN -> [SKIP][19] ([Intel XE#2320]) [19]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-4/igt@kms_cursor_crc@cursor-rapid-movement-32x32.html - shard-lnl: NOTRUN -> [SKIP][20] ([Intel XE#1424]) [20]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-7/igt@kms_cursor_crc@cursor-rapid-movement-32x32.html * igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions-varying-size: - shard-lnl: NOTRUN -> [SKIP][21] ([Intel XE#323] / [Intel XE#6035]) [21]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-2/igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions-varying-size.html - shard-bmg: NOTRUN -> [SKIP][22] ([Intel XE#2286] / [Intel XE#6035]) [22]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-10/igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions-varying-size.html * igt@kms_flip@2x-dpms-vs-vblank-race: - shard-lnl: NOTRUN -> [SKIP][23] ([Intel XE#1421]) [23]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-2/igt@kms_flip@2x-dpms-vs-vblank-race.html * igt@kms_flip@flip-vs-expired-vblank@b-edp1: - shard-lnl: [PASS][24] -> [FAIL][25] ([Intel XE#301]) [24]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-lnl-1/igt@kms_flip@flip-vs-expired-vblank@b-edp1.html [25]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-5/igt@kms_flip@flip-vs-expired-vblank@b-edp1.html * igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-downscaling: - shard-lnl: NOTRUN -> [SKIP][26] ([Intel XE#1397] / [Intel XE#1745] / [Intel XE#7385]) [26]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-6/igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-downscaling.html * igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-downscaling@pipe-a-default-mode: - shard-lnl: NOTRUN -> [SKIP][27] ([Intel XE#1397] / [Intel XE#7385]) [27]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-6/igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-downscaling@pipe-a-default-mode.html * igt@kms_frontbuffer_tracking@fbc-rgb565-draw-render: - shard-bmg: NOTRUN -> [SKIP][28] ([Intel XE#4141]) +3 other tests skip [28]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-1/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-render.html * igt@kms_frontbuffer_tracking@fbcdrrs-1p-primscrn-pri-shrfb-draw-render: - shard-lnl: NOTRUN -> [SKIP][29] ([Intel XE#6312] / [Intel XE#651]) +1 other test skip [29]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-7/igt@kms_frontbuffer_tracking@fbcdrrs-1p-primscrn-pri-shrfb-draw-render.html * igt@kms_frontbuffer_tracking@fbcdrrs-2p-scndscrn-pri-indfb-draw-render: - shard-lnl: NOTRUN -> [SKIP][30] ([Intel XE#656] / [Intel XE#7905]) +5 other tests skip [30]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-6/igt@kms_frontbuffer_tracking@fbcdrrs-2p-scndscrn-pri-indfb-draw-render.html * igt@kms_frontbuffer_tracking@fbcdrrshdr-1p-primscrn-indfb-msflip-blt: - shard-bmg: NOTRUN -> [SKIP][31] ([Intel XE#2311]) +6 other tests skip [31]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-1/igt@kms_frontbuffer_tracking@fbcdrrshdr-1p-primscrn-indfb-msflip-blt.html - shard-lnl: NOTRUN -> [SKIP][32] ([Intel XE#6312]) [32]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-4/igt@kms_frontbuffer_tracking@fbcdrrshdr-1p-primscrn-indfb-msflip-blt.html * igt@kms_frontbuffer_tracking@fbcdrrshdr-abgr161616f-draw-mmap-wc: - shard-bmg: NOTRUN -> [SKIP][33] ([Intel XE#7061]) +1 other test skip [33]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-7/igt@kms_frontbuffer_tracking@fbcdrrshdr-abgr161616f-draw-mmap-wc.html - shard-lnl: NOTRUN -> [SKIP][34] ([Intel XE#7061]) +1 other test skip [34]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-8/igt@kms_frontbuffer_tracking@fbcdrrshdr-abgr161616f-draw-mmap-wc.html * igt@kms_frontbuffer_tracking@fbcpsrhdr-2p-primscrn-spr-indfb-draw-blt: - shard-lnl: NOTRUN -> [SKIP][35] ([Intel XE#7905]) +7 other tests skip [35]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-2/igt@kms_frontbuffer_tracking@fbcpsrhdr-2p-primscrn-spr-indfb-draw-blt.html * igt@kms_frontbuffer_tracking@hdr-rgb565-draw-blt: - shard-lnl: NOTRUN -> [SKIP][36] ([Intel XE#7865]) +6 other tests skip [36]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-6/igt@kms_frontbuffer_tracking@hdr-rgb565-draw-blt.html * igt@kms_frontbuffer_tracking@psrhdr-2p-primscrn-cur-indfb-draw-blt: - shard-bmg: NOTRUN -> [SKIP][37] ([Intel XE#2313]) +12 other tests skip [37]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-1/igt@kms_frontbuffer_tracking@psrhdr-2p-primscrn-cur-indfb-draw-blt.html * igt@kms_plane@pixel-format-y-tiled-ccs-modifier: - shard-lnl: NOTRUN -> [SKIP][38] ([Intel XE#7283]) [38]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-6/igt@kms_plane@pixel-format-y-tiled-ccs-modifier.html * igt@kms_plane@pixel-format-y-tiled-modifier: - shard-bmg: NOTRUN -> [SKIP][39] ([Intel XE#7283]) +1 other test skip [39]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-10/igt@kms_plane@pixel-format-y-tiled-modifier.html * igt@kms_plane_scaling@intel-max-src-size: - shard-lnl: NOTRUN -> [SKIP][40] ([Intel XE#3307]) [40]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-2/igt@kms_plane_scaling@intel-max-src-size.html * igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5: - shard-bmg: NOTRUN -> [SKIP][41] ([Intel XE#2763] / [Intel XE#6886]) +4 other tests skip [41]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-4/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5.html * igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-c: - shard-lnl: NOTRUN -> [SKIP][42] ([Intel XE#2763] / [Intel XE#6886]) +3 other tests skip [42]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-5/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-c.html * igt@kms_psr2_sf@pr-cursor-plane-move-continuous-exceed-fully-sf: - shard-bmg: NOTRUN -> [SKIP][43] ([Intel XE#1489]) +1 other test skip [43]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-5/igt@kms_psr2_sf@pr-cursor-plane-move-continuous-exceed-fully-sf.html - shard-lnl: NOTRUN -> [SKIP][44] ([Intel XE#2893] / [Intel XE#7304]) [44]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-3/igt@kms_psr2_sf@pr-cursor-plane-move-continuous-exceed-fully-sf.html * igt@kms_psr@fbc-psr2-sprite-render: - shard-bmg: NOTRUN -> [SKIP][45] ([Intel XE#2234] / [Intel XE#2850]) +2 other tests skip [45]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-5/igt@kms_psr@fbc-psr2-sprite-render.html - shard-lnl: NOTRUN -> [SKIP][46] ([Intel XE#1406] / [Intel XE#7345]) [46]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-3/igt@kms_psr@fbc-psr2-sprite-render.html * igt@kms_psr@fbc-psr2-sprite-render@edp-1: - shard-lnl: NOTRUN -> [SKIP][47] ([Intel XE#1406] / [Intel XE#4609]) [47]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-3/igt@kms_psr@fbc-psr2-sprite-render@edp-1.html * igt@kms_psr@pr-primary-blt: - shard-lnl: NOTRUN -> [SKIP][48] ([Intel XE#1406]) [48]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-1/igt@kms_psr@pr-primary-blt.html * igt@kms_rotation_crc@primary-yf-tiled-reflect-x-90: - shard-bmg: NOTRUN -> [SKIP][49] ([Intel XE#3904] / [Intel XE#7342]) [49]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-7/igt@kms_rotation_crc@primary-yf-tiled-reflect-x-90.html - shard-lnl: NOTRUN -> [SKIP][50] ([Intel XE#3414] / [Intel XE#3904] / [Intel XE#7342]) [50]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-7/igt@kms_rotation_crc@primary-yf-tiled-reflect-x-90.html * igt@xe_eudebug@basic-vm-bind-ufence: - shard-bmg: NOTRUN -> [SKIP][51] ([Intel XE#7636]) +1 other test skip [51]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-6/igt@xe_eudebug@basic-vm-bind-ufence.html * igt@xe_eudebug@multigpu-basic-client-many: - shard-lnl: NOTRUN -> [SKIP][52] ([Intel XE#7636]) +1 other test skip [52]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-4/igt@xe_eudebug@multigpu-basic-client-many.html * igt@xe_evict@evict-beng-mixed-many-threads-small: - shard-bmg: [PASS][53] -> [INCOMPLETE][54] ([Intel XE#6321] / [Intel XE#8355]) [53]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-bmg-7/igt@xe_evict@evict-beng-mixed-many-threads-small.html [54]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-6/igt@xe_evict@evict-beng-mixed-many-threads-small.html * igt@xe_evict@evict-cm-threads-small-multi-vm: - shard-lnl: NOTRUN -> [SKIP][55] ([Intel XE#6540] / [Intel XE#688]) +1 other test skip [55]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-5/igt@xe_evict@evict-cm-threads-small-multi-vm.html * igt@xe_exec_balancer@virtual-all-active: - shard-lnl: NOTRUN -> [SKIP][56] ([Intel XE#7482]) +2 other tests skip [56]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-2/igt@xe_exec_balancer@virtual-all-active.html * igt@xe_exec_basic@multigpu-once-null-rebind: - shard-bmg: NOTRUN -> [SKIP][57] ([Intel XE#2322] / [Intel XE#7372]) +2 other tests skip [57]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-3/igt@xe_exec_basic@multigpu-once-null-rebind.html - shard-lnl: NOTRUN -> [SKIP][58] ([Intel XE#1392]) +2 other tests skip [58]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-3/igt@xe_exec_basic@multigpu-once-null-rebind.html * igt@xe_exec_fault_mode@twice-multi-queue-invalid-userptr-fault: - shard-lnl: NOTRUN -> [SKIP][59] ([Intel XE#8374]) [59]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-1/igt@xe_exec_fault_mode@twice-multi-queue-invalid-userptr-fault.html - shard-bmg: NOTRUN -> [SKIP][60] ([Intel XE#8374]) [60]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-9/igt@xe_exec_fault_mode@twice-multi-queue-invalid-userptr-fault.html * igt@xe_exec_multi_queue@max-queues-preempt-mode-fault-basic: - shard-bmg: NOTRUN -> [SKIP][61] ([Intel XE#8364]) +4 other tests skip [61]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-2/igt@xe_exec_multi_queue@max-queues-preempt-mode-fault-basic.html * igt@xe_exec_multi_queue@two-queues-dyn-priority-smem: - shard-lnl: NOTRUN -> [SKIP][62] ([Intel XE#8364]) +3 other tests skip [62]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-8/igt@xe_exec_multi_queue@two-queues-dyn-priority-smem.html * igt@xe_pxp@pxp-stale-bo-bind-post-termination-irq: - shard-bmg: NOTRUN -> [SKIP][63] ([Intel XE#4733] / [Intel XE#7417]) [63]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-3/igt@xe_pxp@pxp-stale-bo-bind-post-termination-irq.html * igt@xe_sriov_flr@flr-each-isolation: - shard-lnl: NOTRUN -> [SKIP][64] ([Intel XE#3342]) [64]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-6/igt@xe_sriov_flr@flr-each-isolation.html * igt@xe_sriov_scheduling@equal-throughput-normal-priority@numvfs-random-gt0-rcs0: - shard-bmg: [PASS][65] -> [FAIL][66] ([Intel XE#7992]) +2 other tests fail [65]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-bmg-10/igt@xe_sriov_scheduling@equal-throughput-normal-priority@numvfs-random-gt0-rcs0.html [66]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-4/igt@xe_sriov_scheduling@equal-throughput-normal-priority@numvfs-random-gt0-rcs0.html #### Possible fixes #### * igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1: - shard-lnl: [FAIL][67] ([Intel XE#301] / [Intel XE#3149]) -> [PASS][68] +1 other test pass [67]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-lnl-8/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html [68]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-8/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html * igt@kms_flip@flip-vs-expired-vblank@a-edp1: - shard-lnl: [FAIL][69] ([Intel XE#301]) -> [PASS][70] +1 other test pass [69]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-lnl-1/igt@kms_flip@flip-vs-expired-vblank@a-edp1.html [70]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-5/igt@kms_flip@flip-vs-expired-vblank@a-edp1.html * igt@kms_pm_dc@dc5-dpms: - shard-lnl: [FAIL][71] ([Intel XE#7340] / [Intel XE#7504]) -> [PASS][72] [71]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-lnl-8/igt@kms_pm_dc@dc5-dpms.html [72]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-1/igt@kms_pm_dc@dc5-dpms.html * igt@kms_pm_dc@dc6-psr: - shard-lnl: [FAIL][73] ([Intel XE#7340]) -> [PASS][74] +1 other test pass [73]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-lnl-1/igt@kms_pm_dc@dc6-psr.html [74]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-5/igt@kms_pm_dc@dc6-psr.html * igt@xe_exec_system_allocator@fault-process-benchmark: - shard-bmg: [FAIL][75] ([Intel XE#7850]) -> [PASS][76] [75]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-bmg-3/igt@xe_exec_system_allocator@fault-process-benchmark.html [76]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-1/igt@xe_exec_system_allocator@fault-process-benchmark.html #### Warnings #### * igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip: - shard-lnl: [SKIP][77] ([Intel XE#1124]) -> [ABORT][78] ([Intel XE#8007]) [77]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-lnl-4/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html [78]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-7/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html * igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions: - shard-lnl: [SKIP][79] ([Intel XE#309] / [Intel XE#7343]) -> [SKIP][80] ([Intel XE#309] / [Intel XE#7343] / [Intel XE#7935]) [79]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-lnl-4/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions.html [80]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-8/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions.html * igt@kms_tiled_display@basic-test-pattern: - shard-bmg: [FAIL][81] ([Intel XE#1729] / [Intel XE#7424]) -> [SKIP][82] ([Intel XE#2426] / [Intel XE#5848]) [81]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-bmg-10/igt@kms_tiled_display@basic-test-pattern.html [82]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-bmg-2/igt@kms_tiled_display@basic-test-pattern.html * igt@xe_exec_multi_queue@many-queues-dyn-priority-smem: - shard-lnl: [ABORT][83] ([Intel XE#8007]) -> [SKIP][84] ([Intel XE#8364]) [83]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8971/shard-lnl-5/igt@xe_exec_multi_queue@many-queues-dyn-priority-smem.html [84]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/shard-lnl-7/igt@xe_exec_multi_queue@many-queues-dyn-priority-smem.html [Intel XE#1124]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1124 [Intel XE#1392]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1392 [Intel XE#1397]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1397 [Intel XE#1406]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1406 [Intel XE#1421]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1421 [Intel XE#1424]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1424 [Intel XE#1467]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1467 [Intel XE#1489]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1489 [Intel XE#1729]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1729 [Intel XE#1745]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1745 [Intel XE#2234]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2234 [Intel XE#2286]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2286 [Intel XE#2311]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2311 [Intel XE#2313]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2313 [Intel XE#2320]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2320 [Intel XE#2322]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2322 [Intel XE#2325]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2325 [Intel XE#2328]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2328 [Intel XE#2390]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2390 [Intel XE#2426]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2426 [Intel XE#2652]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2652 [Intel XE#2763]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2763 [Intel XE#2850]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2850 [Intel XE#2887]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2887 [Intel XE#2893]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2893 [Intel XE#301]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/301 [Intel XE#306]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/306 [Intel XE#307]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/307 [Intel XE#309]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/309 [Intel XE#3149]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3149 [Intel XE#323]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/323 [Intel XE#3307]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3307 [Intel XE#3342]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3342 [Intel XE#3414]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3414 [Intel XE#367]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/367 [Intel XE#3904]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3904 [Intel XE#4141]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4141 [Intel XE#4609]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4609 [Intel XE#4733]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4733 [Intel XE#5848]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5848 [Intel XE#6035]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6035 [Intel XE#6312]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6312 [Intel XE#6321]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6321 [Intel XE#651]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/651 [Intel XE#6540]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6540 [Intel XE#656]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/656 [Intel XE#688]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/688 [Intel XE#6886]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6886 [Intel XE#6974]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6974 [Intel XE#7059]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7059 [Intel XE#7061]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7061 [Intel XE#7085]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7085 [Intel XE#7283]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7283 [Intel XE#7304]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7304 [Intel XE#7340]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7340 [Intel XE#7342]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7342 [Intel XE#7343]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7343 [Intel XE#7345]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7345 [Intel XE#7358]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7358 [Intel XE#7367]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7367 [Intel XE#7372]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7372 [Intel XE#7385]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7385 [Intel XE#7417]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7417 [Intel XE#7424]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7424 [Intel XE#7482]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7482 [Intel XE#7504]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7504 [Intel XE#7636]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7636 [Intel XE#7850]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7850 [Intel XE#7865]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7865 [Intel XE#7905]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7905 [Intel XE#7935]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7935 [Intel XE#7992]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/7992 [Intel XE#8007]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/8007 [Intel XE#8355]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/8355 [Intel XE#8364]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/8364 [Intel XE#8365]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/8365 [Intel XE#8374]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/8374 Build changes ------------- * IGT: IGT_8971 -> IGTPW_15391 * Linux: xe-5274-f7cb2873b7430d84afd4ad4e4771d3f8ad03fbf9 -> xe-5275-18816557ad112c94f3bf5ee625cd862d8d3f41af IGTPW_15391: 1862c378ecfbf12c2dab61a1c11c7170f516506f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git IGT_8971: 8971 xe-5274-f7cb2873b7430d84afd4ad4e4771d3f8ad03fbf9: f7cb2873b7430d84afd4ad4e4771d3f8ad03fbf9 xe-5275-18816557ad112c94f3bf5ee625cd862d8d3f41af: 18816557ad112c94f3bf5ee625cd862d8d3f41af == Logs == For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15391/index.html [-- Attachment #2: Type: text/html, Size: 31763 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2026-06-18 17:00 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2026-06-17 20:25 [PATCH i-g-t v1 0/2] Allow intel_reg tool to work also with accelerators Kamil Konieczny 2026-06-17 20:25 ` [PATCH i-g-t v1 1/2] lib/intel_chipset: Create intel_get_pci_accelerator_device() function Kamil Konieczny 2026-06-17 20:25 ` [PATCH i-g-t v1 2/2] tools/intel_reg: Create default accelerator access Kamil Konieczny 2026-06-17 22:09 ` Dixit, Ashutosh 2026-06-18 11:50 ` Kamil Konieczny 2026-06-18 16:59 ` Dixit, Ashutosh 2026-06-18 5:50 ` Jani Nikula 2026-06-17 22:14 ` ✓ Xe.CI.BAT: success for Allow intel_reg tool to work also with accelerators Patchwork 2026-06-17 22:29 ` ✓ i915.CI.BAT: " Patchwork 2026-06-18 7:46 ` ✗ Xe.CI.FULL: failure " Patchwork
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox