[PULL] drm-intel-gt-next

2024-04-26 Thread Joonas Lahtinen
Hi Dave & Sima, Here's the drm-intel-gt-next PR for v6.10 in one shot. We are adding a new uAPI for Mesa to request higher GT frequency for compute contexts on GuC platform. Then there is a W/A for DG2 to move to fixed CCS load balancing and make all DG2 SKUs appear with single CCS with all the

[PULL] drm-intel-gt-next

2024-02-28 Thread Tvrtko Ursulin
Hi Dave, Sima, Last drm-intel-gt-next pull request for 6.9. There are only two small fixes in there so could also wait for the -next-fixes round if so would be preferred. One fix is for a kerneldoc warning and other for a very unlikely userptr object creation failure where cleanup would oops.

Re: [PULL] drm-intel-gt-next

2024-02-20 Thread Joonas Lahtinen
Quoting Joonas Lahtinen (2024-02-16 11:41:44) > (+ Jonathan) > > Quoting Dave Airlie (2024-02-16 04:58:03) > > On Thu, 15 Feb 2024 at 20:06, Tvrtko Ursulin > > wrote: > > > > > > Hi Dave, Daniel, > > > > > > First pull request for 6.9 with probably one more coming in one to two > > > weeks. > >

Re: [PULL] drm-intel-gt-next

2024-02-16 Thread Joonas Lahtinen
(+ Jonathan) Quoting Dave Airlie (2024-02-16 04:58:03) > On Thu, 15 Feb 2024 at 20:06, Tvrtko Ursulin > wrote: > > > > Hi Dave, Daniel, > > > > First pull request for 6.9 with probably one more coming in one to two > > weeks. > > > > Nothing to interesting in this one, mostly a sprinkle of small

Re: [PULL] drm-intel-gt-next

2024-02-16 Thread Thomas Hellström
On Fri, 2024-02-16 at 10:31 +0100, Thomas Hellström wrote: > Hi, Dave > > On Fri, 2024-02-16 at 12:58 +1000, Dave Airlie wrote: > > On Thu, 15 Feb 2024 at 20:06, Tvrtko Ursulin > > wrote: > > > > > > Hi Dave, Daniel, > > > > > > First pull request for 6.9 with probably one more coming in one >

Re: [PULL] drm-intel-gt-next

2024-02-16 Thread Thomas Hellström
Hi, Dave On Fri, 2024-02-16 at 12:58 +1000, Dave Airlie wrote: > On Thu, 15 Feb 2024 at 20:06, Tvrtko Ursulin > wrote: > > > > Hi Dave, Daniel, > > > > First pull request for 6.9 with probably one more coming in one to > > two > > weeks. > > > > Nothing to interesting in this one, mostly a

Re: [PULL] drm-intel-gt-next

2024-02-15 Thread Dave Airlie
On Thu, 15 Feb 2024 at 20:06, Tvrtko Ursulin wrote: > > Hi Dave, Daniel, > > First pull request for 6.9 with probably one more coming in one to two > weeks. > > Nothing to interesting in this one, mostly a sprinkle of small fixes in > GuC, HuC, Perf/OA, a tiny bit of prep work for future

[PULL] drm-intel-gt-next

2024-02-15 Thread Tvrtko Ursulin
Hi Dave, Daniel, First pull request for 6.9 with probably one more coming in one to two weeks. Nothing to interesting in this one, mostly a sprinkle of small fixes in GuC, HuC, Perf/OA, a tiny bit of prep work for future platforms and some code cleanups. One new uapi in the form of a GuC

[PULL] drm-intel-gt-next

2023-12-15 Thread Joonas Lahtinen
Hi Dave & Sima, Final drm-intel-gt-next PR for v6.8. Elimination of kmap_atomic() from the driver to allow kernel wide cleanup. One new DG2 W/A and static checker/spelling fixes. Best Regards, Joonas *** drm-intel-gt-next-2023-12-15: Driver Changes: - Eliminate use of kmap_atomic() in i915

