tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 6ba8a227fd19d19779005fb66ad7562608e1df83 Add linux-next specific
files for 20230210
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202301302110.metnwkbd-...@intel.com
https
On Thursday, 9 February 2023 20:32:31 CET Janusz Krzysztofik wrote:
> If any of *-without-i915 subtests fails or skips for any reason, it may
> leave the i915 module unloaded while keeping our device list populated
> with initially collected data. In a follow up igt_fixture section we then
> try
== Series Details ==
Series: drm/i915/uapi/huc: two levels of HuC authentication
URL : https://patchwork.freedesktop.org/series/113864/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12723_full -> Patchwork_113864v1_full
On Fri, Feb 10, 2023 at 06:21:06PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/xehp: LNCF/LBCF workarounds should be on the GT list
> URL : https://patchwork.freedesktop.org/series/113857/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from
== Series Details ==
Series: drm/i915/pxp: Add MTL PXP Support (rev4)
URL : https://patchwork.freedesktop.org/series/112647/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12723_full -> Patchwork_112647v4_full
Summary
On Tue, Feb 7, 2023 at 9:07 AM Gustavo Sousa wrote:
>
> The following changes since commit 5c11a3742947810ee8bffbd476eb5a1b0c7999f2:
>
> amdgpu: Add VCN 4.0.2 firmware (2023-01-25 07:40:41 -0500)
>
> are available in the Git repository at:
>
> git://anongit.freedesktop.org/drm/drm-firmware
On Thu, Feb 2, 2023 at 11:56 AM Gustavo Sousa wrote:
>
> The following changes since commit 5c11a3742947810ee8bffbd476eb5a1b0c7999f2:
>
> amdgpu: Add VCN 4.0.2 firmware (2023-01-25 07:40:41 -0500)
>
> are available in the Git repository at:
>
>
== Series Details ==
Series: drm/i915/gt: Use i915 instead of dev_priv as name for the private device
URL : https://patchwork.freedesktop.org/series/113899/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12729 -> Patchwork_113899v1
== Series Details ==
Series: drm/i915/xehp: LNCF/LBCF workarounds should be on the GT list
URL : https://patchwork.freedesktop.org/series/113857/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12722_full -> Patchwork_113857v1_full
== Series Details ==
Series: drm/i915/gt: Make sure that errors are propagated through request chains
URL : https://patchwork.freedesktop.org/series/113892/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12727 -> Patchwork_113892v1
== Series Details ==
Series: series starting with [1/2] drm/i915: Populate wm.max_level for everyone
(rev3)
URL : https://patchwork.freedesktop.org/series/113808/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12722_full -> Patchwork_113808v3_full
On Tue, Feb 7, 2023 at 10:21 AM Jani Nikula wrote:
>
> From: Ville Syrjälä
>
> CONFIG_DRM_USE_DYNAMIC_DEBUG breaks debug prints for (at least modular)
> drm drivers. The debug prints can be reinstated by manually frobbing
> /sys/module/drm/parameters/debug after the fact, but at that point the
>
On Fri, Feb 10, 2023 at 09:20:25AM -0800, Umesh Nerlige Ramappa wrote:
On Thu, Feb 09, 2023 at 12:50:39PM +0100, Janusz Krzysztofik wrote:
Users reported oopses on list corruptions when using i915 perf with a
number of concurrently running graphics applications. That indicates we
are currently
On Thu, Feb 09, 2023 at 12:50:39PM +0100, Janusz Krzysztofik wrote:
Users reported oopses on list corruptions when using i915 perf with a
number of concurrently running graphics applications. That indicates we
are currently missing some important tests for such scenarios. Cover
that gap.
== Series Details ==
Series: Waitboost drm syncobj waits (rev2)
URL : https://patchwork.freedesktop.org/series/113846/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12727 -> Patchwork_113846v2
Summary
---
Hi Janusz,
On 2023-02-10 at 15:21:20 +0100, Janusz Krzysztofik wrote:
> On Friday, 10 February 2023 15:02:59 CET Kamil Konieczny wrote:
> > Hi Janusz,
> >
> > I have one nit, see below.
> >
> > On 2023-02-09 at 20:32:31 +0100, Janusz Krzysztofik wrote:
> > > If any of *-without-i915 subtests
Hi Tvrtko,
On 2023-02-10 at 15:22:07 +, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> No one remembered to add names for the new compute engines.
Actually there was patch:
https://patchwork.freedesktop.org/series/112674/
intel_gpu_top: Add display name for compute engine class
Submitted
From: Tvrtko Ursulin
No one remembered to add names for the new compute engines.
Signed-off-by: Tvrtko Ursulin
---
tools/intel_gpu_top.c | 4
1 file changed, 4 insertions(+)
diff --git a/tools/intel_gpu_top.c b/tools/intel_gpu_top.c
index c043c8960dd0..e13e35b71f4b 100644
---
It is becoming a strong habit to call the drm_i915_private
structures "i915", but there are still many left that are called
dev_priv.
Sometimes this makes grepping a bit challenging and anyway it
keeps a coherent style.
Rename all the "dev_priv" structures in the gt/* directory to
"i915".
On Friday, 10 February 2023 15:02:59 CET Kamil Konieczny wrote:
> Hi Janusz,
>
> I have one nit, see below.
>
> On 2023-02-09 at 20:32:31 +0100, Janusz Krzysztofik wrote:
> > If any of *-without-i915 subtests fails or skips for any reason, it may
> > leave the i915 module unloaded while keeping
Currently, for operations like memory clear or copy for big
chunks of memory, we generate multiple requests executed in a
chain.
But if one of the requests generated fails we would not know it
to unless it happens to the last request, because errors are not
properly propagated.
For this we need
Hi Janusz,
I have one nit, see below.
On 2023-02-09 at 20:32:31 +0100, Janusz Krzysztofik wrote:
> If any of *-without-i915 subtests fails or skips for any reason, it may
> leave the i915 module unloaded while keeping our device list populated
> with initially collected data. In a follow up
== Series Details ==
Series: drm/i915/display: Pass drm_i915_private as param to i915 funcs (rev4)
URL : https://patchwork.freedesktop.org/series/113083/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/113083/revisions/4/mbox/ not
applied
== Series Details ==
Series: Waitboost drm syncobj waits (rev2)
URL : https://patchwork.freedesktop.org/series/113846/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
From: Nirmoy Das
For i915 functions pass struct drm_i915_private directly instead of
struct drm_device.
v2: Use to_i915(dev) directly without alias(Andrzej).
Cc: Rodrigo Vivi
Suggested-by: Jani Nikula
Signed-off-by: Nirmoy Das
Reviewed-by: Jani Nikula
Reviewed-by: Andrzej Hajda
From: Tvrtko Ursulin
Userspace waits coming via the drm_syncobj route have so far been
bypassing the waitboost mechanism.
Use the previously added dma-fence wait tracking API and apply the
same waitboosting logic which applies to other entry points.
This should fix the perfomance regressions
From: Tvrtko Ursulin
Use the newly added dma-fence API to apply waitboost not only requests
which have been marked with I915_WAIT_PRIORITY by i915, but which may be
waited upon by others (such as for instance buffer sharing in multi-GPU
scenarios).
Signed-off-by: Tvrtko Ursulin
---
From: Tvrtko Ursulin
Use the previously added dma-fence API to mark the direct i915 waits as
explicit. This has no significant effect apart from following the new
pattern.
Signed-off-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_request.c | 3 ++-
1 file changed, 2 insertions(+), 1
From: Tvrtko Ursulin
Use the previously added dma-fence tracking of explicit waiters.
Signed-off-by: Tvrtko Ursulin
---
drivers/gpu/drm/drm_syncobj.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_syncobj.c b/drivers/gpu/drm/drm_syncobj.c
index
From: Tvrtko Ursulin
In i915 we have this concept of "wait boosting" where we give a priority boost
for instance to fences which are actively waited upon from userspace. This has
it's pros and cons and can certainly be discussed at lenght. However fact is
some workloads really like it.
Problem
From: Tvrtko Ursulin
Track how many callers are explicity waiting on a fence to signal and
allow querying that via new dma_fence_wait_count() API.
This provides infrastructure on top of which generic "waitboost" concepts
can be implemented by individual drivers. Wait-boosting is any reactive
On 2/10/2023 1:21 PM, Andi Shyti wrote:
Hi Jani,
On Thu, Jan 19, 2023 at 12:58:47PM +0200, Jani Nikula wrote:
On Thu, 19 Jan 2023, Nirmoy Das wrote:
For i915 functions pass struct drm_i915_private directly instead of
struct drm_device.
Reviewed-by: Jani Nikula
but maybe let's wait until
Hi Jani,
On Thu, Jan 19, 2023 at 12:58:47PM +0200, Jani Nikula wrote:
> On Thu, 19 Jan 2023, Nirmoy Das wrote:
> > For i915 functions pass struct drm_i915_private directly instead of
> > struct drm_device.
>
> Reviewed-by: Jani Nikula
>
> but maybe let's wait until we've synced up with
On Thu, Feb 09, 2023 at 03:22:28PM -0800, Matt Roper wrote:
> Although registers in the L3 bank/node configuration ranges are marked
> as having "DEV" reset characteristics in the bspec, this appears to be a
> hold-over from pre-Xe_HP platforms. In reality, these registers
> maintain their values
On Friday, 10 February 2023 12:21:58 CET Kamil Konieczny wrote:
> Hi,
>
> On 2023-02-10 at 08:53:12 +0100, Janusz Krzysztofik wrote:
> > Hi,
> >
> > On Thursday, 9 February 2023 12:50:38 CET Janusz Krzysztofik wrote:
> > > Users reported oopses on list corruptions when using i915 perf with a
> >
Hi,
> can any of the DRM maintainers please check and eventually ack
> this patch?
I renew my request for an ack from any of the drm maintainers.
This patch has been already reviewd.
If it's OK I can take it into the drm-intel-gt-next branch.
Thanks,
Andi
> On Tue, Jan 17, 2023 at 12:53:49PM
On Wed, 08 Feb 2023, Swati Sharma wrote:
> Hi Jani,
>
> Thanks for the reviews. Please find my replies inline.
>
> On 07-Feb-23 2:05 PM, Jani Nikula wrote:
>> On Tue, 07 Feb 2023, Suraj Kandpal wrote:
>>> From: Swati Sharma
>>>
>>> DSC_Output_Format_Sink_Support entry is added to
Hi,
On 2023-02-10 at 08:53:12 +0100, Janusz Krzysztofik wrote:
> Hi,
>
> On Thursday, 9 February 2023 12:50:38 CET Janusz Krzysztofik wrote:
> > Users reported oopses on list corruptions when using i915 perf with a
> > number of concurrently running graphics applications. That indicates we
> >
Am 08.02.23 um 15:53 schrieb Matthew Auld:
The ttm BO now initially has NULL bo->resource, and leaves the driver
the handle that. However it looks like we forgot to handle that for
ttm_bo_move_memcpy() users, like with vram-gem, since it just silently
returns zero. This seems to then trigger
On Tue, 07 Feb 2023, Greg Kroah-Hartman wrote:
> On Tue, Feb 07, 2023 at 04:33:37PM +0200, Jani Nikula wrote:
>> From: Ville Syrjälä
>>
>> CONFIG_DRM_USE_DYNAMIC_DEBUG breaks debug prints for (at least modular)
>> drm drivers. The debug prints can be reinstated by manually frobbing
>>
On Thu, 09 Feb 2023, Lyude Paul wrote:
> On Tue, 2023-02-07 at 14:59 +0200, Imre Deak wrote:
>> Hi all,
>>
>> On Mon, Feb 06, 2023 at 01:48:53PM +0200, Imre Deak wrote:
>> > Add the MST topology for a CRTC to the atomic state if the driver
>> > needs to force a modeset on the CRTC after the
On Fri, Feb 10, 2023 at 12:37:21PM +0200, Jani Nikula wrote:
> On Fri, 10 Feb 2023, Ville Syrjälä wrote:
> > On Thu, Feb 09, 2023 at 05:40:14PM +0200, Jani Nikula wrote:
> >> On Thu, 09 Feb 2023, Ville Syrjala wrote:
> >> > @@ -3229,7 +3216,7 @@ static void ilk_wm_merge(struct drm_i915_private
On Fri, 10 Feb 2023, Ville Syrjälä wrote:
> On Thu, Feb 09, 2023 at 05:40:14PM +0200, Jani Nikula wrote:
>> On Thu, 09 Feb 2023, Ville Syrjala wrote:
>> > @@ -3229,7 +3216,7 @@ static void ilk_wm_merge(struct drm_i915_private
>> > *dev_priv,
>> >merged->fbc_wm_enabled =
Hi
Am 10.02.23 um 01:08 schrieb David Airlie:
On Fri, Feb 10, 2023 at 9:47 AM Stephen Rothwell wrote:
Hi all,
The following commit is also in the drm-fixes tree as a different commit
(but the same patch):
94d8b6572a1f ("nvidiafb: detect the hardware support before removing
console.")
On Thu, 9 Feb 2023 15:10:38 +0200
Ville Syrjälä wrote:
> On Thu, Feb 09, 2023 at 01:58:55PM +0200, Pekka Paalanen wrote:
> > On Wed, 8 Feb 2023 23:10:16 +0200
> > Ville Syrjala wrote:
> >
> > > From: Ville Syrjälä
> > >
> > > Add a new immutable plane property by which a plane can
45 matches
Mail list logo
