== Series Details ==
Series: Expose max and current bpc via debugfs (rev6)
URL : https://patchwork.freedesktop.org/series/102502/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11624 -> Patchwork_102502v6
Summary
---
In case framebuffer setup is deferred it will happen in HPD worker.
Then on driver removal we should assure it will not happen after
drm_fb_helper_unregister_fbi, otherwise we risk UAF.
The patch should fix following GPF:
[272.634530] general protection fault, probably for non-canonical address
Currently selective fetch area calculation ends up as bogus area in
at least following cases:
1. Updated plane is partially or fully outside pipe area
2. Big fb with only part of memory area used for plane
These end up as y1 = 0, y2 = 4 or y2 being outside pipe area. This
patch set addresses
Currently we have some corner cases where area calculation fails. For
these sel fetch area calculation ends up having update area as y1 = 0,
y2 = 4. Instead of these values safer option is full update.
One of such for example is big fb with offset. We don't have usable
offset in
Current update area calculation is not handling situation where
e.g. cursor plane is fully or partially outside pipe area.
Fix this by checking damage area against pipe_src area using
drm_rect_intersect.
v2: Set x1 and x2 in damaged_area initialization
Closes:
== Series Details ==
Series: Expose max and current bpc via debugfs (rev6)
URL : https://patchwork.freedesktop.org/series/102502/
State : warning
== Summary ==
Error: dim checkpatch failed
1ca3c5bc0e7d drm/debug: Expose connector's max supported bpc via debugfs
-:21: WARNING:BAD_SIGN_OFF:
On Fri, 2022-05-06 at 18:40 +, Souza, Jose wrote:
> On Fri, 2022-05-06 at 18:28 +, Hogander, Jouni wrote:
> > On Fri, 2022-05-06 at 15:29 +, Souza, Jose wrote:
> > > On Fri, 2022-05-06 at 08:48 +0300, Jouni Högander wrote:
> > > > Currently we have some corner cases where area
Modes like 4K100, 4K120, 8K50, 8K60 need FRL and/or DSC from source.
Since FRL and DSC are not currently supported natively by intel
platforms (are supported only via DP-HDMI2.1 PCONs), these modes must
be pruned as per spec.
Currently these modes are not getting pruned as we check the TMDS clock,
As per Sec 7.8.1 of HDMI2.1 spec, sources that support modes:
4K100, 4K120, 8K50, 8K60 must support these modes in at least one of
the below formats:
i) uncompressed FRL, 420 format and min of 10 bpc, or
ii) compressed FRL, 444 format and min of 10 bpc.
Since FRL and DSC are not supported
HF-VSDB/SCDB has bits to advertise support for 16, 12 and 10 bpc.
If none of the bits are set, the minimum bpc supported with DSC is 8.
This patch corrects the min bpc supported to be 8, instead of 0.
Fixes: 76ee7b905678 ("drm/edid: Parse DSC1.2 cap fields from HFVSDB block")
Cc: Ankit Nautiyal
== Series Details ==
Series: drm/i915/guc: Refactor CT access to use iosys_map (rev5)
URL : https://patchwork.freedesktop.org/series/101148/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11625 -> Patchwork_101148v5
Summary
== Series Details ==
Series: drm/i915/guc: Refactor CT access to use iosys_map (rev5)
URL : https://patchwork.freedesktop.org/series/101148/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
From: Siva Mullati
ver2: remove newly added iosys map api from ver1
ver3: address review comments
ver4: remove accessing vaddr
This is continuation to the below patch series to use iosys map
APIs, to use CT commands and descriptors.
https://patchwork.freedesktop.org/series/99711/
Siva Mullati
From: Siva Mullati
Convert CT commands and descriptors to use iosys_map rather
than plain pointer and save it in the intel_guc_ct_buffer struct.
This will help with ct_write and ct_read for cmd send and receive
after the initialization by abstracting the IO vs system memory.
Signed-off-by: Siva
[TLDR: I'm adding this regression report to the list of tracked
regressions; all text from me you find below is based on a few templates
paragraphs you might have encountered already already in similar form.]
Hi, this is your Linux kernel regression tracker. Top-posting for once,
to make this
On Fri, 2022-05-06 at 15:43 +, Souza, Jose wrote:
> On Fri, 2022-05-06 at 08:48 +0300, Jouni Högander wrote:
> > Current update area calculation is not handling situation where
> > e.g. cursor plane is fully or partially outside pipe area.
> >
> > Fix this by checking damage area against
On Sat, 30 Apr 2022 22:04:55 +0200,
Mauro Carvalho Chehab wrote:
>
> On some devices, the hda driver needs to hook into a video driver,
> in order to be able to properly access the audio hardware and/or
> the power management function.
>
> That's the case of several snd_hda_intel devices that
On 29/04/2022 11:04, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
We have a statement from HW designers that the GPU read regression when
using 2M pages was fixed from Icelake onwards, which was also confirmed
by bencharking Eero did last year:
"""
When IOMMU is disabled, enabling THP causes
On Sat, 7 May 2022 at 14:29, José Roberto de Souza wrote:
>
> This feature is supported in graphics version 6 and newer in all
> integrated GPUs not including VLC and CHV, so we can drop this flag
> for a not so complicated macro check.
s/VLC/VLV/ ?
There are also some gen9/10 platforms that
We'll need to propagate drm_edid everywhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 52 --
1 file changed, 27 insertions(+), 25 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index
We'll need to propagate drm_edid everywhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 5d8744a7b62e..037102a4d0b5 100644
---
We'll need to propagate drm_edid everywhere.
v2: Drop incorrect NULL name check (Dan Carpenter)
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c
We'll need to propagate drm_edid everywhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index c2887012add0..8acdb08a8571 100644
---
We'll need to propagate drm_edid everywhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 8acdb08a8571..5d8744a7b62e 100644
---
We'll need to propagate drm_edid everywhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 27 +--
1 file changed, 13 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index f54699422bca..c2887012add0
We'll need to propagate drm_edid everywhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 037102a4d0b5..51d918c66a26 100644
---
We'll need to propagate drm_edid everywhere.
v2: Handle NULL EDID pointer (Ville, CI)
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 34 +-
1 file changed, 21 insertions(+), 13 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c
We'll need to propagate drm_edid everywhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 27 ++-
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index bea8f33c58ad..364949e146a9
Quoting José Roberto de Souza (2022-05-07 16:28:50)
> No need to have this parameter in intel_device_info struct
> as this feature is supported by Broadwell, Haswell all platforms with
> display version 9 or newer.
This is opposite of the direction we want to move to.
We want to embrace the
On 07/05/2022 00:34, Matt Roper wrote:
On Thu, Apr 28, 2022 at 01:18:42PM +0100, Tvrtko Ursulin wrote:
Hi,
On 28/04/2022 00:07, Matt Roper wrote:
Rather than storing subslice masks internally as u8[] (inside the sseu
structure) and u32 (everywhere else), let's move over to using an
On 09/05/2022 15:01, Souza, Jose wrote:
On Mon, 2022-05-09 at 14:32 +0100, Tvrtko Ursulin wrote:
On 05/05/2022 20:35, José Roberto de Souza wrote:
No need to have this parameter in intel_device_info struct
as all platforms with display version 9 or newer, haswell or broadwell
supports it.
We'll need to propagate drm_edid everywhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 96e3f9327044..e4fdf742645b 100644
---
Only one of the conditions can be true.
Suggested-by: Ville Syrjälä
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/drm_edid.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
We'll need to propagate drm_edid everywhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 95 ++
1 file changed, 46 insertions(+), 49 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index
We'll need to propagate drm_edid everywhere. This is a clunky start, but
a start nonetheless. We'll eventually convert all of the EDID parsing to
struct drm_edid.
Initially, we'll just create the struct drm_edid in stack. This will be
the compat layer for legacy struct edid code. In the future,
We'll need to propagate drm_edid everywhere.
v2: Use drm_edid_legacy_init()
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 48 +++---
1 file changed, 29 insertions(+), 19 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c
We have an iterator for this, use it. It does include the base block,
but its tag is 0 and will be skipped.
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/drm_edid.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git
Introduce new opaque type struct drm_edid to encapsulate the EDID data
and the size allocated for it. The contents will be private to
drm_edid.c.
There are a number of reasons for adding a container around struct edid:
* struct edid is a raw blob pointer to data that usually originates
outside
v2 of [1] with some NULL deref bugs and checkpatch/sparse warnings
fixed.
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/103665/
Jani Nikula (25):
drm/edid: use else-if in CTA extension parsing
drm/edid: convert drm_for_each_detailed_block() to edid iter
drm/edid: add struct
On 05/05/2022 20:35, José Roberto de Souza wrote:
No need to have this parameter in intel_device_info struct
as all platforms with display version 9 or newer, haswell or broadwell
supports it.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load
On Mon, 2022-05-09 at 10:24 +0300, Jouni Högander wrote:
> Currently we have some corner cases where area calculation fails. For
> these sel fetch area calculation ends up having update area as y1 = 0,
> y2 = 4. Instead of these values safer option is full update.
>
> One of such for example is
On 09/05/2022 11:49, Matthew Auld wrote:
On 29/04/2022 11:04, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
We have a statement from HW designers that the GPU read regression when
using 2M pages was fixed from Icelake onwards, which was also confirmed
by bencharking Eero did last year:
"""
On Mon, 2022-05-09 at 15:38 +0300, Joonas Lahtinen wrote:
> Quoting José Roberto de Souza (2022-05-07 16:28:50)
> > No need to have this parameter in intel_device_info struct
> > as this feature is supported by Broadwell, Haswell all platforms with
> > display version 9 or newer.
>
> This is
We'll need to propagate drm_edid everywhere.
v2: Rebase
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_displayid.c | 16
drivers/gpu/drm/drm_edid.c | 17 ++---
include/drm/drm_displayid.h | 6 +++---
include/drm/drm_edid.h | 6 --
4
We'll need to propagate drm_edid everywhere. Also make version_greater()
a function for type safety.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 29 +
1 file changed, 17 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c
We'll need to propagate drm_edid everywhere.'
v2: Handle NULL EDID pointer (Ville, CI)
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 37 +++--
1 file changed, 23 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c
We'll need to propagate drm_edid everywhere.
v2: Fix checkpatch warning on superfluous parens
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c
We'll need to propagate drm_edid everywhere.
v2: Handle NULL drm_edid
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index
We'll need to propagate drm_edid everywhere.
v2: Rebase
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index
We'll need to propagate drm_edid everywhere.
v2: Handle NULL EDID pointer (Ville, CI)
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 33 -
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c
We'll need to propagate drm_edid everywhere.
v2: Handle NULL EDID pointer (Ville, CI)
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 37 ++---
1 file changed, 22 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c
We'll need to propagate drm_edid everywhere.
v2: Handle NULL EDID pointer (Ville, CI)
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_edid.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index
On Mon, 2022-05-09 at 10:24 +0300, Jouni Högander wrote:
> Current update area calculation is not handling situation where
> e.g. cursor plane is fully or partially outside pipe area.
>
> Fix this by checking damage area against pipe_src area using
> drm_rect_intersect.
>
> v2: Set x1 and x2 in
On Mon, 2022-05-09 at 17:05 +0300, Jani Nikula wrote:
> On Mon, 09 May 2022, Tvrtko Ursulin wrote:
> > On 05/05/2022 20:35, José Roberto de Souza wrote:
> > > No need to have this parameter in intel_device_info struct
> > > as all platforms with display version 9 or newer, haswell or broadwell
>
On Mon, 2022-05-09 at 14:32 +0100, Tvrtko Ursulin wrote:
> On 05/05/2022 20:35, José Roberto de Souza wrote:
> > No need to have this parameter in intel_device_info struct
> > as all platforms with display version 9 or newer, haswell or broadwell
> > supports it.
> >
> > As a side effect of the
On Mon, 2022-05-09 at 12:09 +0100, Matthew Auld wrote:
> On Sat, 7 May 2022 at 14:29, José Roberto de Souza
> wrote:
> >
> > This feature is supported in graphics version 6 and newer in all
> > integrated GPUs not including VLC and CHV, so we can drop this flag
> > for a not so complicated
On Mon, 09 May 2022, Tvrtko Ursulin wrote:
> On 05/05/2022 20:35, José Roberto de Souza wrote:
>> No need to have this parameter in intel_device_info struct
>> as all platforms with display version 9 or newer, haswell or broadwell
>> supports it.
>>
>> As a side effect of the of removal this
On Mon, 2022-05-09 at 15:52 +0100, Matthew Auld wrote:
> On Mon, 9 May 2022 at 15:05, Souza, Jose wrote:
> >
> > On Mon, 2022-05-09 at 12:09 +0100, Matthew Auld wrote:
> > > On Sat, 7 May 2022 at 14:29, José Roberto de Souza
> > > wrote:
> > > >
> > > > This feature is supported in graphics
== Series Details ==
Series: drm/i915/guc: Refactor CT access to use iosys_map (rev5)
URL : https://patchwork.freedesktop.org/series/101148/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11625_full -> Patchwork_101148v5_full
On Mon, 2022-05-09 at 15:27 +0100, Tvrtko Ursulin wrote:
> On 09/05/2022 15:01, Souza, Jose wrote:
> > On Mon, 2022-05-09 at 14:32 +0100, Tvrtko Ursulin wrote:
> > > On 05/05/2022 20:35, José Roberto de Souza wrote:
> > > > No need to have this parameter in intel_device_info struct
> > > > as all
Hello Jose,
Thanks much for the patch. I tested it on chrome system and the patch works.
Adding my Tested-by.
Tested-by: Vidya Srinivas
Regards
Vidya
> -Original Message-
> From: Souza, Jose
> Sent: Tuesday, May 3, 2022 2:11 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: Srinivas,
On some devices, the hda driver needs to hook into a video driver,
in order to be able to properly access the audio hardware and/or
the power management function.
That's the case of several snd_hda_intel devices that depends on
i915 driver.
Ensure that a proper reference between the snd-hda
Currently, kernel/module annotates module dependencies when
request_symbol is used, but it doesn't cover more complex inter-driver
dependencies that are subsystem and/or driver-specific.
That's because module_try_get() and symbol_get() doesn't try to
setup the module owner.
In the case of hdmi
There's no such function, and __symbol_get() is already declared
as GPL. So, this is likely a left-over.
Signed-off-by: Mauro Carvalho Chehab
---
See [PATCH v6 0/4] at:
https://lore.kernel.org/all/cover.1652113087.git.mche...@kernel.org/
include/linux/module.h | 1 -
1 file changed, 1
Sometimes, device drivers are bound into each other via try_module_get(),
making such references invisible when looking at /proc/modules or lsmod.
Add a function to allow setting up module references for such
cases, and call it when try_module_get() is used.
Reviewed-by: Dan Williams
Some Kernel modules use symbol_get() or symbol_request() in order
to bind into other drivers. That's the case, for instance, of
media dvb drivers that hook the frontend drivers via I2C using
dvb_attach() macro.
When such bindings happen, one needs first to unload/unbind the
driver that got the
On Mon, 9 May 2022 at 15:05, Souza, Jose wrote:
>
> On Mon, 2022-05-09 at 12:09 +0100, Matthew Auld wrote:
> > On Sat, 7 May 2022 at 14:29, José Roberto de Souza
> > wrote:
> > >
> > > This feature is supported in graphics version 6 and newer in all
> > > integrated GPUs not including VLC and
== Series Details ==
Series: Expose max and current bpc via debugfs (rev7)
URL : https://patchwork.freedesktop.org/series/102502/
State : warning
== Summary ==
Error: dim checkpatch failed
dd718ee48d2d drm/debug: Expose connector's max supported bpc via debugfs
-:21: WARNING:BAD_SIGN_OFF:
== Series Details ==
Series: Fixes for selective fetch area calculation (rev2)
URL : https://patchwork.freedesktop.org/series/103659/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11626 -> Patchwork_103659v2
Summary
== Series Details ==
Series: Expose max and current bpc via debugfs (rev7)
URL : https://patchwork.freedesktop.org/series/102502/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11626 -> Patchwork_102502v7
Summary
---
From: Siva Mullati
Convert slpc shared data to use iosys_map rather than
plain pointer and save it in the intel_guc_slpc struct.
This will help with in read and update slpc shared data
after the slpc init by abstracting the IO vs system memory.
Signed-off-by: Siva Mullati
---
From: Siva Mullati
Ver2: remove accessing drm_cflush for io memory
This is continuation to the original patch series to use iosys map
APIs to use slpc shared data commands and descriptors.
https://patchwork.freedesktop.org/series/99711/
Siva Mullati (1):
drm/i915/guc: Convert slpc to
Em Thu, 5 May 2022 23:35:29 +0200
Andi Shyti escreveu:
> Hi Mauro,
>
> [...]
>
> > +static int ref_module_dependency(struct module *mod, struct module *this)
> > +{
> > + int ret;
> > +
> > + if (!this || !this->name)
> > + return -EINVAL;
> > +
> > + if (mod == this)
> > +
== Series Details ==
Series: drm/edid: introduce struct drm_edid (rev3)
URL : https://patchwork.freedesktop.org/series/103665/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11626 -> Patchwork_103665v3
Summary
---
== Series Details ==
Series: Let userspace know when snd-hda-intel needs i915
URL : https://patchwork.freedesktop.org/series/103760/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/103760/revisions/1/mbox/ not
applied
Applying: module: drop
On Mon, May 09, 2022 at 06:23:35PM +0200, Mauro Carvalho Chehab wrote:
> Currently, kernel/module annotates module dependencies when
> request_symbol is used, but it doesn't cover more complex inter-driver
> dependencies that are subsystem and/or driver-specific.
>
At this pount v5.18-rc7 is out
== Series Details ==
Series: drm/i915/fbdev: disable HPD before framebuffer unregistration
URL : https://patchwork.freedesktop.org/series/103738/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11626 -> Patchwork_103738v1
== Series Details ==
Series: drm/edid: introduce struct drm_edid (rev3)
URL : https://patchwork.freedesktop.org/series/103665/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-
== Series Details ==
Series: drm/i915/guc: Refactor slpc shared data access to use iosys_map (rev2)
URL : https://patchwork.freedesktop.org/series/101430/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11626 -> Patchwork_101430v2
This series
1. Fixes a bug introduced in GuC Error Capture that
was sharing the memmap of the multi-region GuC
logging buffer.
1. Adds support for unaligned wc memcpy during the
copying of logs to relay channel.
2. Renames the debugfs file for controlling GuC relay
When GuC-Error-Capture was introduced, we created
buf_in_use as a way to identify if relay logging
had started. It is meant to replace the previous
method where a mmap of the GuC log buffer was
the indicator but not since GuC Error Capture
shares that mapping throughout operation.
However, that
GuC log relay debugfs name for the control handle vs the actual relay
channel are vague. Fix them so it's obvious from the name.
Signed-off-by: Alan Previn
---
drivers/gpu/drm/i915/gt/uc/intel_guc_log.c| 2 +-
.../drm/i915/gt/uc/intel_guc_log_debugfs.c| 22 +--
2 files
In order to provide alignment between IGT intel_guc_logger tool and
i915 kernel's guc log relay channels without requiring updating both
repositories everytime a sizing change is made, provide that info
via debugfs files.
Signed-off-by: Alan Previn
---
drivers/gpu/drm/i915/gt/uc/intel_guc_log.c
All other GuC Relay Logging debugfs handles including recent
additions are under the 'i915/gt/uc/path' so let's also move
'guc_log_relay_chan' to its proper home.
Signed-off-by: Alan Previn
---
drivers/gpu/drm/i915/gt/uc/intel_guc.h| 2 ++
drivers/gpu/drm/i915/gt/uc/intel_guc_log.c|
Add a helper to get GuC log buffer size.
Signed-off-by: Alan Previn
---
drivers/gpu/drm/i915/gt/uc/intel_guc_log.c | 49 --
1 file changed, 27 insertions(+), 22 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_log.c
Add usage of unaligned wc mempy in read_update_log_buffer
as newer formats of GuC debug-log-events are no longer
guaranteed to be exactly 4-dwords long per event.
Signed-off-by: Alan Previn
---
drivers/gpu/drm/i915/gt/uc/intel_guc_log.c | 9 ++---
1 file changed, 6 insertions(+), 3
== Series Details ==
Series: Prune unsupported modes as per HDMI2.1 spec
URL : https://patchwork.freedesktop.org/series/103741/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11626 -> Patchwork_103741v1
Summary
---
== Series Details ==
Series: Fixes for selective fetch area calculation (rev2)
URL : https://patchwork.freedesktop.org/series/103659/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11626_full -> Patchwork_103659v2_full
On Wed, Apr 27, 2022 at 08:41:35AM -0700, Niranjana Vishwanathapura wrote:
On Wed, Apr 20, 2022 at 03:45:25PM -0700, Niranjana Vishwanathapura wrote:
On Thu, Mar 31, 2022 at 10:28:48AM +0200, Daniel Vetter wrote:
Adding a pile of people who've expressed interest in vm_bind for their
drivers.
== Series Details ==
Series: drm/i915/fbdev: disable HPD before framebuffer unregistration (rev3)
URL : https://patchwork.freedesktop.org/series/103738/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11626 -> Patchwork_103738v3
== Series Details ==
Series: drm/i915/fbdev: disable HPD before framebuffer unregistration (rev2)
URL : https://patchwork.freedesktop.org/series/103738/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11626 -> Patchwork_103738v2
== Series Details ==
Series: Update GuC relay logging debugfs
URL : https://patchwork.freedesktop.org/series/103767/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: Update GuC relay logging debugfs
URL : https://patchwork.freedesktop.org/series/103767/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11626 -> Patchwork_103767v1
Summary
---
**WARNING**
On 08/05/2022 15:38, Hans de Goede wrote:
Hi All,
When running a 5.18-rc4 (and -rc5) kernel on a Chuwi Hi 8, which is
a Bay Trail based tablet with 2G RAM and a 1200x1920 DSI panel.
I noticed that gnome-shell was misrendering. Many UI elements were
missing (they were all black) and at the gdm
== Series Details ==
Series: Prune unsupported modes as per HDMI2.1 spec
URL : https://patchwork.freedesktop.org/series/103741/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11626_full -> Patchwork_103741v1_full
Summary
Hi Ashutosh,
On Wed, Apr 27, 2022 at 01:38:33PM -0700, Ashutosh Dixit wrote:
> All kmalloc'd kobjects need a kobject_put() to free memory. For example in
> previous code, kobj_gt_release() never gets called. The requirement of
> kobject_put() now results in a slightly different code organization.
96 matches
Mail list logo