[PULL] drm-intel-gt-next

2023-12-08 Thread Joonas Lahtinen
Hi Dave & Sima, A rather late first drm-intel-gt-next PR towards v6.8. As most significant change we have addition of the DRM fdinfo memory stats functionality. Then DG2 and MTL workaround additions and fixes and a few for older platforms as well. PMU WARN_ON splat cleanup. The rest is mostly

[PULL] drm-intel-gt-next

2023-10-19 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here is the final pull request for 6.7. As indicated that it may happen in the last pull, the remaining missing functionality for Meteorlake, enabling the GuC based TLB invalidation, has since been merged and platform thought to be ready for lifting out of force probe status.

[PULL] drm-intel-gt-next

2023-10-12 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here is the second pull request for 6.7. I say second and not final because there is a very small chance we might be doing another one next week, to bring Meteorlake out of force probe status, which was quite close this week but apparently not quite there. At the moment it looks

[PULL] drm-intel-gt-next

2023-09-28 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here goes the first pull request for 6.7. Nothing major in this round - a bunch of fixes, mostly relating to various GuC and PXP features/functionalities, and a few new mostly DG2 workarounds. Tiny bit or Meteorlake enablement and a tiny bit of selftests fixes and even less

[PULL] drm-intel-gt-next

2023-08-11 Thread Joonas Lahtinen
Hi Dave & Daniel, Here's the final drm-intel-gt-next PR for v6.6. Not too many patches as the previous PR was later than usual. Just one more workaround fix for MTL, some object coherency refactoring and selftest fix. Note that there is a backmerge of drm-next[1], too. Regards, Joonas [1] As

[PULL] drm-intel-gt-next

2023-08-04 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes the first drm-intel-gt-next PR for v6.6. We have a fix for infinite GPU wait race condition found by CI, then improved tweakability of RPS algo and fixes to GuC SLPC for tuning the frequency behavior of the system. OA report zeroing fix, Aux CCS invalidation fix on

[PULL] drm-intel-gt-next

2023-06-08 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here goes the final pull request for 6.5. A few improvements to robustness of dealing with GuC communication issues, compute applications, small BAR systems perf/OA monitoring. Then a little bit more of Meteorlake enablement which this time round includes the HuC loading code,

[PULL] drm-intel-gt-next

2023-05-24 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here goes the first pull request for 6.5. In terms of headline features probably the fact GuC platforms can now show per client engine utilisation sticks out the most. Then there is a bunch of fixes where those in the area of GuC error capture, SLPS and firmware loading

Re: [PULL] drm-intel-gt-next

2023-04-06 Thread Daniel Vetter
On Thu, Apr 06, 2023 at 03:34:04PM +0300, Jani Nikula wrote: > On Thu, 06 Apr 2023, Maarten Lankhorst > wrote: > > Hi Dave, Daniel, > > Pull request to avoid backmerges. ;) > > Cheers, > > ~Maarten > > Not using dim for this? Is the subject line copy-pasted from another > pull request? :) dim

Re: [PULL] drm-intel-gt-next

2023-04-06 Thread Daniel Vetter
On Thu, Apr 06, 2023 at 11:18:06AM +0300, Joonas Lahtinen wrote: > Hi Dave & Daniel, > > Here goes the final drm-intel-gt-next pull request for v6.4. > > As top items we have a fix for context runtime accounting, Meteorlake > enabling, DMAR error noise elimination due to GPU error capture, BAR >

Re: [PULL] drm-intel-gt-next

2023-04-06 Thread Jani Nikula
On Thu, 06 Apr 2023, Maarten Lankhorst wrote: > Hi Dave, Daniel, > Pull request to avoid backmerges. ;) > Cheers, > ~Maarten Not using dim for this? Is the subject line copy-pasted from another pull request? :) BR, Jani. > > drm-misc-next-2023-04-06: > drm-misc-next for v6.4-rc1: > > UAPI

