== Series Details ==
Series: drm/i915/ttm: Async migration
URL : https://patchwork.freedesktop.org/series/96798/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-
+drivers/gpu/drm/i915/display/inte
Update the copy function i915_gem_obj_copy_ttm() to be asynchronous for
future users and update the only current user to sync the objects
as needed after this function.
Signed-off-by: Thomas Hellström
---
drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c | 40 ++--
drivers/gpu/drm/i91
Don't wait sync while migrating, but rather make the GPU blit await the
dependencies and add a moving fence to the object.
This also enables asynchronous VRAM management in that on eviction,
rather than waiting for the moving fence to expire before freeing VRAM,
it is freed immediately and the fen
There is an interesting refcounting loop:
struct intel_memory_region has a struct ttm_resource_manager,
ttm_resource_manager->move may hold a reference to i915_request,
i915_request may hold a reference to intel_context,
intel_context may hold a reference to drm_i915_gem_object,
drm_i915_gem_object
Move the i915_gem_obj_copy_ttm() function to i915_gem_ttm_move.h.
This will help keep a number of functions static when introducing
async moves.
Signed-off-by: Thomas Hellström
---
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 47 ---
drivers/gpu/drm/i915/gem/i915_gem_ttm.h |
From: Maarten Lankhorst
For now, we will only allow async migration when TTM is used,
so the paths we care about are related to TTM.
The mmap path is handled by having the fence in ttm_bo->moving,
when pinning, the binding only becomes available after the moving
fence is signaled, and pinning a
From: Maarten Lankhorst
We want to get rid of i915_vma tracking to simplify the code and
lifetimes. Add a way to set/put the moving fence, in preparation for
removing the tracking.
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/i915/gem/i915_gem_object.c | 37 ++
driv
This patch series deals with async migration and async vram management.
It still leaves an important part out, which is async unbinding which
will reduce latency further, at least when trying to migrate already active
objects.
Patches 1/6 and 2/6 deal with accessing and waiting for the TTM moving
On Thu, Oct 28, 2021 at 08:28:09PM -0700, Matt Roper wrote:
> From: Daniele Ceraolo Spurio
>
> In coming patches we'll be doing the actual tile initialization between
> these two uncore init phases.
>
> Signed-off-by: Daniele Ceraolo Spurio
> Signed-off-by: Matt Roper
> Reviewed-by: Lucas De M
== Series Details ==
Series: Introduce new i915 macros for checking PTEs (rev4)
URL : https://patchwork.freedesktop.org/series/96679/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10864_full -> Patchwork_21557_full
Summary
== Series Details ==
Series: Introduce new i915 macros for checking PTEs (rev4)
URL : https://patchwork.freedesktop.org/series/96679/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10864 -> Patchwork_21557
Summary
---
Noted. Thanks for your consideration, Jani.
Regards
William
-Original Message-
From: Jani Nikula
Sent: Wednesday, November 10, 2021 6:45 PM
To: Tseng, William ; intel-gfx@lists.freedesktop.org
Cc: Tseng, William ; Ville Syrjala
; Kulkarni, Vandita
; Lee, Shawn C ; Chiou,
Cooper
Sub
This series is to introduce new macros generic to i915 for checking 0 and 1
bits,
instead on relying on whats defined by the mmu, since it could be different
or non-exisitent between different platforms.
v2: Corrected sender's email.
v3: Corrected spelling error.
v4: Clean up a few other macros
GEN6_PTE_VALID and GEN6_PDE_VALID both checks the 0 bit
to see weather the mapping of the corresponding graphics
memory page is valid. Instead of having two different
macros doing the same thing, this patch replaces the macros
with I915_PAGE_PRESENT.
Signed-off-by: Michael Cheng
---
drivers/gpu/
Removes BYT_PTE_WRITEABLE and replace it with
I915_PAGE_RW.
Signed-off-by: Michael Cheng
---
drivers/gpu/drm/i915/gt/intel_ggtt.c | 2 +-
drivers/gpu/drm/i915/gt/intel_gtt.h | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_ggtt.c
b/drivers/gpu/
Certain functions within i915 uses macros that are defined for
specific architectures by the mmu, such as _PAGE_RW and _PAGE_PRESENT
(Some architectures don't even have these macros defined, like ARM64).
Instead of re-using bits defined for the CPU, we should use bits
defined for i915. This patch
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle
URL : https://patchwork.freedesktop.org/series/96784/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10863_full -> Patchwork_21556_full
[Redundant sending of this email due to some mail issues]
On 2021-10-28 20:28:12, Matt Roper wrote:
> From: Tvrtko Ursulin
>
> Add some basic plumbing to support more than one dynamically allocated
> struct intel_gt. Up to four gts are supported in i915->gts[], with slot
> zero shadowing the ex
Hi,
> > +#define for_each_gt(i915__, id__, gt__) \
> > + for ((id__) = 0; \
> > +(id__) < I915_MAX_TILES; \
> > +(id__)++) \
> > + for_each_if(((gt__) = (i915__)->gts[(id__)]))
>
> In this patch set, symbol I915_MAX_TILES is introduced.
> In a later patch set of this s
Hi all,
On Fri, 5 Nov 2021 12:51:22 +1100 Stephen Rothwell
wrote:
>
> On Thu, 28 Oct 2021 18:27:53 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the char-misc tree got a conflict in:
> >
> > drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c
> >
> > between commit:
> >
> >
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle
URL : https://patchwork.freedesktop.org/series/96784/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10863 -> Patchwork_21556
Summary
-
On Wed, Nov 10, 2021 at 01:46:46PM +0200, Ville Syrjälä wrote:
> On Wed, Nov 10, 2021 at 10:59:26AM +0530, Tilak Tangudu wrote:
> > Enable runtime pm autosuspend by default for gen12 and
> > later versions.
> >
> > Signed-off-by: Tilak Tangudu
> > ---
> > drivers/gpu/drm/i915/intel_runtime_pm.c
t; > different platforms with linux-next 20211109:
> > -
> > https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_l...@reload.html
> > -
> > https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_l...@re
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle
URL : https://patchwork.freedesktop.org/series/96784/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
f81f77a16d9c ALSA: hda: fix general protection fault in azx_runtime_idle
-:31: WARNING:CO
ng drvdata to NULL at end of azx_remove().
>
> Signed-off-by: Kai Vehmanen
> ---
> sound/pci/hda/hda_intel.c | 1 +
> 1 file changed, 1 insertion(+)
>
> Some non-persistent direct links showing the bug trigger on
> different platforms with linux-next 20211109:
> -
>
.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_l...@reload.html
-
https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_l...@reload.html
Notably with 2020 linux-next, the bug does not trigger:
-
https://intel-gfx-ci.01.org/tree/linux-next/next
== Series Details ==
Series: drm/i915: Skip error capture when wedged on init (rev2)
URL : https://patchwork.freedesktop.org/series/96718/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10863_full -> Patchwork_21555_full
Sum
On 2021-11-10 09:35, Tvrtko Ursulin wrote:
On 10/11/2021 07:25, Lu Baolu wrote:
On 2021/11/10 1:35, Tvrtko Ursulin wrote:
On 09/11/2021 17:19, Lucas De Marchi wrote:
On Tue, Nov 09, 2021 at 12:17:59PM +, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
On igfx + dgfx setups, it appears that
On 2021-11-10 14:11, Tvrtko Ursulin wrote:
On 10/11/2021 12:35, Lu Baolu wrote:
On 2021/11/10 20:08, Tvrtko Ursulin wrote:
On 10/11/2021 12:04, Lu Baolu wrote:
On 2021/11/10 17:30, Tvrtko Ursulin wrote:
On 10/11/2021 07:12, Lu Baolu wrote:
Hi Tvrtko,
On 2021/11/9 20:17, Tvrtko Ursulin wr
== Series Details ==
Series: drm/i915/dsi: transmit brightness command in HS state (rev4)
URL : https://patchwork.freedesktop.org/series/96702/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10863_full -> Patchwork_21554_full
On Wed, 2021-11-10 at 16:05 +, Hogander, Jouni wrote:
> On Tue, 2021-11-09 at 18:17 +, Souza, Jose wrote:
> > On Tue, 2021-11-09 at 10:31 +, Hogander, Jouni wrote:
> > > On Mon, 2021-11-08 at 13:38 -0800, José Roberto de Souza wrote:
> > > > When a plane with a multiplanar format is add
== Series Details ==
Series: drm/i915/dsi: let HW maintain the HS-TRAIL timing
URL : https://patchwork.freedesktop.org/series/96750/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10863_full -> Patchwork_21553_full
Summary
-
On 11/10/2021 5:33 AM, Surendrakumar Upadhyay, TejaskumarX wrote:
-Original Message-
From: Ceraolo Spurio, Daniele
Sent: 10 November 2021 03:05
To: Jani Nikula ; Surendrakumar Upadhyay,
TejaskumarX
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH V2] drm/i915/gt:
On Tue, 2021-11-09 at 18:17 +, Souza, Jose wrote:
> On Tue, 2021-11-09 at 10:31 +, Hogander, Jouni wrote:
> > On Mon, 2021-11-08 at 13:38 -0800, José Roberto de Souza wrote:
> > > When a plane with a multiplanar format is added to the state by
> > > drm_atomic_add_affected_planes(), only th
== Series Details ==
Series: drm/i915: Skip error capture when wedged on init (rev2)
URL : https://patchwork.freedesktop.org/series/96718/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10863 -> Patchwork_21555
Summary
-
== Series Details ==
Series: drm/i915/dsi: transmit brightness command in HS state (rev4)
URL : https://patchwork.freedesktop.org/series/96702/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10863 -> Patchwork_21554
Summary
== Series Details ==
Series: drm/i915/dsi: let HW maintain the HS-TRAIL timing
URL : https://patchwork.freedesktop.org/series/96750/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10863 -> Patchwork_21553
Summary
---
On 10/11/2021 12:35, Lu Baolu wrote:
On 2021/11/10 20:08, Tvrtko Ursulin wrote:
On 10/11/2021 12:04, Lu Baolu wrote:
On 2021/11/10 17:30, Tvrtko Ursulin wrote:
On 10/11/2021 07:12, Lu Baolu wrote:
Hi Tvrtko,
On 2021/11/9 20:17, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
On igfx + dgfx
Quoting Christoph Hellwig (2021-11-09 09:59:57)
> On Thu, Nov 04, 2021 at 02:59:18PM +0200, Joonas Lahtinen wrote:
> > The minimal we should do is to eliminate the double underscore
> > prefixed functions. But I would prefer to have the symbol exports by
> > default so that we can enable the functi
> -Original Message-
> From: Ceraolo Spurio, Daniele
> Sent: 10 November 2021 03:05
> To: Jani Nikula ; Surendrakumar Upadhyay,
> TejaskumarX
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH V2] drm/i915/gt: Hold RPM wakelock during
> PXP suspend
>
>
>
> On 11/
On 11/10/21 13:16, Patchwork wrote:
Project List - Patchwork *Patch Details*
*Series:* drm/i915/ttm: Fix illegal addition to shrinker list
*URL:* https://patchwork.freedesktop.org/series/96748/
*State:*failure
*Details:*
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21552/in
On 2021/11/10 20:08, Tvrtko Ursulin wrote:
On 10/11/2021 12:04, Lu Baolu wrote:
On 2021/11/10 17:30, Tvrtko Ursulin wrote:
On 10/11/2021 07:12, Lu Baolu wrote:
Hi Tvrtko,
On 2021/11/9 20:17, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
On igfx + dgfx setups, it appears that intel_iommu=igfx
On 2021/11/10 17:35, Tvrtko Ursulin wrote:
On 10/11/2021 07:25, Lu Baolu wrote:
On 2021/11/10 1:35, Tvrtko Ursulin wrote:
On 09/11/2021 17:19, Lucas De Marchi wrote:
On Tue, Nov 09, 2021 at 12:17:59PM +, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
On igfx + dgfx setups, it appears that
== Series Details ==
Series: drm/i915/ttm: Fix illegal addition to shrinker list
URL : https://patchwork.freedesktop.org/series/96748/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10861_full -> Patchwork_21552_full
Summary
On 10/11/2021 12:04, Lu Baolu wrote:
On 2021/11/10 17:30, Tvrtko Ursulin wrote:
On 10/11/2021 07:12, Lu Baolu wrote:
Hi Tvrtko,
On 2021/11/9 20:17, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
On igfx + dgfx setups, it appears that intel_iommu=igfx_off option only
disables the igfx iommu. S
On 2021/11/10 17:30, Tvrtko Ursulin wrote:
On 10/11/2021 07:12, Lu Baolu wrote:
Hi Tvrtko,
On 2021/11/9 20:17, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
On igfx + dgfx setups, it appears that intel_iommu=igfx_off option only
disables the igfx iommu. Stop relying on global intel_iommu_gfx_ma
On Wed, Nov 10, 2021 at 10:49:24AM +0200, Pekka Paalanen wrote:
> On Wed, 10 Nov 2021 00:02:16 +0200
> Ville Syrjälä wrote:
>
> > On Tue, Nov 09, 2021 at 03:47:58PM -0500, Harry Wentland wrote:
> > > On 2021-11-08 04:54, Pekka Paalanen wrote:
> > > > On Thu, 4 Nov 2021 12:27:56 -0400
> > > > Ha
On Wed, Nov 10, 2021 at 10:59:26AM +0530, Tilak Tangudu wrote:
> Enable runtime pm autosuspend by default for gen12 and
> later versions.
>
> Signed-off-by: Tilak Tangudu
> ---
> drivers/gpu/drm/i915/intel_runtime_pm.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm
From: Tvrtko Ursulin
Trying to capture uninitialised engines when we wedged on init ends in
tears. Skip that together with uC capture, since failure to initialise the
latter can actually be one of the reasons for wedging on init.
v2:
* Use i915_disable_error_state when wedging on init/fini.
Si
On 10/11/2021 10:48, Matthew Auld wrote:
On Tue, 9 Nov 2021 at 12:20, Tvrtko Ursulin
wrote:
From: Tvrtko Ursulin
Trying to capture uninitialised engines when we wedged on init ends in
tears. Skip that together with uC capture, since failure to initialise the
latter can actually be one of t
On Tue, 9 Nov 2021 at 12:20, Tvrtko Ursulin
wrote:
>
> From: Tvrtko Ursulin
>
> Trying to capture uninitialised engines when we wedged on init ends in
> tears. Skip that together with uC capture, since failure to initialise the
> latter can actually be one of the reasons for wedging on init.
>
>
On Wed, 10 Nov 2021, William Tseng wrote:
> In Video Mode, if DSI transcoder is set to transmit packets
> in LP Escape mode, screen flickering would be obseved when
> brightness commands are continuously and quickly transmitted
> to a panel.
>
> The problem may be resolved by changing the mode to
On Tue, 09 Nov 2021, Jani Nikula wrote:
> On Tue, 09 Nov 2021, Vandita Kulkarni wrote:
>> This reverts commit 991d9557b0c457fb92bc49ddde24a7d9ce6144a8.
>> The Bspec was updated recently with the pll ungate sequence
>> similar to that of icl dsi enable sequence.
>> Hence reverting.
>>
>> Bspec:491
On 11/10/21 11:29, Matthew Auld wrote:
On 10/11/2021 08:55, Thomas Hellström wrote:
There's a small window of opportunity during which the adjust_lru()
function can be called with a GEM refcount of zero from the TTM
eviction code. This results in a kernel BUG().
Ensure that we don't attempt t
On 10/11/2021 08:55, Thomas Hellström wrote:
There's a small window of opportunity during which the adjust_lru()
function can be called with a GEM refcount of zero from the TTM
eviction code. This results in a kernel BUG().
Ensure that we don't attempt to modify the GEM shrinker lists unless
we
This change is to avoid over-specification of the TEOT timing
parameter, which is derived from software in current design.
Supposed that THS-TRAIL and THS-EXIT have the minimum values,
i.e., 60 and 100 in ns. If SW is overriding the HW default,
the TEOT value becomes 150 ns, approximately calculat
== Series Details ==
Series: drm/i915/ttm: Fix illegal addition to shrinker list
URL : https://patchwork.freedesktop.org/series/96748/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10861 -> Patchwork_21552
Summary
---
On 10/11/2021 07:25, Lu Baolu wrote:
On 2021/11/10 1:35, Tvrtko Ursulin wrote:
On 09/11/2021 17:19, Lucas De Marchi wrote:
On Tue, Nov 09, 2021 at 12:17:59PM +, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
On igfx + dgfx setups, it appears that intel_iommu=igfx_off option only
disables
On 10/11/2021 07:12, Lu Baolu wrote:
Hi Tvrtko,
On 2021/11/9 20:17, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
On igfx + dgfx setups, it appears that intel_iommu=igfx_off option only
disables the igfx iommu. Stop relying on global intel_iommu_gfx_mapped
and probe presence of iommu domain per
There's a small window of opportunity during which the adjust_lru()
function can be called with a GEM refcount of zero from the TTM
eviction code. This results in a kernel BUG().
Ensure that we don't attempt to modify the GEM shrinker lists unless
we have a GEM refcount.
Fixes: ebd4a8ec7799 ("drm
On Wed, 10 Nov 2021 00:02:16 +0200
Ville Syrjälä wrote:
> On Tue, Nov 09, 2021 at 03:47:58PM -0500, Harry Wentland wrote:
> > On 2021-11-08 04:54, Pekka Paalanen wrote:
> > > On Thu, 4 Nov 2021 12:27:56 -0400
> > > Harry Wentland wrote:
> > >
> > >> On 2021-11-04 04:38, Pekka Paalanen wrote
Hi Dave, Daniel,
Here's this week PR for drm-misc-next-fixes.
Maxime
drm-misc-next-fixes-2021-11-10:
Removed the TTM Huge Page functionnality to address a crash, a timeout
fix for udl, CONFIG_FB dependency improvements, a fix for a circular
locking depency in imx, a NULL pointer dereference fix
== Series Details ==
Series: drm/i915: Use per device iommu check (rev2)
URL : https://patchwork.freedesktop.org/series/96715/
State : failure
== Summary ==
Applying: drm/i915: Use per device iommu check
error: git diff header lacks filename information when removing 1 leading
pathname compon
63 matches
Mail list logo
