Re: [PULL] drm-xe-next

2025-07-11 Thread Simona Vetter
On Thu, Jul 10, 2025 at 06:16:55PM -0400, Rodrigo Vivi wrote: > Hi Dave and Sima, > > Here goes our drm-xe-next towards 6.17. > I'm still considering an extra small one in the beginning > of next week if possible. > > Before going to the details of what this pull request contains, > I'd like to s

Re: [PULL] drm-xe-next

2025-07-11 Thread Simona Vetter
On Thu, Jul 10, 2025 at 06:16:55PM -0400, Rodrigo Vivi wrote: > Hi Dave and Sima, > > Here goes our drm-xe-next towards 6.17. > I'm still considering an extra small one in the beginning > of next week if possible. > > Before going to the details of what this pull request contains, > I'd like to s

Re: [PULL] drm-xe-next

2025-04-28 Thread Thomas Hellström
On Mon, 2025-04-28 at 16:27 +0200, Thomas Hellstrom wrote: > Hi Dave, Simona > > An additional drm-xe-next PR as requested on IRC. > A lot of fixes but some new stuff as detailed below. > > Please note that the top commit, > > "Drop force_alloc from xe_bo_evict in selftests" > > carries a Fixes

Re: [PULL] drm-xe-next

2025-03-07 Thread Lucas De Marchi
On Fri, Mar 07, 2025 at 08:51:03AM -0600, Lucas De Marchi wrote: On Fri, Mar 07, 2025 at 02:02:15AM -0600, Lucas De Marchi wrote: Hi Dave and Sima, Last drm-xe-next pull request for 6.15. It comes with some big features that we have been working on for some time: EU stall sampling and SVM. The

Re: [PULL] drm-xe-next

2025-03-07 Thread Lucas De Marchi
On Fri, Mar 07, 2025 at 02:02:15AM -0600, Lucas De Marchi wrote: Hi Dave and Sima, Last drm-xe-next pull request for 6.15. It comes with some big features that we have been working on for some time: EU stall sampling and SVM. The latter also touches other subsystems and provides the common parts

Re: [PULL] drm-xe-next

2024-10-25 Thread Matthew Brost
On Fri, Oct 25, 2024 at 12:45:26PM +0200, Thomas Hellström wrote: > On Fri, 2024-10-25 at 12:34 +0300, Jani Nikula wrote: > > On Fri, 25 Oct 2024, Thomas Hellström > > wrote: > > > On Thu, 2024-10-24 at 19:22 +, Matthew Brost wrote: > > > > On Thu, Oct 24, 2024 at 07:52:11PM +0200, Thomas Hell

Re: [PULL] drm-xe-next

2024-10-25 Thread Thomas Hellström
On Fri, 2024-10-25 at 12:34 +0300, Jani Nikula wrote: > On Fri, 25 Oct 2024, Thomas Hellström > wrote: > > On Thu, 2024-10-24 at 19:22 +, Matthew Brost wrote: > > > On Thu, Oct 24, 2024 at 07:52:11PM +0200, Thomas Hellstrom wrote: > > > > Hi, Dave & Simona, > > > > > > > > This week's drm-xe-

Re: [PULL] drm-xe-next

2024-10-25 Thread Jani Nikula
On Fri, 25 Oct 2024, Thomas Hellström wrote: > On Thu, 2024-10-24 at 19:22 +, 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

Re: [PULL] drm-xe-next

2024-10-25 Thread Thomas Hellström
On Thu, 2024-10-24 at 19:22 +, 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 p

Re: [PULL] drm-xe-next

2024-10-24 Thread Matthew Brost
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_asy

Re: [PULL] drm-xe-next-fixes

2024-09-19 Thread Lucas De Marchi
On Thu, Sep 19, 2024 at 09:56:47PM GMT, Lucas De Marchi wrote: Hi Dave and Simona, A few fixes for 6.11-rc1. oops, I meant 6.12-rc1, of course :) Lucas De Marchi

Re: [PULL] drm-xe-next

2024-08-27 Thread Daniel Vetter
On Thu, Aug 22, 2024 at 03:55:23PM -0500, Lucas De Marchi wrote: > Hi Dave and Sima, > > Second drm-xe-next pull request for the 6.12 cycle. > > Several fixes here that are also going through drm-xe-fixes. Most of the > other changes are the missing bits for Xe2 (LNL and BMG) and general > refact

Re: [PULL] drm-xe-next-fixes v2

2024-07-11 Thread Rodrigo Vivi
On Thu, Jul 11, 2024 at 02:29:04PM -0700, Jordan Justen wrote: > On 2024-07-11 08:18:18, Rodrigo Vivi wrote: > > Hi Dave and Sima, > > > > This is a v2 of https://lore.kernel.org/intel-xe/zo2so4t32dxqy...@intel.com/ > > > > v2 - Removed Thomas' write-back caching mode patch since Lucas will > >