[PULL] drm-intel-gt-next

2023-04-06 Thread Maarten Lankhorst
Hi Dave, Daniel, Pull request to avoid backmerges. ;) Cheers, ~Maarten drm-misc-next-2023-04-06: drm-misc-next for v6.4-rc1: UAPI Changes: Cross-subsystem Changes: - Document port and rotation dt bindings better. - For panel timing DT bindings, document that vsync and hsync are first, rather

[PULL] drm-intel-gt-next

2023-04-06 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes the final drm-intel-gt-next pull request for v6.4. As top items we have a fix for context runtime accounting, Meteorlake enabling, DMAR error noise elimination due to GPU error capture, BAR resizing forcewake fix and memory contents clearing fix for discrete. More

[PULL] drm-intel-gt-next

2023-03-16 Thread Joonas Lahtinen
Hi Dave & Daniel, Here's the first batch of drm-intel-gt-next towards v6.4. There is an important performance monitoring fix (#6333), more resiliency to pcode load delay and avoiding caching problems on LLC systems for ring buffers. Stolen memory probing fix and a missing register whitelisting

[PULL] drm-intel-gt-next

2023-02-01 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here goes the final pull request for 6.3. Aside a few fixes, the reset is split between refactoring of the workarounds code and correcting some workaround placement to correctly align for new platforms, and converting the GuC code to use dedicated logging macros, as was done for

Re: [PULL] drm-intel-gt-next

2023-01-24 Thread Daniel Vetter
On Wed, Jan 18, 2023 at 11:24:44AM +, Tvrtko Ursulin wrote: > Hi Dave, Daniel, > > Here goes the first pull request for 6.3. > > What sticks out most is the amount of fixes, majority of which if not all > would have already landed via gt/next fixes pull requests though, so I > will only

[PULL] drm-intel-gt-next

2023-01-18 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here goes the first pull request for 6.3. What sticks out most is the amount of fixes, majority of which if not all would have already landed via gt/next fixes pull requests though, so I will only mention them here briefly. Most impactful ones are probably in the area of DG2

[PULL] drm-intel-gt-next

2022-11-18 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes the last drm-intel-gt-next feature pull req for v6.2. We have a couple of important fixes around memory management (TTM and userptr), then demoting GuC kernel contexts to normal priority and Meteorlake enabling. Beyond that it's smaller fixes to code structure and

[PULL] drm-intel-gt-next

2022-11-03 Thread Joonas Lahtinen
Hi Dave & Daniel, This amends the previous PR that did cause a build error with clang: https://lists.freedesktop.org/archives/dri-devel/2022-October/377713.html Quite naturally, it includes a fix to the hwmon code tested with Clang version 14.0.5 and GCC 12.2.1. Additionally there is a screen

Re: [PULL] drm-intel-gt-next

2022-11-01 Thread Dave Airlie
On Mon, 31 Oct 2022 at 21:07, Joonas Lahtinen wrote: > > Hi Dave & Daniel, > > Here goes first drm-intel-gt-next pull req towards 6.2. > > We have a fix for #6222 (kernel memory corruption issue) and fix for > display regression after resume. A missing W/A for Gen12 iGPUs and > extension of

[PULL] drm-intel-gt-next

2022-10-31 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes first drm-intel-gt-next pull req towards 6.2. We have a fix for #6222 (kernel memory corruption issue) and fix for display regression after resume. A missing W/A for Gen12 iGPUs and extension of compute pre-emption timeout to 7.5 seconds to account for compute corner

[PULL] drm-intel-gt-next

2022-09-16 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes the final drm-intel-gt-next towards 6.1. For stable platforms we have fixes for throttle reasons decoding to sysfs, GuC version update to 7.5, XeHP SDV GSC support and the usual pile of smaller fixes. DG2 and DG1 runtime PM is now mostly fixed for LMEM access via

[PULL] drm-intel-gt-next

