== Series Details ==
Series: 5.3-rc3: Frozen graphics with kcompactd migrating i915 pages
URL : https://patchwork.freedesktop.org/series/64983/
State : failure
== Summary ==
Applying: 5.3-rc3: Frozen graphics with kcompactd migrating i915 pages
error: sha1 information is lacking or useless
- Chris Wilson wrote:
> Quoting Wang Xiayang (2019-08-07 15:54:37)
> > The irq_lock is acquired in multiple functions:
> >
> > 1) i915_request_cancel_breadcrumb
> > <- ... <- panfrost_gpu_irq_handler
> > 2) intel_engine_breadcrumbs_irq
> > <- ... <- cherryview_irq_handler
> > 3)
[off topic: plain text mail please]
On Fri, 9 Aug 2019 12:41:42 + Martin Wilck wrote:
>
> This happened to me today, running kernel 5.3.0-rc3-1.g571863b-default
> (5.3-rc3 with just a few patches on top), after starting a KVM virtual
> machine. The X screen was frozen. Remote login via ssh
Quoting Mika Kuoppala (2019-08-09 17:12:20)
> Chris Wilson writes:
>
> > As we are phasing out using the GEM context for internal clients that
> > need to manipulate logical context state directly, remove the
> > constructor for the GVT context. We are not using it for anything other
> > than
Chris Wilson writes:
> As we are phasing out using the GEM context for internal clients that
> need to manipulate logical context state directly, remove the
> constructor for the GVT context. We are not using it for anything other
> than default setup and allocation of an i915_ppgtt.
>
>
Move the timeline from being inside the intel_ring to intel_context
itself. This saves much pointer dancing and makes the relations of the
context to its timeline much clearer.
Signed-off-by: Chris Wilson
Reviewed-by: Matthew Auld
---
drivers/gpu/drm/i915/gem/i915_gem_context.c | 35
As we are phasing out using the GEM context for internal clients that
need to manipulate logical context state directly, remove the
constructor for the GVT context. We are not using it for anything other
than default setup and allocation of an i915_ppgtt.
Signed-off-by: Chris Wilson
---
Refactor the backends to handle the deferred context allocation in a
consistent manner, and allow calling it as an explicit first step in
pinning a context for the first time. This should make it easier for
backends to keep track of partially constructed contexts from
initialisation.
Push the ring creation flags from the outer GEM context to the inner
intel_context to avoid an unsightly back-reference from inside the
backend.
Signed-off-by: Chris Wilson
Reviewed-by: Andi Shyti
---
drivers/gpu/drm/i915/gem/i915_gem_context.c | 38 ---
Quoting Mika Kuoppala (2019-08-09 15:56:53)
> Our current avoidance of non readable mcr range was not
> inclusive enough. Extend the start and end.
>
> References: HSDES#1405586840
> Cc: Tvrtko Ursulin
> Signed-off-by: Mika Kuoppala
> ---
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 2 +-
>
== Series Details ==
Series: drm/i915: Extend non readable mcr range
URL : https://patchwork.freedesktop.org/series/64976/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13947
Summary
---
== Series Details ==
Series: series starting with drm/i915: Check for a second VCS engine more
carefully (rev2)
URL : https://patchwork.freedesktop.org/series/64948/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13946
Our current avoidance of non readable mcr range was not
inclusive enough. Extend the start and end.
References: HSDES#1405586840
Cc: Tvrtko Ursulin
Signed-off-by: Mika Kuoppala
---
drivers/gpu/drm/i915/gt/intel_workarounds.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
== Series Details ==
Series: series starting with drm/i915: Check for a second VCS engine more
carefully (rev2)
URL : https://patchwork.freedesktop.org/series/64948/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Check for a second VCS
== Series Details ==
Series: drm/i915: Free the imported shmemfs file for phys objects
URL : https://patchwork.freedesktop.org/series/64963/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13945
Summary
== Series Details ==
Series: put_user_pages(): miscellaneous call sites
URL : https://patchwork.freedesktop.org/series/64952/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13944
Summary
---
Trying to hit a deadlock for invalidating dirty userptr pages (via
kcompactd).
Signed-off-by: Chris Wilson
---
tests/i915/gem_shrink.c | 36
1 file changed, 32 insertions(+), 4 deletions(-)
diff --git a/tests/i915/gem_shrink.c b/tests/i915/gem_shrink.c
== Series Details ==
Series: put_user_pages(): miscellaneous call sites
URL : https://patchwork.freedesktop.org/series/64952/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a8fd3c309ebb mm/gup: add make_dirty arg to put_user_pages_dirty_lock()
092c14de82fe drivers/gpu/drm/via:
== Series Details ==
Series: series starting with [1/4] dma-buf: add reservation_object_fences helper
URL : https://patchwork.freedesktop.org/series/64955/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13941
== Series Details ==
Series: series starting with [CI,1/2] drm/i915: Stop reconfiguring our shmemfs
mountpoint
URL : https://patchwork.freedesktop.org/series/64927/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6660_full -> Patchwork_13928_full
== Series Details ==
Series: series starting with [1/8] dma-buf: fix busy wait for new shared fences
URL : https://patchwork.freedesktop.org/series/64951/
State : failure
== Summary ==
Applying: dma-buf: fix busy wait for new shared fences
Using index info to reconstruct a base tree...
M
== Series Details ==
Series: put_user_pages(): miscellaneous call sites
URL : https://patchwork.freedesktop.org/series/64585/
State : failure
== Summary ==
Applying: mm/gup: add make_dirty arg to put_user_pages_dirty_lock()
Applying: net/rds: convert put_page() to put_user_page*()
Applying:
== Series Details ==
Series: put_user_pages(): miscellaneous call sites
URL : https://patchwork.freedesktop.org/series/64950/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13939
Summary
---
== Series Details ==
Series: dma-buf: make dma_fence structure a bit smaller (rev3)
URL : https://patchwork.freedesktop.org/series/64953/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13938
Summary
== Series Details ==
Series: series starting with [1/4] dma-buf: add reservation_object_fences helper
URL : https://patchwork.freedesktop.org/series/64955/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
6ff342a1513c dma-buf: add reservation_object_fences helper
-:25:
== Series Details ==
Series: series starting with [1/5] drm/i915: stop pruning reservation object
after wait
URL : https://patchwork.freedesktop.org/series/64949/
State : failure
== Summary ==
Applying: drm/i915: stop pruning reservation object after wait
Using index info to reconstruct a
Quoting Martin Wilck (2019-08-09 13:41:42)
> This happened to me today, running kernel 5.3.0-rc3-1.g571863b-default
> (5.3-rc3 with just a few patches on top), after starting a KVM virtual
> machine. The X screen was frozen. Remote login via ssh was still
> possible, thus I was able to retrieve
This happened to me today, running kernel 5.3.0-rc3-1.g571863b-default
(5.3-rc3 with just a few patches on top), after starting a KVM virtual
machine. The X screen was frozen. Remote login via ssh was still
possible, thus I was able to retrieve basic logs.
sysrq-w showed two blocked processes
== Series Details ==
Series: put_user_pages(): miscellaneous call sites
URL : https://patchwork.freedesktop.org/series/64950/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d134d48f6ff8 mm/gup: add make_dirty arg to put_user_pages_dirty_lock()
4ff1243be3c3 net/rds: convert
To use the legacy BSD selector, you must have a second VCS engine, or
else the ABI simply maps the request for another engine onto VCS0.
However, we only checked a single VCS1 location and overlooking the
possibility of a sparse VCS set being mapped to the dense ABI.
v2: num_vcs_engines() turns
== Series Details ==
Series: gpu/drm/i915: disable interrupt when holding spinlock
URL : https://patchwork.freedesktop.org/series/64956/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13937
Summary
---
Quoting Patchwork (2019-08-09 13:21:54)
> Possible regressions
>
> * igt@gem_ctx_create@basic-files:
> - fi-kbl-r: [PASS][1] -> [FAIL][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6667/fi-kbl-r/igt@gem_ctx_cre...@basic-files.html
>[2]:
>
== Series Details ==
Series: series starting with [CI,1/3] drm/i915: Check for a second VCS engine
more carefully
URL : https://patchwork.freedesktop.org/series/64948/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13936
John Hubbard writes:
> On 8/7/19 10:42 PM, Michael Ellerman wrote:
>> Hi John,
>>
>> john.hubb...@gmail.com writes:
>>> diff --git a/arch/powerpc/mm/book3s64/iommu_api.c
>>> b/arch/powerpc/mm/book3s64/iommu_api.c
>>> index b056cae3388b..e126193ba295 100644
>>> ---
== Series Details ==
Series: dma-buf: make dma_fence structure a bit smaller (rev3)
URL : https://patchwork.freedesktop.org/series/64953/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5dc1dc420f4d dma-buf: make dma_fence structure a bit smaller v2
-:40:
On 8/7/19 3:33 AM, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide conversion, as described in
== Series Details ==
Series: series starting with [CI,1/3] drm/i915: Check for a second VCS engine
more carefully
URL : https://patchwork.freedesktop.org/series/64948/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Check for a second VCS
== Series Details ==
Series: drm/i915: Check for a second VCS engine more carefully (rev2)
URL : https://patchwork.freedesktop.org/series/64938/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6667 -> Patchwork_13935
Summary
On 09/08/2019 12:07, Chris Wilson wrote:
Matthew spotted that we lost the fput() for phys objects now that we are
not relying on the core to cleanup the GEM object. (For the record, phys
objects import the shmemfs from their original set of pages and keep it
to provide swap space, but we never
Matthew spotted that we lost the fput() for phys objects now that we are
not relying on the core to cleanup the GEM object. (For the record, phys
objects import the shmemfs from their original set of pages and keep it
to provide swap space, but we never transform back into a shmem object.)
== Series Details ==
Series: drm/i915: Generalise BSD default selection
URL : https://patchwork.freedesktop.org/series/64947/
State : failure
== Summary ==
Applying: drm/i915: Generalise BSD default selection
Using index info to reconstruct a base tree...
M
== Series Details ==
Series: drm/i915: Stop reconfiguring our shmemfs mountpoint
URL : https://patchwork.freedesktop.org/series/64922/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6658_full -> Patchwork_13926_full
Summary
== Series Details ==
Series: drm/i915: Replace global bsd_dispatch_index with random seed (rev2)
URL : https://patchwork.freedesktop.org/series/64891/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6665 -> Patchwork_13933
On Thu, 08 Aug 2019, Chris Wilson wrote:
> Quoting Jani Nikula (2019-08-08 14:42:39)
>> The daily dose of header cleanup. I think I'll settle down for a while after
>> this one. ;)
>>
>> BR,
>> Jani.
>>
>> Jani Nikula (10):
>> drm/i915: remove unused dev_priv->no_aux_handshake
>> drm/i915:
On Mon, 01 Jul 2019, Animesh Manna wrote:
> Display State Buffer (DSB) is hardware capability which allows
> driver to batch submit HW programming.
>
> As part of initial enablement common api created which currently used
> to program gamma lut proramming.
>
> Going forwad DSB support can be
== Series Details ==
Series: drm/i915/selftests: Fixup a missing legacy_idx
URL : https://patchwork.freedesktop.org/series/64921/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6658_full -> Patchwork_13925_full
Summary
Quoting Wang Xiayang (2019-08-07 15:54:37)
> The irq_lock is acquired in multiple functions:
>
> 1) i915_request_cancel_breadcrumb
> <- ... <- panfrost_gpu_irq_handler
> 2) intel_engine_breadcrumbs_irq
> <- ... <- cherryview_irq_handler
> 3) i915_request_enable_breadcrumb
> 4)
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
Add some helpers to correctly allocate/free reservation_object_lists.
Otherwise we might forget to drop dma_fence references on list destruction.
Signed-off-by: Christian König
---
drivers/dma-buf/reservation.c | 65 +--
1 file changed, 46 insertions(+), 19
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
On 8/7/19 3:33 AM, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide conversion, as described in
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
On 8/6/19 6:32 PM, john.hubb...@gmail.com wrote:
> From: John Hubbard
> ...
>
> John Hubbard (38):
> mm/gup: add make_dirty arg to put_user_pages_dirty_lock()
...
> 54 files changed, 191 insertions(+), 323 deletions(-)
>
ahem, yes, apparently this is what happens if I add a few patches while
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
Instead of open coding the sequence loop use the new helper.
Signed-off-by: Christian König
---
drivers/gpu/drm/i915/gem/i915_gem_busy.c | 24 +++-
1 file changed, 7 insertions(+), 17 deletions(-)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_busy.c
On 8/8/19 9:25 AM, Weiny, Ira wrote:
>>
>> On 8/7/19 7:36 PM, Ira Weiny wrote:
>>> On Wed, Aug 07, 2019 at 10:46:49AM +0200, Michal Hocko wrote:
On Wed 07-08-19 10:37:26, Jan Kara wrote:
> On Fri 02-08-19 12:14:09, John Hubbard wrote:
>> On 8/2/19 7:52 AM, Jan Kara wrote:
>>> On
The only remaining use for this is to protect against setting a new exclusive
fence while we grab both exclusive and shared. That can also be archived by
looking if the exclusive fence has changed or not after completing the
operation.
v2: switch setting excl fence to rcu_assign_pointer
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
Am 06.08.19 um 21:24 schrieb Chris Wilson:
Quoting Christian König (2019-08-06 16:01:33)
Add a new helper to get a consistent set of pointers from the reservation
object. While at it group all access helpers together in the header file.
Ah, needs to be earlier :)
Ah, crap. That got
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
On 8/7/19 3:33 AM, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide conversion, as described in
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
On 8/2/19 11:48 AM, John Hubbard wrote:
> On 8/2/19 2:19 AM, Joonas Lahtinen wrote:
>> Quoting john.hubb...@gmail.com (2019-08-02 05:19:37)
>>> From: John Hubbard
...
> In order to deal with the merge problem, I'll drop this patch from my series,
> and I'd recommend that the drm-intel-next take
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
The only remaining use for this is to protect against setting a new exclusive
fence while we grab both exclusive and shared. That can also be archived by
looking if the exclusive fence has changed or not after completing the
operation.
Signed-off-by: Christian König
---
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
On Thu, 2019-08-01 at 19:19 -0700, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide conversion, as
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
On 8/2/19 2:19 AM, Joonas Lahtinen wrote:
Quoting john.hubb...@gmail.com (2019-08-02 05:19:37)
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
On 8/7/19 10:42 PM, Michael Ellerman wrote:
> Hi John,
>
> john.hubb...@gmail.com writes:
>> diff --git a/arch/powerpc/mm/book3s64/iommu_api.c
>> b/arch/powerpc/mm/book3s64/iommu_api.c
>> index b056cae3388b..e126193ba295 100644
>> --- a/arch/powerpc/mm/book3s64/iommu_api.c
>> +++
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
When reservation_object_add_shared_fence is replacing an old fence with a new
one we should not drop the old one before the new one is in place.
Otherwise other cores can busy wait for the new one to appear.
Signed-off-by: Christian König
---
drivers/dma-buf/reservation.c | 14 +++---
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
Hi!
Dne petek, 26. julij 2019 ob 19:23:14 CEST je Andrzej Pietrasiewicz
napisal(a):
> Use the ddc pointer provided by the generic connector.
>
> Signed-off-by: Andrzej Pietrasiewicz
Acked-by: Jernej Skrabec
Thanks!
Best regards,
Jernej
> ---
> drivers/gpu/drm/bridge/synopsys/dw-hdmi.c |
From: Ira Weiny
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
The reservation object should be capable of handling its internal memory
management itself. And since we search for a free slot to add the fence
from the beginning this is actually a waste of time and only minimal helpful.
Drop it to allow removal of the seqno handling in the reservation object.
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder versions").
Cc:
Am 05.08.19 um 18:54 schrieb Chris Wilson:
Quoting Chris Wilson (2019-08-05 16:58:56)
Quoting Christian König (2019-08-05 16:45:50)
The reservation object should be capable of handling its internal memory
management itself. And since we search for a free slot to add the fence
from the
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
Provide a more capable variation of put_user_pages_dirty_lock(),
and delete put_user_pages_dirty(). This is based on the
following:
1. Lots of call sites become simpler if a bool is passed
into put_user_page*(), instead of making the call site
choose which put_user_page*()
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder
On Fri, Aug 2, 2019 at 4:20 AM wrote:
>
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide conversion, as described in commit
Add a new helper to get a consistent set of pointers from the reservation
object. While at it group all access helpers together in the header file.
Signed-off-by: Christian König
---
drivers/dma-buf/dma-buf.c | 27 ++--
drivers/dma-buf/reservation.c | 60 ++
101 - 200 of 343 matches
Mail list logo
