From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] ✗ CI.BAT: failure for Add OA functionality to Xe (rev5)
Date: Tue, 19 Sep 2023 14:27:08 -0700 [thread overview]
Message-ID: <87cyydyhub.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <169414981780.14895.12026633836111579449@emeril.freedesktop.org>
On Thu, 07 Sep 2023 22:10:17 -0700, Patchwork wrote:
>
> Patch Details
>
> Series: Add OA functionality to Xe (rev5)
> URL: https://patchwork.freedesktop.org/series/121084/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-121084v5/index.html
>
> CI Bug Log - changes from xe-362-758f01ec2a6774fda1e8f8075d31f42b81783caf_BAT -> xe-pw-121084v5_BAT
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with xe-pw-121084v5_BAT absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-121084v5_BAT, please notify your bug team (lgci.bug.filing@intel.com) to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
> Participating hosts (4 -> 4)
>
> No changes in participating hosts
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in xe-pw-121084v5_BAT:
>
> IGT changes
>
> Possible regressions
>
> * igt@kms_addfb_basic@invalid-set-prop:
>
> * bat-adlp-7: PASS -> INCOMPLETE
>
> * igt@xe_exec_balancer@twice-cm-virtual-rebind:
>
> * bat-adlp-7: PASS -> FAIL +43 other tests fail
>
> * igt@xe_exec_balancer@twice-virtual-userptr-invalidate:
>
> * bat-dg2-oem2: PASS -> FAIL +38 other tests fail
>
> * igt@xe_exec_compute_mode@twice-userptr-invalidate:
>
> * bat-atsm-2: PASS -> FAIL +38 other tests fail
>
> * igt@xe_exec_threads@threads-mixed-basic:
>
> * bat-dg2-oem2: PASS -> TIMEOUT +3 other tests timeout
>
> * bat-atsm-2: PASS -> TIMEOUT +2 other tests timeout
>
> * igt@xe_exec_threads@threads-mixed-shared-vm-userptr-invalidate-race:
>
> * bat-adlp-7: PASS -> TIMEOUT +5 other tests timeout
>
> * bat-dg2-oem2: PASS -> INCOMPLETE
>
> * igt@xe_exec_threads@threads-mixed-userptr-invalidate:
>
> * bat-atsm-2: PASS -> INCOMPLETE
These failures are due to the fact that the kernel patch has added an
additional field to 'struct drm_xe_engine_class_instance':
drm/xe/uapi: Introduce OA (observability architecture) uapi
@@ -748,6 +756,7 @@ struct drm_xe_engine_class_instance {
__u16 engine_instance;
__u16 gt_id;
+ __u16 oa_unit_id;
};
The tests pass with my IGT version but there's no way to fix these in CI
since XE CI does not have a "Test-with". Let's see, we may add some padding
to the struct first and merge that and then replace that padding with the
field above.
This field will not be needed if we go with 'struct drm_xe_query_oa_info'
(which is introduced in xe_drm.h) but not implemented yet.
Thanks.
--
Ashutosh
prev parent reply other threads:[~2023-09-19 21:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 4:23 [Intel-xe] [PATCH 00/17] Add OA functionality to Xe Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 01/17] drm/xe/oa: Introduce OA (observability architecture) uapi Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 02/17] drm/xe/oa: Add OA types Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 03/17] drm/xe/oa: Add registers and GPU commands used by OA Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 04/17] drm/xe/oa: Module init/exit and probe/remove Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 05/17] drm/xe/oa: Add/remove config ioctl's Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 06/17] drm/xe/oa: Start implementing OA stream open ioctl Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 07/17] drm/xe/oa: OA stream initialization Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 08/17] drm/xe/oa: Expose OA stream fd Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 09/17] drm/xe/oa: Read file_operation Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 10/17] drm/xe/oa: Implement queries Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 11/17] drm/xe/oa: Override GuC RC with OA on PVC Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 12/17] drm/xe/perf: "Perf" layer to support multiple perf counter stream types Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 13/17] drm/xe/oa: Multiplex PERF ops through a single PERF ioctl Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 14/17] drm/xe/oa: Simplify OA configs in uapi Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 15/17] drm/xe/oa: Remove OA format names from OA uapi Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 16/17] drm/xe/oa: Make xe_oa_timestamp_frequency per gt Ashutosh Dixit
2023-09-08 4:23 ` [Intel-xe] [PATCH 17/17] drm/xe/oa: Remove filtering reports on context id Ashutosh Dixit
2023-09-09 1:24 ` Dixit, Ashutosh
2023-11-13 20:22 ` Dixit, Ashutosh
2023-09-08 4:26 ` [Intel-xe] ✓ CI.Patch_applied: success for Add OA functionality to Xe (rev5) Patchwork
2023-09-08 4:27 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-08 4:28 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-08 4:35 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-08 4:35 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-09-19 21:18 ` Dixit, Ashutosh
2023-09-08 4:36 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-09-08 5:10 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-09-19 21:27 ` Dixit, Ashutosh [this message]
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=87cyydyhub.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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