2022-09-09 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes second drm-intel-gt-next PR towards 6.1. As the top item we're now aligning the GuC/HuC firmware versioning to meet the expectations recorded under firmware-usage-guidelines.rst. A revert of a previous (incorrect) userspace register removal for DG2 and addition of new

[PULL] drm-intel-gt-next

2022-08-24 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes the first drm-intel-gt-next PR towards 6.1. Quite a small one. As primary things, there's the parallel support of GuC v69 and v70 which already went in via -fixes, improvements to the TLB invalidation performance regressions, further DG2 enabling and improved

Re: [PULL] drm-intel-gt-next

2022-07-21 Thread Vivi, Rodrigo
On Wed, 2022-07-13 at 17:31 -0400, Rodrigo Vivi wrote: > Hi Dave and Daniel, > > On behalf of Tvrtko, who is recovering from Covid, > here goes the latest drm-intel-gt-next pull request > targeting 5.20. Hi Folks, any particular issue with this pull request? We just realized it is not yet part

[PULL] drm-intel-gt-next

2022-07-13 Thread Rodrigo Vivi
Hi Dave and Daniel, On behalf of Tvrtko, who is recovering from Covid, here goes the latest drm-intel-gt-next pull request targeting 5.20. Thanks, Rodrigo. Driver uAPI changes: - All related to the Small BAR support: (and all by Matt Auld) * add probed_cpu_visible_size * expose the avail

[PULL] drm-intel-gt-next

2022-06-29 Thread Tvrtko Ursulin
Hi Dave, Daniel, This is the first pull request for 5.20 merge window. A lot of fixes across the board, a few improvements and quite a lot of driver refactoring to prepare for Ponte Vecchio, and then a bunch of Ponte Vecchio early enablement on top. In terms of improvements, we now enable huge

[PULL] drm-intel-gt-next

2022-05-05 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here goes the final drm-intel-gt-next PR towards 5.19. A fix for a security issue affecting Tigerlake onwards and a plain fix for a race in VMA handling have landed since the previous pull. Also last two bits of DG2 enablement are included - GuC firmware version has been

[PULL] drm-intel-gt-next

2022-04-27 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here goes the first drm-intel-gt-next PR towards 5.19. A lot of stuff here across the board in terms of new features, new platform support and bug fixes. For bug fixes the most interesting are: * a fix for out of bounds kernel access in mmap ops due incorrect object bound

[PULL] drm-intel-gt-next

2022-03-02 Thread Joonas Lahtinen
Hi Dave & Daniel, Here is the last feature PR for v5.18. For new platforms we have got more DG2 enabling: small BAR foundations, 64K page support and accelerated migration. For XeHP SDV we've got flat CCS detection and compute command streamer being added. Disabling i915 build on PREEMPT_RT for

Re: [PULL] drm-intel-gt-next

2022-02-23 Thread Vivi, Rodrigo
On Tue, 2022-02-22 at 11:44 -0800, Lucas De Marchi wrote: > On Mon, Feb 21, 2022 at 11:21:35AM +0200, Jani Nikula wrote: > > On Mon, 21 Feb 2022, Dave Airlie wrote: > > > On Thu, 17 Feb 2022 at 20:26, Joonas Lahtinen > > > wrote: > > > > > > > > Hi Dave & Daniel, > > > > > > > > Here is the

Re: [PULL] drm-intel-gt-next

2022-02-22 Thread Lucas De Marchi
On Mon, Feb 21, 2022 at 11:21:35AM +0200, Jani Nikula wrote: On Mon, 21 Feb 2022, Dave Airlie wrote: On Thu, 17 Feb 2022 at 20:26, Joonas Lahtinen wrote: Hi Dave & Daniel, Here is the first drm-intel-gt-next feature PR towards v5.18. Am I missing some previous drm-intel pull?

Re: [PULL] drm-intel-gt-next