Re: [PULL] drm-xe-next-fixes v2

2024-07-11 Thread Jordan Justen
On 2024-07-11 08:18:18, Rodrigo Vivi wrote: > Hi Dave and Sima, > > This is a v2 of https://lore.kernel.org/intel-xe/zo2so4t32dxqy...@intel.com/ > > v2 - Removed Thomas' write-back caching mode patch since Lucas will propagete > that through drm-xe-fixes towards 6.10. So we remove the amount of p

Re: [PULL] drm-xe-next-fixes

2024-07-10 Thread Rodrigo Vivi
On Wed, Jul 10, 2024 at 02:42:38PM -0500, Lucas De Marchi wrote: > On Tue, Jul 09, 2024 at 05:31:39PM GMT, Rodrigo Vivi wrote: > > Hi Dave and Sima, > > > > Here goes a very early drm-xe-next-fixes with 2 important fixes > > that are going to impact user space. > > > > 1. The first one is the ren

Re: [PULL] drm-xe-next-fixes

2024-07-10 Thread Lucas De Marchi
On Tue, Jul 09, 2024 at 05:31:39PM GMT, Rodrigo Vivi wrote: Hi Dave and Sima, Here goes a very early drm-xe-next-fixes with 2 important fixes that are going to impact user space. 1. The first one is the rename of the OA stuff from the bad 'perf' name to the xe_observation. Although the rename i

Re: [PULL] drm-xe-next

2024-07-05 Thread Daniel Vetter
On Tue, Jul 02, 2024 at 03:02:22PM -0400, Rodrigo Vivi wrote: > Hi Dave and Sima, > > Here goes our actual last PR towards 6.11. > One extra to make the drm-xe-next-fixes smoother. > > Mostly with fixes that would be anyway part of the > drm-xe-next-fixes, plus some more SRIOV preparation > and a

Re: [PULL] drm-xe-next

2024-02-26 Thread Lucas De Marchi
On Mon, Feb 26, 2024 at 10:46:43AM +, Daniel Stone wrote: Hi, On Mon, 26 Feb 2024 at 03:21, Lucas De Marchi wrote: All of this should be fixed by now: dim is used for applying and pushing patches, which has additional checks so that doesn't happen again. Still pending confirmation from Dan

Re: [PULL] drm-xe-next

2024-02-26 Thread Daniel Stone
Hi, On Mon, 26 Feb 2024 at 03:21, Lucas De Marchi wrote: > All of this should be fixed by now: dim is used for applying and pushing > patches, which has additional checks so that doesn't happen again. Still > pending confirmation from Daniel Stone if the git server hooks are ready > in gitlab so

Re: [PULL] drm-xe-next

2024-02-26 Thread Daniel Vetter
On Sun, Feb 25, 2024 at 09:21:00PM -0600, Lucas De Marchi wrote: > Hi Dave and Sima, > > Here's the PR for drm-xe-next for Linux v6.9. It's a big list of > changes, but it contains several fixes for things noticed throughout the > v6.8 cycle after being merged upstream, added to the linux-next, et

Re: [PULL] drm-xe-next v2

2023-12-20 Thread Dafna Hirschfeld
On 19.12.2023 19:22, Rodrigo Vivi wrote: Hi Dave and Sima, Here goes a v2 of our first pull request. First PR: https://lore.kernel.org/all/zxzta75g5vhcr...@intel.com/ The lack of committer signature blocked Dave's tools on getting that. I'm sorry for that. As you know we were maintaining this

Re: [PULL] drm-xe-next

2023-12-18 Thread Oded Gabbay
On Fri, Dec 15, 2023 at 05:28:19PM -0500, Rodrigo Vivi wrote: > Hi Dave and Sima, > > Here goes the first pull request for the drm/xe driver. > > Our team was focused on putting together a driver that uses most, if not all, > of the key drm concepts and has a functional display that is shared wit

Re: [PULL] drm-xe-next

2023-12-18 Thread Oded Gabbay
On Fri, Dec 15, 2023 at 05:28:19PM -0500, Rodrigo Vivi wrote: > Hi Dave and Sima, > > Here goes the first pull request for the drm/xe driver. > > Our team was focused on putting together a driver that uses most, if not all, > of the key drm concepts and has a functional display that is shared wit

Re: [PULL] drm-xe-next

2023-12-18 Thread Oded Gabbay
On Sat, Dec 16, 2023 at 12:28 AM Rodrigo Vivi wrote: > > Hi Dave and Sima, > > Here goes the first pull request for the drm/xe driver. > > Our team was focused on putting together a driver that uses most, if not all, > of the key drm concepts and has a functional display that is shared with i915.