> -Original Message-
> From: Intel-xe On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 08/20] drm/i915/fbc: Extract _intel_fbc_cfb_stride()
>
> From: Ville Syrjälä
>
> Pull t
> -Original Message-
> From: Intel-xe On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 11/20] drm/i915/fbc: Extract intel_fbc_max_cfb_height()
>
> From: Ville Syrjälä
>
> Pul
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 12/20] drm/i915/fbc: Extract _intel_fbc_cfb_size()
>
> From: Ville Syrjälä
>
> Pull the
> -Original Message-
> From: Intel-xe On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 13/20] drm/i915/fbc: Extract intel_fbc_cfb_cpp()
>
> From: Ville Syrjälä
>
> Extract a
> -Original Message-
> From: Intel-xe On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 14/20] drm/i915/fbc: Introduce intel_fbc_preferred_cfb_size()
>
> From: Ville Syrjälä
>
On Wed, Jul 03, 2024 at 02:21:48PM +0530, Nautiyal, Ankit K wrote:
>
> On 6/26/2024 1:48 PM, Stanislav Lisovskiy wrote:
> > Implement required changes for mode validation and compute config,
> > to support Ultrajoiner.
> > This also includes required DSC changes and checks.
> >
> > Signed-off-by:
On Tue, Jul 09, 2024 at 04:27:18PM -0400, Rodrigo Vivi wrote:
> On Fri, Jun 28, 2024 at 05:46:01PM +0300, Jani Nikula wrote:
> >
> > Hi Dave & Sima -
> >
> > Another feature pull towards v6.11, hopefully last. This should also fix
> > the 32-bit build issue [1] seen in drm-next.
>
> Sima, Dave,
> -Original Message-
> From: Intel-xe On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 15/20] drm/xe/fbdev: Fix BIOS FB vs.s stolen size checke
Nit: Typo in vs and check
> Fro
> -Original Message-
> From: Intel-xe On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 16/20] drm/i915/fbdev: Extract intel_fbdev_fb_prefer_stolen()
>
> From: Ville Syrjälä
>
> -Original Message-
> From: Intel-xe On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 17/20] drm/xe/fbdev: Extract intel_fbdev_fb_prefer_stolen()
>
> From: Ville Syrjälä
>
>
> -Original Message-
> From: Intel-xe On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 18/20] drm/xe/fbdev: Use the same logic for fbdev stolen
> takever and fresh allocation
>
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 19/20] drm/i915/fbdev: Adjust fbdev stolen mem usage heuristic
>
> From: Ville Syrjälä
>
> -Original Message-
> From: Intel-xe On Behalf Of Ville
> Syrjala
> Sent: Friday, July 5, 2024 8:23 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: intel...@lists.freedesktop.org
> Subject: [PATCH 20/20] drm/xe/fbdev: Adjust fbdev stolen mem usage heuristic
>
> From: Ville Syrjälä
>
We already teach lockdep that dma_resv nests within drm_modeset_lock,
but there's a lot more: All drm kms ioctl rely on being able to
put/get_user while holding modeset locks, so we really need a
might_fault in there too to complete the picture. Add it.
Motivated by a syzbot report that blew up on
console_lock is the outermost subsystem lock for a lot of subsystems,
which means get/put_user must nest within. Which means it cannot be
acquired somewhere deeply nested in other locks, and most definitely
not while holding fs locks potentially needed to resolve faults.
console_trylock is the bes
On 09/07/2024 15:02, Tvrtko Ursulin wrote:
On 09/07/2024 13:53, Nitin Gote wrote:
We're seeing a GPU HANG issue on a CHV platform, which was caused by
bac24f59f454 ("drm/i915/execlists: Enable coarse preemption boundaries
for gen8").
Gen8 platform has only timeslice and doesn't support a p
On Wed, Jul 10, 2024 at 09:46:51AM +0200, Thorsten Blum wrote:
> As the comment explains, the if check ensures that the divisor oa_period
> is a u32. Explicitly cast oa_period to u32 to remove the following
> Coccinelle/coccicheck warning reported by do_div.cocci:
>
> WARNING: do_div() does a 64
Am 10.07.24 um 11:31 schrieb Daniel Vetter:
We already teach lockdep that dma_resv nests within drm_modeset_lock,
but there's a lot more: All drm kms ioctl rely on being able to
put/get_user while holding modeset locks, so we really need a
might_fault in there too to complete the picture. Add it.
== Series Details ==
Series: series starting with [1/2] drm: Add might_fault to drm_modeset_lock
priming
URL : https://patchwork.freedesktop.org/series/135935/
State : warning
== Summary ==
Error: dim checkpatch failed
e6e5d57c8c88 drm: Add might_fault to drm_modeset_lock priming
-:20: WARNIN
== Series Details ==
Series: series starting with [1/2] drm: Add might_fault to drm_modeset_lock
priming
URL : https://patchwork.freedesktop.org/series/135935/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately
On Tue, Jul 09, 2024 at 03:28:15PM -0500, Lucas De Marchi wrote:
> On Fri, Jul 05, 2024 at 05:52:50PM GMT, Ville Syrjälä wrote:
> >From: Ville Syrjälä
> >
> >Consolidate the "should we allocate fbdev fb in stolen?"
> >check into a helper function. Makes it easier to change the
> >heuristics withou
== Series Details ==
Series: series starting with [1/2] drm: Add might_fault to drm_modeset_lock
priming
URL : https://patchwork.freedesktop.org/series/135935/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15057 -> Patchwork_135935v1
==
On Wed, 10 Jul 2024 at 13:39, Christian König wrote:
>
> Am 10.07.24 um 11:31 schrieb Daniel Vetter:
> > We already teach lockdep that dma_resv nests within drm_modeset_lock,
> > but there's a lot more: All drm kms ioctl rely on being able to
> > put/get_user while holding modeset locks, so we rea
On Wed, Jul 10, 2024 at 01:55:32PM +0200, Thorsten Blum wrote:
> On 10. Jul 2024, at 13:38, Ville Syrjälä
> wrote:
> > On Wed, Jul 10, 2024 at 09:46:51AM +0200, Thorsten Blum wrote:
> >> As the comment explains, the if check ensures that the divisor oa_period
> >> is a u32. Explicitly cast oa_per
Am 10.07.24 um 13:58 schrieb Daniel Vetter:
On Wed, 10 Jul 2024 at 13:39, Christian König wrote:
Am 10.07.24 um 11:31 schrieb Daniel Vetter:
We already teach lockdep that dma_resv nests within drm_modeset_lock,
but there's a lot more: All drm kms ioctl rely on being able to
put/get_user while
From: Ville Syrjälä
On ilk/snb the pipe may be configured to place the LUT before or
after the CSC depending on various factors, but as there is only
one LUT (no split mode like on IVB+) we only advertise a gamma_lut
and no degamma_lut in the uapi to avoid confusing userspace.
This can cause a p
console_lock is the outermost subsystem lock for a lot of subsystems,
which means get/put_user must nest within. Which means it cannot be
acquired somewhere deeply nested in other locks, and most definitely
not while holding fs locks potentially needed to resolve faults.
console_trylock is the bes
== Series Details ==
Series: drm/i915: Fix readout degamma_lut mismatch on ilk/snb
URL : https://patchwork.freedesktop.org/series/135939/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15057 -> Patchwork_135939v1
Summary
---
On 7/10/2024 2:07 PM, Lisovskiy, Stanislav wrote:
On Wed, Jul 03, 2024 at 02:21:48PM +0530, Nautiyal, Ankit K wrote:
On 6/26/2024 1:48 PM, Stanislav Lisovskiy wrote:
Implement required changes for mode validation and compute config,
to support Ultrajoiner.
This also includes required DSC chan
As the comment explains, the if check ensures that the divisor oa_period
is a u32. Explicitly cast oa_period to u32 to remove the following
Coccinelle/coccicheck warning reported by do_div.cocci:
WARNING: do_div() does a 64-by-32 division, please consider using div64_u64
instead
Signed-off-by:
On 2024-07-10, Daniel Vetter wrote:
> console_lock is the outermost subsystem lock for a lot of subsystems,
> which means get/put_user must nest within. Which means it cannot be
> acquired somewhere deeply nested in other locks, and most definitely
> not while holding fs locks potentially needed t
On 10. Jul 2024, at 13:38, Ville Syrjälä wrote:
> On Wed, Jul 10, 2024 at 09:46:51AM +0200, Thorsten Blum wrote:
>> As the comment explains, the if check ensures that the divisor oa_period
>> is a u32. Explicitly cast oa_period to u32 to remove the following
>> Coccinelle/coccicheck warning report
== Series Details ==
Series: series starting with [1/2] drm: Add might_fault to drm_modeset_lock
priming (rev2)
URL : https://patchwork.freedesktop.org/series/135935/
State : warning
== Summary ==
Error: dim checkpatch failed
9e9ca832c1d9 drm: Add might_fault to drm_modeset_lock priming
-:20:
== Series Details ==
Series: series starting with [1/2] drm: Add might_fault to drm_modeset_lock
priming (rev2)
URL : https://patchwork.freedesktop.org/series/135935/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked sep
== Series Details ==
Series: series starting with [1/2] drm: Add might_fault to drm_modeset_lock
priming (rev2)
URL : https://patchwork.freedesktop.org/series/135935/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15057 -> Patchwork_135935v2
===
> -Original Message-
> From: Tvrtko Ursulin
> Sent: Wednesday, July 10, 2024 4:22 PM
> To: Gote, Nitin R ; intel-gfx@lists.freedesktop.org
> Cc: dri-de...@lists.freedesktop.org; Shyti, Andi ;
> chris.p.wil...@linux.intel.com; Das, Nirmoy ;
> janusz.krzyszto...@linux.intel.com; sta...@vge
== Series Details ==
Series: drm/i915: Explicitly cast divisor to fix Coccinelle warning
URL : https://patchwork.freedesktop.org/series/135942/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15058 -> Patchwork_135942v1
Summa
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
On 02/07/2024 18:57, Jim Cromie wrote:
Several tests are dependent upon config choices. Lets avoid failing
where that is noise.
The KCONFIG_CONFIG var exists to convey the config-file around. If
the var names a file, read it and extract the relevant CONFIG items,
and use them to skip the dep
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
DPKGC can now be enabled with VRR enabled if Vmin = Vmax = Flipline
is met.
Bspec: 68986
Signed-off-by: Suraj Kandpal
---
drivers/gpu/drm/i915/display/skl_watermark.c | 24 +++-
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/skl_water
We're seeing a GPU HANG issue on a CHV platform, which was caused by
bac24f59f454 ("drm/i915/execlists: Enable coarse preemption boundaries for
gen8").
Gen8 platform has only timeslice and doesn't support a preemption mechanism
as engines do not have a preemption timer and doesn't send an irq if
As per recommendation in the workarounds:
WA_14021987551, Wa_16023588340:
There is an issue with accessing Stolen memory pages due a
hardware limitation. Limit the usage of stolen memory for
fbdev for LNL+. Don't use BIOS FB from stolen on LNL+ and
assign the same from system memory.
Signed-off-b
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave"
with more appropriate terms. Inspired by and following on to Wolfram's
series to fix drivers/i2c/[1], fix the terminology for users of the
I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists
in the spec
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave"
with more appropriate terms. Inspired by Wolfram's series to fix drivers/i2c/,
fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that
the approved verbiage exists in the specification.
Acked-by: Alex
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave"
with more appropriate terms. Inspired by Wolfram's series to fix drivers/i2c/,
fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that
the approved verbiage exists in the specification.
Acked-by: Thoma
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave"
with more appropriate terms. Inspired by Wolfram's series to fix drivers/i2c/,
fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that
the approved verbiage exists in the specification.
Reviewed-by: Ro
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave"
with more appropriate terms. Inspired by Wolfram's series to fix drivers/i2c/,
fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that
the approved verbiage exists in the specification.
Reviewed-by: Ma
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave"
with more appropriate terms. Inspired by Wolfram's series to fix drivers/i2c/,
fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that
the approved verbiage exists in the specification.
Acked-by: Thoma
I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave"
with more appropriate terms. Inspired by Wolfram's series to fix drivers/i2c/,
fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that
the approved verbiage exists in the specification.
Acked-by: Thoma
== Series Details ==
Series: drm/i915/dpkgc: Add VRR condition for DPKGC Enablement
URL : https://patchwork.freedesktop.org/series/135966/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15060 -> Patchwork_135966v1
Summary
--
== Series Details ==
Series: drm/i915/gt: Do not consider preemption during execlists_dequeue for
gen8 (rev2)
URL : https://patchwork.freedesktop.org/series/135901/
State : warning
== Summary ==
Error: dim checkpatch failed
55e56364a5b9 drm/i915/gt: Do not consider preemption during execlists
== Series Details ==
Series: drm/i915/gt: Do not consider preemption during execlists_dequeue for
gen8 (rev2)
URL : https://patchwork.freedesktop.org/series/135901/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15060 -> Patchwork_135901v2
=
== Series Details ==
Series: drm/xe/fbdev: Limit the usage of stolen for LNL+
URL : https://patchwork.freedesktop.org/series/135971/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15060 -> Patchwork_135971v1
Summary
---
54 matches
Mail list logo