2022-02-21 Thread Jani Nikula
On Mon, 21 Feb 2022, Dave Airlie wrote: > On Thu, 17 Feb 2022 at 20:26, Joonas Lahtinen > wrote: >> >> Hi Dave & Daniel, >> >> Here is the first drm-intel-gt-next feature PR towards v5.18. > > Am I missing some previous drm-intel pull? > >

Re: [PULL] drm-intel-gt-next

2022-02-20 Thread Dave Airlie
On Thu, 17 Feb 2022 at 20:26, Joonas Lahtinen wrote: > > Hi Dave & Daniel, > > Here is the first drm-intel-gt-next feature PR towards v5.18. Am I missing some previous drm-intel pull? /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/gt/intel_workarounds.c: In function

[PULL] drm-intel-gt-next

2022-02-17 Thread Joonas Lahtinen
Hi Dave & Daniel, Here is the first drm-intel-gt-next feature PR towards v5.18. For DG2 adds subplatform G12, missing workarounds and fixes GuC loading on ARM64. C0/D0 stepping info added for RPL-S. For uAPI enables support for simple parallel submission with execlists which was previously

[PULL] drm-intel-gt-next

2021-12-23 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here goes the final PR towards 5.17. Effectively two largest logical items in this pull request are bugfixes, mainly in the GuC submission backend, and continuation of the locking refactoring being done to make both VMA and backing store handling use dma_resv locking. This is

[PULL] drm-intel-gt-next

2021-12-09 Thread Tvrtko Ursulin
Hi Dave, Daniel, Here goes the first PR towards 5.17. On the bugfixing front most user visible items are a fix for GPU hangs caused by certain media and OpenCL workloads applicable from Gen9 (Skylake) onward, a fix for GPU hangs in Gnome shell on Tigerlake platforms and a fix for runtime power

[PULL] drm-intel-gt-next

2021-10-21 Thread Joonas Lahtinen
Hi Dave & Daniel, Here comes the final feature PR for 5.16. As the biggest thing it adds multi-LRC (parallel) submission implementation for GuC and a simplified parallel submission uAPI to go with that (only works with GuC for now). It is has a similar mission to the bonded submission uAPI, take

[PULL] drm-intel-gt-next

2021-10-08 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes the first PR towards 5.16. As for the big things, this adds encrypted PXP (Protected Xe Path) support for Gen12 integrated. Take a look at the "drm/i915/pxp: add PXP documentation" for further details and the Mesa changes for how the uAPI will look like. Then adds

Re: [PULL] drm-intel-gt-next

2021-08-06 Thread Joonas Lahtinen
Quoting Joonas Lahtinen (2021-08-06 13:06:17) > Hi Dave & Daniel, > > Sorry for the big PR in advance. Had the summer vacations and did not > notice until tool late how many patches were in already before leaving. > > As requested, there is a lot of refactoring to increase the use of TTM >

[PULL] drm-intel-gt-next

2021-08-06 Thread Joonas Lahtinen
Hi Dave & Daniel, Sorry for the big PR in advance. Had the summer vacations and did not notice until tool late how many patches were in already before leaving. As requested, there is a lot of refactoring to increase the use of TTM allocator and prep for DRM scheduler. Note that at times the

[PULL] drm-intel-gt-next

2021-06-10 Thread Joonas Lahtinen
Hi Dave & Daniel, Here's the final -gt-next PR for 5.14. Two major uAPI changes for new Gen12+ platforms: Stop supporting old MMAP IOCTL (excl. TGL) and require use of MMAP_OFFSET instead. Start enabling HuC loading by default (excl. TGL and RKL). Revert for io_mapping_map_user which was

Re: [PULL] drm-intel-gt-next

2021-06-01 Thread Dave Airlie
On Wed, 2 Jun 2021 at 14:17, Dave Airlie wrote: > > On Wed, 2 Jun 2021 at 10:28, Dave Airlie wrote: > > > > This has these two patches applied, and it doesn't build. > > > > drm/i915: drop the __i915_active_call pointer packing > > drm/i915: Fix crash in auto_retire > > > > The latter patch

