Quoting Patchwork (2018-05-04 01:31:49)
> == Series Details ==
>
> Series: drm/i915/execlists: Drop preemption arbitrations points along the ring
> URL : https://patchwork.freedesktop.org/series/42660/
> State : success
>
> == Summary ==
>
> = CI Bug Log - changes from CI_DRM_4135_full -> Patc
== Series Details ==
Series: drm/i915/gtt: Tidy up duplicate branches in gen8_gmch_probe() (rev2)
URL : https://patchwork.freedesktop.org/series/42662/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4135_full -> Patchwork_8904_full =
== Summary - WARNING ==
Minor unknown
On 4 May 2018 at 10:29, Dave Airlie wrote:
> On 4 May 2018 at 10:19, Dave Airlie wrote:
>> On 2 May 2018 at 17:03, Jani Nikula wrote:
>>>
>>> Hi Dave -
>>>
>>> drm-intel-next-2018-04-13:
>>> First drm/i915 feature batch heading for v4.18:
>>>
>>> - drm-next backmerge to fix build (Rodrigo)
>>> -
== Series Details ==
Series: drm/i915/execlists: Drop preemption arbitrations points along the ring
URL : https://patchwork.freedesktop.org/series/42660/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4135_full -> Patchwork_8903_full =
== Summary - WARNING ==
Minor unknow
On 4 May 2018 at 10:19, Dave Airlie wrote:
> On 2 May 2018 at 17:03, Jani Nikula wrote:
>>
>> Hi Dave -
>>
>> drm-intel-next-2018-04-13:
>> First drm/i915 feature batch heading for v4.18:
>>
>> - drm-next backmerge to fix build (Rodrigo)
>> - GPU documentation improvements (Kevin)
>> - GuC and Hu
On 2 May 2018 at 17:03, Jani Nikula wrote:
>
> Hi Dave -
>
> drm-intel-next-2018-04-13:
> First drm/i915 feature batch heading for v4.18:
>
> - drm-next backmerge to fix build (Rodrigo)
> - GPU documentation improvements (Kevin)
> - GuC and HuC refactoring, host/GuC communication, logging, fixes,
== Series Details ==
Series: series starting with [CI,1/2] drm/i915: Lazily unbind vma on close
URL : https://patchwork.freedesktop.org/series/42659/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4135_full -> Patchwork_8902_full =
== Summary - FAILURE ==
Serious unknown
== Series Details ==
Series: i915: Convert to use match_string() helper
URL : https://patchwork.freedesktop.org/series/42654/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4134_full -> Patchwork_8901_full =
== Summary - WARNING ==
Minor unknown changes coming with Patchw
== Series Details ==
Series: drm/i915/dp: silence a static checker warning
URL : https://patchwork.freedesktop.org/series/42630/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4134_full -> Patchwork_8900_full =
== Summary - FAILURE ==
Serious unknown changes coming with P
== Series Details ==
Series: drm/i915/gtt: Tidy up duplicate branches in gen8_gmch_probe() (rev2)
URL : https://patchwork.freedesktop.org/series/42662/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4135 -> Patchwork_8904 =
== Summary - SUCCESS ==
No regressions found.
== Series Details ==
Series: drm/i915/gtt: Tidy up duplicate branches in gen8_gmch_probe() (rev2)
URL : https://patchwork.freedesktop.org/series/42662/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
37171cccb14b drm/i915/gtt: Tidy up duplicate branches in gen8_gmch_probe()
-:14:
== Series Details ==
Series: drm/i915/selftests: fix spelling mistake: "parmaters" -> "parameters"
URL : https://patchwork.freedesktop.org/series/42647/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4134_full -> Patchwork_8899_full =
== Summary - SUCCESS ==
No regression
Following commit f773568b6ff8 ("drm/i915: nuke the duplicated stolen
discovery"), the if-else-chain for determining the GTT size is redundant
with the !chv branches all being the same.
Reported-by: Ville Syrjälä
References: f773568b6ff8 ("drm/i915: nuke the duplicated stolen discovery")
Signed-of
Following commit f773568b6ff8 ("drm/i915: nuke the duplicated stolen
discovery"), the if-else-chain for determining the GTT size is redundant
with the !chv branches all being the same.
Reported-by: Ville Syrjälä
References: f773568b6ff8 ("drm/i915: nuke the duplicated stolen discovery")
Signed-of
== Series Details ==
Series: dma-fence cleanup v2
URL : https://patchwork.freedesktop.org/series/42640/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4134_full -> Patchwork_8898_full =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_8898_full need to
== Series Details ==
Series: drm/i915/execlists: Drop preemption arbitrations points along the ring
URL : https://patchwork.freedesktop.org/series/42660/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4135 -> Patchwork_8903 =
== Summary - SUCCESS ==
No regressions found.
== Series Details ==
Series: series starting with [CI,1/2] drm/i915: Lazily unbind vma on close
URL : https://patchwork.freedesktop.org/series/42659/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4135 -> Patchwork_8902 =
== Summary - SUCCESS ==
No regressions found.
E
Quoting Lionel Landwerlin (2018-05-03 21:09:01)
> On 03/05/18 19:00, Tvrtko Ursulin wrote:
> >> One other thing I've been wondering is whether we should strictly
> >> validate the input from userspace.
> >> Right now we min/max the numbers and never raise any error.
> >
> > It does feel low level
On 03/05/18 20:54, Chris Wilson wrote:
Limit the arbitration (where preemption may occur) to inside the batch,
and prevent it from happening on the pipecontrols/flushes we use to
write the breadcrumb seqno. Once the user batch is complete, we have
nothing left to do but serialise and emit the bre
On 03/05/18 19:00, Tvrtko Ursulin wrote:
On 03/05/2018 18:31, Lionel Landwerlin wrote:
On 03/05/18 18:12, Tvrtko Ursulin wrote:
On 30/04/2018 15:37, Lionel Landwerlin wrote:
On 25/04/18 12:50, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-04-25 12:45:14)
This function will be used la
== Series Details ==
Series: series starting with [CI,1/2] drm/i915: Lazily unbind vma on close
URL : https://patchwork.freedesktop.org/series/42659/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Commit: drm/i915: Lazily unbind vma on close
-drivers/gpu/drm/i915/selftests/../i915_d
On 5/3/2018 12:54 PM, Chris Wilson wrote:
Limit the arbitration (where preemption may occur) to inside the batch,
and prevent it from happening on the pipecontrols/flushes we use to
write the breadcrumb seqno. Once the user batch is complete, we have
nothing left to do but serialise and emit the
Limit the arbitration (where preemption may occur) to inside the batch,
and prevent it from happening on the pipecontrols/flushes we use to
write the breadcrumb seqno. Once the user batch is complete, we have
nothing left to do but serialise and emit the breadcrumb; switching
contexts at this point
Don't pre-emptively retire the oldest request in our ring's list if it
is the only request. We keep various bits of state alive using the
active reference from the request and would rather transfer that state
over to a new request rather than the more involved process of retiring
and reacquiring it
When userspace is passing around swapbuffers using DRI, we frequently
have to open and close the same object in the foreign address space.
This shows itself as the same object being rebound at roughly 30fps
(with a second object also being rebound at 30fps), which involves us
having to rewrite the
Quoting Tvrtko Ursulin (2018-05-03 18:49:27)
>
> On 03/05/2018 07:36, Chris Wilson wrote:
> > As we reschedule the requests, we do not want the submission tasklet
> > running until we finish updating the priority chains. (We start
> > rewriting priorities from the oldest, but the dequeue looks at
== Series Details ==
Series: i915: Convert to use match_string() helper
URL : https://patchwork.freedesktop.org/series/42654/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4134 -> Patchwork_8901 =
== Summary - SUCCESS ==
No regressions found.
External URL:
https://pa
The new helper returns index of the matching string in an array.
We are going to use it here.
Signed-off-by: Andy Shevchenko
---
drivers/gpu/drm/i915/intel_pipe_crc.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_pipe_crc.
On 03/05/2018 18:31, Lionel Landwerlin wrote:
On 03/05/18 18:12, Tvrtko Ursulin wrote:
On 30/04/2018 15:37, Lionel Landwerlin wrote:
On 25/04/18 12:50, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-04-25 12:45:14)
This function will be used later by the per (context,engine) power
prog
On 03/05/2018 07:36, Chris Wilson wrote:
As we reschedule the requests, we do not want the submission tasklet
running until we finish updating the priority chains. (We start
rewriting priorities from the oldest, but the dequeue looks at the most
recent in-flight, so there is a small race conditi
On 03/05/18 18:12, Tvrtko Ursulin wrote:
On 30/04/2018 15:37, Lionel Landwerlin wrote:
On 25/04/18 12:50, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-04-25 12:45:14)
This function will be used later by the per (context,engine) power
programming interface.
No. This is not the appropri
== Series Details ==
Series: drm/i915/dp: silence a static checker warning
URL : https://patchwork.freedesktop.org/series/42630/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4134 -> Patchwork_8900 =
== Summary - SUCCESS ==
No regressions found.
External URL:
https:/
On 25/04/2018 12:45, Lionel Landwerlin wrote:
From: Chris Wilson
We want to allow userspace to reconfigure the subslice configuration for
its own use case. To do so, we expose a context parameter to allow
adjustment of the RPCS register stored within the context image (and
currently not access
== Series Details ==
Series: drm/i915/psr: vbt change for psr (rev6)
URL : https://patchwork.freedesktop.org/series/41289/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4131_full -> Patchwork_8897_full =
== Summary - SUCCESS ==
No regressions found.
External URL:
htt
On Thu, May 03, 2018 at 09:58:56AM -0700, Rodrigo Vivi wrote:
> On Wed, May 02, 2018 at 03:31:15PM -0700, Tarun Vyas wrote:
> > On Wed, May 02, 2018 at 01:04:06PM -0700, Vivi, Rodrigo wrote:
> > > On Wed, May 02, 2018 at 09:51:43PM +0300, Ville Syrjälä wrote:
> > > > On Wed, May 02, 2018 at 11:19:1
Rodrigo,
The changes are already in place on kabylake 209+ onwards, So limiting
this change to only kabylake and confirmed vbt version for now.
RCR is already raised for GOP team to resolve. Once we get the other
platform confirmation, we can add those platforms too.
Here is
On 30/04/2018 15:37, Lionel Landwerlin wrote:
On 25/04/18 12:50, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-04-25 12:45:14)
This function will be used later by the per (context,engine) power
programming interface.
No. This is not the appropriate uABI, please see
intel_engine_lookup_u
On 03/05/2018 07:36, Chris Wilson wrote:
Don't pre-emptively retire the oldest request in our ring's list if it
is the only request. We keep various bits of state alive using the
active reference from the request and would rather transfer that state
over to a new request rather than the more inv
On 03/05/2018 07:36, Chris Wilson wrote:
When userspace is passing around swapbuffers using DRI, we frequently
have to open and close the same object in the foreign address space.
This shows itself as the same object being rebound at roughly 30fps
(with a second object also being rebound at 30fp
On Wed, May 02, 2018 at 03:31:15PM -0700, Tarun Vyas wrote:
> On Wed, May 02, 2018 at 01:04:06PM -0700, Vivi, Rodrigo wrote:
> > On Wed, May 02, 2018 at 09:51:43PM +0300, Ville Syrjälä wrote:
> > > On Wed, May 02, 2018 at 11:19:14AM -0700, Tarun Vyas wrote:
> > > > On Mon, Apr 30, 2018 at 10:19:33A
== Series Details ==
Series: drm: Fix rounding errors and use scaling in i915, v2.
URL : https://patchwork.freedesktop.org/series/42631/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4131_full -> Patchwork_8896_full =
== Summary - FAILURE ==
Serious unknown changes comin
Quoting Leon Romanovsky (2018-05-03 16:36:55)
> From: Leon Romanovsky
>
> The macro u64_to_ptr() and function ptr_to_u64() are useful enough
> to be part of general header, so move them there and allow RDMA
> subsystem reuse them.
>
> Signed-off-by: Leon Romanovsky
Feel free to merge this thro
On Thu, May 03, 2018 at 01:53:22PM +0300, Dan Carpenter wrote:
> Smatch warns that "n_entries" isn't always set. It would trigger a
> some WARN_ON()s on that path so presumably it can't happen but it's
> simple enough to initialize it to zero just to silence the warning.
I usually would just ask
On 03/05/2018 07:36, Chris Wilson wrote:
Limit the arbitration (where preemption may occur) to inside the batch,
and prevent it from happening on the pipecontrols/flushes we use to
write the breadcrumb seqno. Once the user batch is complete, we have
nothing left to do but serialise and emit the
On 03/05/2018 15:06, Chris Wilson wrote:
Quoting Joonas Lahtinen (2018-05-03 14:59:35)
Quoting Chris Wilson (2018-05-02 20:21:42)
I caught the compiler emitting the if(!NULL) guard at the start of
dma_fence_put(); on the request it should know for certain is already
non-NULL. Mark up the funct
On 03/05/2018 17:04, Joonas Lahtinen wrote:
Quoting Lionel Landwerlin (2018-04-26 13:22:30)
On 26/04/18 11:00, Joonas Lahtinen wrote:
Quoting Lionel Landwerlin (2018-04-25 14:45:21)
From: Chris Wilson
We want to allow userspace to reconfigure the subslice configuration for
its own use case.
Quoting Chris Wilson (2018-05-03 18:35:48)
> Quoting Paulo Zanoni (2018-05-03 16:24:47)
> > Em Qui, 2018-05-03 às 12:59 +0300, Joonas Lahtinen escreveu:
> > > Please split the patch here and add a respective Fixes: tag to when
> > > base Icelake support was introduced. Lacking this portion when
> >
On 03/05/18 17:04, Joonas Lahtinen wrote:
Quoting Lionel Landwerlin (2018-04-26 13:22:30)
On 26/04/18 11:00, Joonas Lahtinen wrote:
Quoting Lionel Landwerlin (2018-04-25 14:45:21)
From: Chris Wilson
We want to allow userspace to reconfigure the subslice configuration for
its own use case. To
== Series Details ==
Series: drm/i915/selftests: fix spelling mistake: "parmaters" -> "parameters"
URL : https://patchwork.freedesktop.org/series/42647/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4134 -> Patchwork_8899 =
== Summary - WARNING ==
Minor unknown changes c
Quoting Joonas Lahtinen (2018-05-03 17:04:31)
> More advanced tactics would include scheduling work so that we try to
> avoid the slice count changes and deduct the switching time from the
> execution budget of the app requesting less slices (if we had fair
> time slicing).
Have you been peeking a
== Series Details ==
Series: drm/i915/dp: silence a static checker warning
URL : https://patchwork.freedesktop.org/series/42630/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4131_full -> Patchwork_8894_full =
== Summary - FAILURE ==
Serious unknown changes coming with P
Quoting Lionel Landwerlin (2018-04-26 13:22:30)
> On 26/04/18 11:00, Joonas Lahtinen wrote:
> > Quoting Lionel Landwerlin (2018-04-25 14:45:21)
> >> From: Chris Wilson
> >>
> >> We want to allow userspace to reconfigure the subslice configuration for
> >> its own use case. To do so, we expose a co
== Series Details ==
Series: dma-fence cleanup v2
URL : https://patchwork.freedesktop.org/series/42640/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4134 -> Patchwork_8898 =
== Summary - SUCCESS ==
No regressions found.
External URL:
https://patchwork.freedesktop.or
Quoting Daniel Vetter (2018-05-03 15:25:50)
> @@ -560,7 +567,7 @@ dma_fence_init(struct dma_fence *fence, const struct
> dma_fence_ops *ops,
>spinlock_t *lock, u64 context, unsigned seqno)
> {
> BUG_ON(!lock);
> - BUG_ON(!ops || !ops->wait || !ops->enable_signaling |
== Series Details ==
Series: dma-fence cleanup v2
URL : https://patchwork.freedesktop.org/series/42640/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
0506ef5446b8 dma-fence: remove fill_driver_data callback
79de0bebf6c8 dma-fence: Make ->enable_signaling optional
-:43: WARNING:
Quoting Colin King (2018-05-03 16:45:10)
> From: Colin Ian King
>
> Trivial fix to spelling mistake in pr_err error message
>
> Signed-off-by: Colin Ian King
Reviewed-by: Chris Wilson
-Chris
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
From: Colin Ian King
Trivial fix to spelling mistake in pr_err error message
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/i915/selftests/i915_vma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/selftests/i915_vma.c
b/drivers/gpu/drm/i915/selftes
On Thu, May 03, 2018 at 05:06:09PM +0530, vathsala nagaraju wrote:
> From: Vathsala Nagaraju
>
> For psr block #9, the vbt description has moved to options [0-3] for
> TP1,TP2,TP3 Wakeup time from decimal value without any change to vbt
> structure. Since spec does not mention from which VBT ver
Quoting Paulo Zanoni (2018-05-03 16:24:47)
> Em Qui, 2018-05-03 às 12:59 +0300, Joonas Lahtinen escreveu:
> > Please split the patch here and add a respective Fixes: tag to when
> > base Icelake support was introduced. Lacking this portion when
> > running ICL will
> > cause random memory corruptio
Em Qui, 2018-05-03 às 12:59 +0300, Joonas Lahtinen escreveu:
> Quoting Paulo Zanoni (2018-05-03 03:23:52)
> > ICL changes the registers and addresses to 64 bits.
> >
> > I also briefly looked at implementing an u64 version of the PCI
> > config
> > read functions, but I concluded this wouldn't be
On Thu, May 03, 2018 at 09:50:09AM +0300, Jani Nikula wrote:
> On Wed, 02 May 2018, Chris Wilson wrote:
> > Quoting Ville Syrjälä (2018-05-02 17:14:21)
> >> On Wed, May 02, 2018 at 04:57:09PM +0100, Chris Wilson wrote:
> >> > Quoting Ville Syrjälä (2018-05-02 16:52:41)
> >> > > On Wed, May 02, 201
On Wed, May 02, 2018 at 04:33:00PM -0700, Tarun Vyas wrote:
> From: Tarun
>
> No functional changes, just a minor knit. Stumbled across the kernel doc for
> schedule_timeout() which quotes "In all cases the return value is guaranteed
> to be non-negative". Also, the return code of schedule_timeou
On Thu, May 03, 2018 at 01:41:52PM +0300, Ville Syrjälä wrote:
> On Thu, May 03, 2018 at 08:35:30AM +0200, Daniel Vetter wrote:
> > On Wed, May 02, 2018 at 09:32:47PM +0300, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > Clear the old_state and new_state pointers for every object in
>
- Intro section that links to how this is exposed to userspace.
- Lots more hyperlinks.
- Minor clarifications and style polish
Signed-off-by: Daniel Vetter
Cc: Sumit Semwal
Cc: Gustavo Padovan
Cc: linux-me...@vger.kernel.org
Cc: linaro-mm-...@lists.linaro.org
---
Documentation/driver-api/dma-
dma_fence_default_wait is the default now, same for the trivial
enable_signaling implementation.
Also remove the ->signaled callback, vgem can't peek ahead with a
fastpath, returning false is the default implementation.
Signed-off-by: Daniel Vetter
Cc: Kees Cook
Cc: Cihangir Akturk
Cc: Sean Pa
dma_fence_default_wait is the default now, same for the trivial
enable_signaling implementation.
Reviewed-by: Eric Anholt
Signed-off-by: Daniel Vetter
Cc: David Airlie
Cc: Gerd Hoffmann
Cc: virtualizat...@lists.linux-foundation.org
---
drivers/gpu/drm/virtio/virtgpu_fence.c | 7 ---
1 fil
dma_fence_default_wait is the default now, same for the trivial
enable_signaling implementation.
Signed-off-by: Daniel Vetter
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Cc: Chris Wilson
Cc: Tvrtko Ursulin
Cc: Colin Ian King
Cc: Daniel Vetter
Cc: Mika Kuoppala
Cc: intel-gfx@lists
dma_fence_default_wait is the default now, same for the trivial
enable_signaling implementation.
Reviewed-by: Eric Anholt
Signed-off-by: Daniel Vetter
Cc: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_fence.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/gpu/drm/vc4/vc4_fence.c b
dma_fence_default_wait is the default now.
Signed-off-by: Daniel Vetter
Cc: Ben Skeggs
Cc: nouv...@lists.freedesktop.org
---
drivers/gpu/drm/nouveau/nouveau_fence.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c
b/drivers/gpu/drm/nouveau/nouveau_fenc
The trivial enable_signaling implementation matches the default code.
v2: Fix up commit message to match patch better (Eric).
Cc: Eric Anholt
Reviewed-by: Eric Anholt
Signed-off-by: Daniel Vetter
Cc: Dave Airlie
Cc: Gerd Hoffmann
Cc: virtualizat...@lists.linux-foundation.org
---
drivers/gpu
dma_fence_default_wait is the default now, same for the trivial
enable_signaling implementation.
Signed-off-by: Daniel Vetter
Cc: Rob Clark
Cc: linux-arm-...@vger.kernel.org
Cc: freedr...@lists.freedesktop.org
---
drivers/gpu/drm/msm/msm_fence.c | 7 ---
1 file changed, 7 deletions(-)
diff
Almost everyone uses dma_fence_default_wait.
v2: Also remove the BUG_ON(!ops->wait) (Chris).
Reviewed-by: Christian König (v1)
Signed-off-by: Daniel Vetter
Cc: Chris Wilson
Cc: Sumit Semwal
Cc: Gustavo Padovan
Cc: linux-me...@vger.kernel.org
Cc: linaro-mm-...@lists.linaro.org
---
drivers/dm
dma_fence_default_wait is the default now, same for the trivial
enable_signaling implementation.
Reviewed-by: Eric Anholt
Signed-off-by: Daniel Vetter
Cc: Gustavo Padovan
Cc: Maarten Lankhorst
Cc: Sean Paul
Cc: David Airlie
---
drivers/gpu/drm/drm_crtc.c | 7 ---
drivers/g
dma_fence_default_wait is the default now.
Reviewed-by: Christian König
Signed-off-by: Daniel Vetter
Cc: Alex Deucher
Cc: "Christian König"
Cc: Monk Liu
Cc: pding
Cc: Andrey Grodzovsky
Cc: Evan Quan
Cc: Daniel Vetter
Cc: Kees Cook
---
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c | 2
Hi all,
Resending the entire pile because I shrugged of some CI noise which wasn't
noise. Silly me :-/
Besides the BUG_ON that also Chris spotted just minor changes, which I did
send out individually already.
As always, feedback very much welcome.
Thanks, Daniel
Daniel Vetter (15):
dma-fence
Many drivers have a trivial implementation for ->enable_signaling.
Let's make it optional by assuming that signalling is already
available when the callback isn't present.
Reviewed-by: Christian König
Signed-off-by: Daniel Vetter
Cc: Sumit Semwal
Cc: Gustavo Padovan
Cc: linux-me...@vger.kernel
dma_fence_default_wait is the default now, same for the trivial
enable_signaling implementation.
Acked-by: Lucas Stach
Signed-off-by: Daniel Vetter
Cc: Lucas Stach
Cc: Russell King
Cc: Christian Gmeiner
Cc: etna...@lists.freedesktop.org
---
drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 7 ---
Noticed while I was typing docs. Entirely unused.
v2: Remove reference in @timeline_value_str too. While at it clarify
why timeline_value_str has a fence parameter - we don't have an
explicit timeline structure unfortunately.
Cc: Eric Anholt
Reviewed-by: Eric Anholt
Reviewed-by: Christian König
When this was introduced in
commit a519435a96597d8cd96123246fea4ae5a6c90b02
Author: Christian König
Date: Tue Oct 20 16:34:16 2015 +0200
dma-buf/fence: add fence_wait_any_timeout function v2
there was a restriction added that this only works if the dma-fence
uses the dma_fence_default_wai
Quoting Joonas Lahtinen (2018-05-03 15:05:38)
> Quoting Chris Wilson (2018-05-02 14:13:26)
> > When waiting for a finite batch, all that we require is that the batch
> > completes. If it takes the full second (or longer) for us to wake up and
> > notice the completed batch is immaterial, so only as
Quoting Joonas Lahtinen (2018-05-03 14:59:35)
> Quoting Chris Wilson (2018-05-02 20:21:42)
> > I caught the compiler emitting the if(!NULL) guard at the start of
> > dma_fence_put(); on the request it should know for certain is already
> > non-NULL. Mark up the function as non-null and tell the com
Quoting Chris Wilson (2018-05-02 14:13:26)
> When waiting for a finite batch, all that we require is that the batch
> completes. If it takes the full second (or longer) for us to wake up and
> notice the completed batch is immaterial, so only assert that we don't
> report an infinite timeout afterw
Quoting Chris Wilson (2018-05-02 20:21:42)
> I caught the compiler emitting the if(!NULL) guard at the start of
> dma_fence_put(); on the request it should know for certain is already
> non-NULL. Mark up the function as non-null and tell the compiler that
> the request pointer doesn't change:
>
>
Am Freitag, den 27.04.2018, 08:17 +0200 schrieb Daniel Vetter:
> dma_fence_default_wait is the default now, same for the trivial
> enable_signaling implementation.
>
> > Signed-off-by: Daniel Vetter
> > Cc: Lucas Stach
> > Cc: Russell King
> > Cc: Christian Gmeiner
> Cc: etna...@lists.freedesk
On Thu, May 03, 2018 at 04:17:24PM +0300, Ville Syrjälä wrote:
> On Thu, May 03, 2018 at 06:07:45AM -0700, Rodrigo Vivi wrote:
> > On Wed, May 02, 2018 at 10:12:51PM +0300, Ville Syrjälä wrote:
> > > On Wed, May 02, 2018 at 10:52:55AM -0700, Rodrigo Vivi wrote:
> > > > On intel_dp_compute_config()
On Thu, May 03, 2018 at 01:22:16PM +0200, Maarten Lankhorst wrote:
> We want to add more DRM selftests, and there's not much point in
> having a Kconfig option for every single one of them, so make
> a generic one.
>
> Signed-off-by: Maarten Lankhorst
Seems like a reasonable idea.
Reviewed-by:
On Thu, May 03, 2018 at 01:22:17PM +0200, Maarten Lankhorst wrote:
> Signed-off-by: Maarten Lankhorst
> ---
> drivers/gpu/drm/Kconfig | 1 +
> drivers/gpu/drm/selftests/Makefile| 2 +-
> .../gpu/drm/selftests/drm_helper_selftests.h | 9 +
> drivers/gpu/drm
On Thu, May 03, 2018 at 01:22:15PM +0200, Maarten Lankhorst wrote:
> With the previous patch drm_atomic_helper_check_plane_state correctly
> calculates clipping and the xf86-video-intel ddx is fixed to fall back
> to GPU correctly when SetPlane fails, we can remove the hack where
> we try to pan/zo
On Thu, May 03, 2018 at 01:22:13PM +0200, Maarten Lankhorst wrote:
> When calculating limits we want to be as pessimistic as possible,
> so we have to explicitly say whether we want to round up or down
> to accurately calculate whether we are below min_scale or above
> max_scale.
>
> Signed-off-by
On Thu, May 03, 2018 at 01:22:14PM +0200, Maarten Lankhorst wrote:
> Instead of relying on a scale which may increase rounding errors,
> clip src by doing: src * (dst - clip) / dst and rounding the result
> away from 1, so the new coordinates get closer to 1. We won't need
> to fix up with a magic
On Thu, May 03, 2018 at 06:07:45AM -0700, Rodrigo Vivi wrote:
> On Wed, May 02, 2018 at 10:12:51PM +0300, Ville Syrjälä wrote:
> > On Wed, May 02, 2018 at 10:52:55AM -0700, Rodrigo Vivi wrote:
> > > On intel_dp_compute_config() we were calculating the needed vco
> > > for eDP on gen9 and we stashin
Quoting Chris Wilson (2018-05-03 07:36:52)
> If inside hangcheck we see that the engine has paused, but there is an
> execlists interrupt still pending, we know that the tasklet did not
> fire. Dump the GEM trace along with the current engine state, and kick
> the tasklet to recovery without having
On Wed, May 02, 2018 at 10:12:51PM +0300, Ville Syrjälä wrote:
> On Wed, May 02, 2018 at 10:52:55AM -0700, Rodrigo Vivi wrote:
> > On intel_dp_compute_config() we were calculating the needed vco
> > for eDP on gen9 and we stashing it in
> > intel_atomic_state.cdclk.logical.vco
> >
> > However few
== Series Details ==
Series: drm/i915/psr: vbt change for psr (rev6)
URL : https://patchwork.freedesktop.org/series/41289/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4131 -> Patchwork_8897 =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_8897 need
== Series Details ==
Series: drm/i915/psr: vbt change for psr (rev6)
URL : https://patchwork.freedesktop.org/series/41289/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
824c9eb50c54 drm/i915/psr: vbt change for psr
-:69: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV
== Series Details ==
Series: drm: Fix rounding errors and use scaling in i915, v2.
URL : https://patchwork.freedesktop.org/series/42631/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4131 -> Patchwork_8896 =
== Summary - SUCCESS ==
No regressions found.
External URL:
On Thu, 2018-05-03 at 10:46 +, Lisovskiy, Stanislav wrote:
> On Thu, 2018-05-03 at 13:18 +0300, Jani Nikula wrote:
> > On Wed, 02 May 2018, StanLis wrote:
> > > From: Stanislav Lisovskiy
> > >
> > >
> > > diff --git a/Documentation/gpu/kms-properties.csv
> > > b/Documentation/gpu/kms-proper
== Series Details ==
Series: drm: Fix rounding errors and use scaling in i915, v2.
URL : https://patchwork.freedesktop.org/series/42631/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Commit: drm/rect: Round above 1 << 16 upwards to correct scale calculation
functions.
Okay!
Commi
== Series Details ==
Series: drm: Fix rounding errors and use scaling in i915, v2.
URL : https://patchwork.freedesktop.org/series/42631/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9e4d573cb796 drm/rect: Round above 1 << 16 upwards to correct scale calculation
functions.
-:2
== Series Details ==
Series: drm/i915: Perform a chipset flush for GGTT writes
URL : https://patchwork.freedesktop.org/series/42627/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4131 -> Patchwork_8895 =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwo
1 - 100 of 140 matches
Mail list logo
