From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Matthew Brost" <matthew.brost@intel.com>
Cc: Dave Airlie <airlied@gmail.com>,
Simona Vetter <simona.vetter@ffwll.ch>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: Re: [PULL] drm-xe-next
Date: Fri, 25 Oct 2024 12:34:59 +0300 [thread overview]
Message-ID: <87plnor0e4.fsf@intel.com> (raw)
In-Reply-To: <dfdd7040f846234cc4ec18d71e4e4746739c1848.camel@linux.intel.com>
On Fri, 25 Oct 2024, Thomas Hellström <thomas.hellstrom@linux.intel.com> wrote:
> On Thu, 2024-10-24 at 19:22 +0000, Matthew Brost wrote:
>> On Thu, Oct 24, 2024 at 07:52:11PM +0200, Thomas Hellstrom wrote:
>> > Hi, Dave & Simona,
>> >
>> > This week's drm-xe-next PR
>> >
>> > Thanks,
>> > Thomas
>> >
>> >
>> > drm-xe-next-2024-10-24:
>> > UAPI Changes:
>> > - Define and parse OA sync properties (Ashutosh)
>> >
>> > Driver Changes:
>> > - Add caller info to xe_gt_reset_async (Nirmoy)
>> > - A large forcewake rework / cleanup (Himal)
>> > - A g2h response timeout fix (Badal)
>> > - A PTL workaround (Vinay)
>> > - Handle unreliable MMIO reads during forcewake (Shuicheng)
>> > - Ufence user-space access fixes (Nirmoy)
>> > - Annotate flexible arrays (Matthew Brost)
>> > - Enable GuC lite restore (Fei)
>> > - Prevent GuC register capture on VF (Zhanjun)
>> > - Show VFs VRAM / LMEM provisioning summary over debugfs (Michal)
>> > - Parallel queues fix on GT reset (Nirmoy)
>> > - Move reference grabbing to a job's dma-fence (Matt Brost)
>> > - Mark a number of local workqueues WQ_MEM_RECLAIM (Matt Brost)
>>
>> This breaks CI [1] - my mistake. Maybe omit these in this weeks PR.
How did this pass CI and get merged in the first place?!?
It's now botching unrelated pre-merge testing all over the place,
e.g. [3] and [4].
BR,
Jani.
[3] https://lore.kernel.org/r/172981565466.1330037.6238046952250769671@2413ebb6fbb6
[4] https://lore.kernel.org/r/172981849964.1330038.16133455483045565936@2413ebb6fbb6
>>
>> We need [2] merged to fix this. Waiting on an RB but I'd like to get
>> all of this in 6.12.
>>
>> Matt
>>
>> [1]
>> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-140135v2/bat-lnl-1/igt@xe_exec_fault_mode@twice-invalid-fault.html
>> [2] https://patchwork.freedesktop.org/series/140406/
>
> So this CI failure is a warning only and IMHO for drm-xe-next (6.13)
> it's not catastrophic. There might be a window in the bisect history
> where this warning appears. It's perhaps more important for -fixes,
> though.
>
> If we need to wait for the scheduler patch going into drm-misc-next /
> drm-next/ backmerge we'd hold off this branch for too long I fear.
>
> @Dave, @Sima
> If you feel differently please skip this PR for this week and we'll
> work to get the scheduler patch merged asap.
>
> Thanks,
> Thomas
>
>
>>
>> > - OA synchronization support (Ashutosh)
>> >
>> > The following changes since commit
>> > 2eb460ab9f4bc5b575f52568d17936da0af681d8:
>> >
>> > drm/xe: Enlarge the invalidation timeout from 150 to 500 (2024-
>> > 10-16 16:11:10 +0100)
>> >
>> > are available in the Git repository at:
>> >
>> > https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-
>> > next-2024-10-24
>> >
>> > for you to fetch changes up to
>> > 85d3f9e84e0628c412b69aa99b63654dfa08ad68:
>> >
>> > drm/xe/oa: Allow only certain property changes from config (2024-
>> > 10-23 12:42:20 -0700)
>> >
>> > ----------------------------------------------------------------
>> > UAPI Changes:
>> > - Define and parse OA sync properties (Ashutosh)
>> >
>> > Driver Changes:
>> > - Add caller info to xe_gt_reset_async (Nirmoy)
>> > - A large forcewake rework / cleanup (Himal)
>> > - A g2h response timeout fix (Badal)
>> > - A PTL workaround (Vinay)
>> > - Handle unreliable MMIO reads during forcewake (Shuicheng)
>> > - Ufence user-space access fixes (Nirmoy)
>> > - Annotate flexible arrays (Matthew Brost)
>> > - Enable GuC lite restore (Fei)
>> > - Prevent GuC register capture on VF (Zhanjun)
>> > - Show VFs VRAM / LMEM provisioning summary over debugfs (Michal)
>> > - Parallel queues fix on GT reset (Nirmoy)
>> > - Move reference grabbing to a job's dma-fence (Matt Brost)
>> > - Mark a number of local workqueues WQ_MEM_RECLAIM (Matt Brost)
>> > - OA synchronization support (Ashutosh)
>> >
>> > ----------------------------------------------------------------
>> > Ashutosh Dixit (7):
>> > drm/xe/oa: Separate batch submission from waiting for
>> > completion
>> > drm/xe/oa/uapi: Define and parse OA sync properties
>> > drm/xe/oa: Add input fence dependencies
>> > drm/xe/oa: Signal output fences
>> > drm/xe/oa: Move functions up so they can be reused for config
>> > ioctl
>> > drm/xe/oa: Add syncs support to OA config ioctl
>> > drm/xe/oa: Allow only certain property changes from config
>> >
>> > Badal Nilawar (1):
>> > drm/xe/guc/ct: Flush g2h worker in case of g2h response
>> > timeout
>> >
>> > Fei Yang (1):
>> > drm/xe: enable lite restore
>> >
>> > Himal Prasad Ghimiray (26):
>> > drm/xe: Add member initialized_domains to xe_force_wake()
>> > drm/xe/forcewake: Change awake_domain datatype
>> > drm/xe/forcewake: Add a helper xe_force_wake_ref_has_domain()
>> > drm/xe: Error handling in xe_force_wake_get()
>> > drm/xe: Modify xe_force_wake_put to handle _get returned mask
>> > drm/xe/device: Update handling of xe_force_wake_get return
>> > drm/xe/hdcp: Update handling of xe_force_wake_get return
>> > drm/xe/gsc: Update handling of xe_force_wake_get return
>> > drm/xe/gt: Update handling of xe_force_wake_get return
>> > drm/xe/xe_gt_idle: Update handling of xe_force_wake_get
>> > return
>> > drm/xe/devcoredump: Update handling of xe_force_wake_get
>> > return
>> > drm/xe/tests/mocs: Update xe_force_wake_get() return handling
>> > drm/xe/mocs: Update handling of xe_force_wake_get return
>> > drm/xe/xe_drm_client: Update handling of xe_force_wake_get
>> > return
>> > drm/xe/xe_gt_debugfs: Update handling of xe_force_wake_get
>> > return
>> > drm/xe/guc: Update handling of xe_force_wake_get return
>> > drm/xe/huc: Update handling of xe_force_wake_get return
>> > drm/xe/oa: Handle force_wake_get failure in
>> > xe_oa_stream_init()
>> > drm/xe/pat: Update handling of xe_force_wake_get return
>> > drm/xe/gt_tlb_invalidation_ggtt: Update handling of
>> > xe_force_wake_get return
>> > drm/xe/xe_reg_sr: Update handling of xe_force_wake_get return
>> > drm/xe/query: Update handling of xe_force_wake_get return
>> > drm/xe/vram: Update handling of xe_force_wake_get return
>> > drm/xe: forcewake debugfs open fails on xe_forcewake_get
>> > failure
>> > drm/xe: Ensure __must_check for xe_force_wake_get() return
>> > drm/xe: Change return type to void for xe_force_wake_put
>> >
>> > Matthew Brost (5):
>> > drm/xe: Use __counted_by for flexible arrays
>> > drm/xe: Take ref to job's fence in arm
>> > drm/xe: Mark GGTT work queue with WQ_MEM_RECLAIM
>> > drm/xe: Mark G2H work queue with WQ_MEM_RECLAIM
>> > drm/xe: Mark GT work queue with WQ_MEM_RECLAIM
>> >
>> > Michal Wajdeczko (1):
>> > drm/xe/pf: Show VFs LMEM provisioning summary over debugfs
>> >
>> > Nirmoy Das (4):
>> > drm/xe: Add caller info to xe_gt_reset_async
>> > drm/xe/ufence: Prefetch ufence addr to catch bogus address
>> > drm/xe/ufence: Warn if mmget_not_zero() fails
>> > drm/xe: Don't restart parallel queues multiple times on GT
>> > reset
>> >
>> > Shuicheng Lin (1):
>> > drm/xe: Handle unreliable MMIO reads during forcewake
>> >
>> > Vinay Belgaumkar (1):
>> > drm/xe/ptl: Apply Wa_14022866841
>> >
>> > Zhanjun Dong (1):
>> > drm/xe/guc: Prevent GuC register capture running on VF
>> >
>> > drivers/gpu/drm/xe/abi/guc_klvs_abi.h | 1 +
>> > drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 6 +-
>> > drivers/gpu/drm/xe/tests/xe_mocs.c | 18 +-
>> > drivers/gpu/drm/xe/xe_debugfs.c | 27 +-
>> > drivers/gpu/drm/xe/xe_devcoredump.c | 14 +-
>> > drivers/gpu/drm/xe/xe_device.c | 25 +-
>> > drivers/gpu/drm/xe/xe_drm_client.c | 8 +-
>> > drivers/gpu/drm/xe/xe_exec_queue_types.h | 2 +-
>> > drivers/gpu/drm/xe/xe_execlist.c | 2 +-
>> > drivers/gpu/drm/xe/xe_force_wake.c | 134 ++++--
>> > drivers/gpu/drm/xe/xe_force_wake.h | 23 +-
>> > drivers/gpu/drm/xe/xe_force_wake_types.h | 6 +-
>> > drivers/gpu/drm/xe/xe_ggtt.c | 2 +-
>> > drivers/gpu/drm/xe/xe_gsc.c | 23 +-
>> > drivers/gpu/drm/xe/xe_gsc_proxy.c | 9 +-
>> > drivers/gpu/drm/xe/xe_gt.c | 110 +++--
>> > drivers/gpu/drm/xe/xe_gt_debugfs.c | 13 +-
>> > drivers/gpu/drm/xe/xe_gt_idle.c | 26 +-
>> > drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 35 ++
>> > drivers/gpu/drm/xe/xe_gt_sriov_pf_config.h | 1 +
>> > drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c | 5 +
>> > drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 5 +-
>> > drivers/gpu/drm/xe/xe_guc.c | 15 +-
>> > drivers/gpu/drm/xe/xe_guc_ads.c | 5 +
>> > drivers/gpu/drm/xe/xe_guc_capture.c | 8 +-
>> > drivers/gpu/drm/xe/xe_guc_ct.c | 20 +-
>> > drivers/gpu/drm/xe/xe_guc_fwif.h | 1 +
>> > drivers/gpu/drm/xe/xe_guc_log.c | 9 +-
>> > drivers/gpu/drm/xe/xe_guc_pc.c | 50 +-
>> > drivers/gpu/drm/xe/xe_guc_submit.c | 29 +-
>> > drivers/gpu/drm/xe/xe_huc.c | 8 +-
>> > drivers/gpu/drm/xe/xe_mocs.c | 14 +-
>> > drivers/gpu/drm/xe/xe_oa.c | 678
>> > +++++++++++++++++++---------
>> > drivers/gpu/drm/xe/xe_oa_types.h | 12 +
>> > drivers/gpu/drm/xe/xe_pat.c | 65 ++-
>> > drivers/gpu/drm/xe/xe_query.c | 10 +-
>> > drivers/gpu/drm/xe/xe_reg_sr.c | 24 +-
>> > drivers/gpu/drm/xe/xe_sched_job.c | 2 +-
>> > drivers/gpu/drm/xe/xe_sched_job_types.h | 3 +-
>> > drivers/gpu/drm/xe/xe_sync.c | 5 +-
>> > drivers/gpu/drm/xe/xe_vram.c | 12 +-
>> > drivers/gpu/drm/xe/xe_wa_oob.rules | 2 +
>> > include/uapi/drm/xe_drm.h | 17 +
>> > 43 files changed, 997 insertions(+), 487 deletions(-)
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-10-25 9:35 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 17:52 [PULL] drm-xe-next Thomas Hellstrom
2024-10-24 19:22 ` Matthew Brost
2024-10-25 7:30 ` Thomas Hellström
2024-10-25 9:34 ` Jani Nikula [this message]
2024-10-25 10:45 ` Thomas Hellström
2024-10-25 22:26 ` Matthew Brost
-- strict thread matches above, loose matches on Subject: below --
2026-05-14 13:20 Thomas Hellstrom
2026-04-30 13:00 Thomas Hellstrom
2026-03-27 3:24 Matthew Brost
2026-03-26 4:44 Matthew Brost
2026-03-12 14:57 Matthew Brost
2026-03-02 22:40 Matthew Brost
2026-01-15 16:16 Rodrigo Vivi
2025-12-30 9:58 Thomas Hellstrom
2025-12-19 22:41 Rodrigo Vivi
2025-11-14 10:49 Thomas Hellstrom
2025-11-17 20:56 ` Dave Airlie
2025-11-18 8:34 ` Thomas Hellström
2025-11-05 16:53 Thomas Hellstrom
2025-10-28 11:16 Thomas Hellstrom
2025-10-31 17:46 ` Simona Vetter
2025-10-20 8:31 Thomas Hellstrom
2025-10-24 11:26 ` Simona Vetter
2025-09-19 14:53 Lucas De Marchi
2025-08-29 22:00 Lucas De Marchi
2025-07-15 18:21 Rodrigo Vivi
2025-07-10 22:16 Rodrigo Vivi
2025-07-11 9:12 ` Simona Vetter
2025-07-11 9:25 ` Simona Vetter
2025-06-18 20:05 Rodrigo Vivi
2025-05-08 16:01 Thomas Hellstrom
2025-04-28 16:03 Thomas Hellstrom
2025-04-28 14:27 Thomas Hellstrom
2025-04-28 15:40 ` Thomas Hellström
2025-04-17 10:22 Thomas Hellstrom
2025-03-07 8:02 Lucas De Marchi
2025-03-07 14:51 ` Lucas De Marchi
2025-03-07 19:04 ` Lucas De Marchi
2025-02-24 18:50 Lucas De Marchi
2025-01-10 14:54 Rodrigo Vivi
2025-01-07 19:01 Rodrigo Vivi
2024-12-11 23:27 Rodrigo Vivi
2024-10-31 11:50 Thomas Hellstrom
2024-10-17 9:32 Thomas Hellstrom
2024-10-10 9:56 Thomas Hellstrom
2024-09-06 2:29 Lucas De Marchi
2024-08-28 19:18 Lucas De Marchi
2024-08-22 20:55 Lucas De Marchi
2024-08-27 10:51 ` Daniel Vetter
2024-07-30 22:39 Lucas De Marchi
2024-07-02 19:02 Rodrigo Vivi
2024-07-05 8:18 ` Daniel Vetter
2024-06-26 22:32 Rodrigo Vivi
2024-06-06 21:43 Rodrigo Vivi
2024-04-23 12:54 Thomas Hellstrom
2024-02-26 3:21 Lucas De Marchi
2024-02-26 9:58 ` Daniel Vetter
2024-02-26 10:46 ` Daniel Stone
2024-02-26 14:16 ` Lucas De Marchi
2023-12-15 22:28 Rodrigo Vivi
2023-12-17 12:35 ` Oded Gabbay
2023-12-17 12:35 ` Oded Gabbay
2023-12-18 12:09 ` Oded Gabbay
2023-12-18 12:09 ` Oded Gabbay
2023-12-18 14:27 ` Oded Gabbay
2023-12-18 14:27 ` Oded Gabbay
2023-12-19 7:17 ` Ohad Sharabi
2023-12-19 9:15 ` Dani Liberman
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=87plnor0e4.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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.