Re: [PULL] drm-intel-gt-next

2021-06-01 Thread Dave Airlie
On Wed, 2 Jun 2021 at 10:28, Dave Airlie wrote: > > This has these two patches applied, and it doesn't build. > > drm/i915: drop the __i915_active_call pointer packing > drm/i915: Fix crash in auto_retire > > The latter patch shouldn't be necessary after the former, please fix > that up and

Re: [PULL] drm-intel-gt-next

2021-06-01 Thread Dave Airlie
This has these two patches applied, and it doesn't build. drm/i915: drop the __i915_active_call pointer packing drm/i915: Fix crash in auto_retire The latter patch shouldn't be necessary after the former, please fix that up and resend and please build test trees before I get them in future.

Re: [PULL] drm-intel-gt-next

2021-05-28 Thread Joonas Lahtinen
Quoting Joonas Lahtinen (2021-05-28 10:25:57) > Hi Dave & Daniel, > > Here's drm-intel-gt-next pull request. > > Most notably it has the reworked DG1 uAPI (behind CONFIG_BROKEN) > as requested. Important fix for Gitlab issues #3293 and #3450 and > one another kernel crash. Adds missing

[PULL] drm-intel-gt-next

2021-05-28 Thread Joonas Lahtinen
Hi Dave & Daniel, Here's drm-intel-gt-next pull request. Most notably it has the reworked DG1 uAPI (behind CONFIG_BROKEN) as requested. Important fix for Gitlab issues #3293 and #3450 and one another kernel crash. Adds missing workarounds for Gen11 and Gen12. Hiding of modparams for compiled-out

[PULL] drm-intel-gt-next

2021-04-06 Thread Joonas Lahtinen
Hi Dave & Daniel, Bit late PR due to Easter break. Prep work for local memory support as requested. Hard hang fix for Sandybridge. Sanitize dma-buf size on import and avoid GPU reset if heartbeat callback runs before timeout. The rest is mostly small fixes and code/checkpatch cleanups.

[PULL] drm-intel-gt-next

2021-01-21 Thread Joonas Lahtinen
Hi Dave & Daniel, Here is the final PR for v5.12. One more fix for the clear residuals security mitigation. Per-engine reset for Gen7 to avoid collateral damage when some workloads misbehave, flip priority boosting when using explicit fences (sync_file), improving suspend/freeze speed and

[PULL] drm-intel-gt-next

2021-01-14 Thread Joonas Lahtinen
Hi Dave & Daniel, Here is the first PR for v5.12. There are quite a few patches accumulated after the holidays as usual: Most importantly there are fixes to the clear residual security mitigations to avoid GPU hangs caused by them. Further there is option to allow the user to decide to disable

[PULL] drm-intel-gt-next

2020-11-12 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes the drm-intel-gt-next PR for 5.11. Most importantly there is a healthy chunk of Tigerlake related fixes and a fix for user reported issue #2381 where graphics output would stop at "switching to inteldrmfb from simple". Fixes to DMA mapped sg usage in i915 to unblock

[PULL] drm-intel-gt-next

2020-09-07 Thread Joonas Lahtinen
Hi Dave & Daniel, Exactly same content as previous PR: https://lists.freedesktop.org/archives/intel-gfx/2020-September/247626.html Just rebased adding the missing S-o-b:s and updated "Fixes:" tags accordingly as requested. Regards, Joonas *** drm-intel-gt-next-2020-09-07: (Same content as

[PULL] drm-intel-gt-next

2020-09-04 Thread Joonas Lahtinen
Hi Dave & Daniel, Here goes the GT pull request for v5.10. It's the same patches as previously at "topic/drm-intel-gem-next", one dropped and a few re-ordered while creating the "drm-intel-gt-next" branch. So the patches have been part of drm-tip already for weeks. More about the PR itself at