On 03/08/2019 2:41 am, John Hubbard wrote:
On 8/2/19 6:27 PM, Calum Mackay wrote:
On 02/08/2019 3:20 am, john.hubb...@gmail.com wrote:
...
Since it's static, and only called twice, might it be better to change its two
callers [nfs_direct_{read,write}_schedule_iovec()] to call
On Fri, Jul 26, 2019 at 07:23:01PM +0200, Andrzej Pietrasiewicz wrote:
> Use the ddc pointer provided by the generic connector.
>
> Signed-off-by: Andrzej Pietrasiewicz
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
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 31.07.19 um 11:12 schrieb Daniel Vetter:
[SNIP]
I think I brought this up before, but new top-post for a clean start.
Use-case I have in mind is something like amdkfd's model, where you have a
list of buffers (per context or whatever) that you always need to have
present. Idea is to also use
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 6:27 PM, Calum Mackay wrote:
> On 02/08/2019 3:20 am, john.hubb...@gmail.com wrote:
...
> Since it's static, and only called twice, might it be better to change its
> two callers [nfs_direct_{read,write}_schedule_iovec()] to call
> put_user_pages() directly, and remove
Am 31.07.19 um 10:05 schrieb Daniel Vetter:
[SNIP]
Okay, I see now I was far off the mark with what I thought TTM_PL_SYSTEM
was. The discussion helped clear up several bits of confusion on my part.
From proposed names, I find MAPPED and PINNED slightly confusing.
In terms of backing store
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: 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
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
Other cores don't busy wait any more and we removed the last user of checking
the seqno for changes. Drop updating the number for shared fences altogether.
Signed-off-by: Christian König
---
drivers/dma-buf/reservation.c | 6 --
1 file changed, 6 deletions(-)
diff --git
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 7:52 AM, Jan Kara wrote:
On Fri 02-08-19 07:24:43, Matthew Wilcox wrote:
On Fri, Aug 02, 2019 at 02:41:46PM +0200, Jan Kara wrote:
On Fri 02-08-19 11:12:44, Michal Hocko wrote:
On Thu 01-08-19 19:19:31, john.hubb...@gmail.com wrote:
[...]
2) Convert all of the call sites for
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 02/08/2019 3:20 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 commit
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 (08/05/19 19:12), Al Viro wrote:
[..]
> On Tue, Aug 06, 2019 at 01:03:06AM +0900, Sergey Senozhatsky wrote:
> > tmpfs does not set ->remount_fs() anymore and its users need
> > to be converted to new mount API.
>
> Could you explain why the devil do you bother with remount at all?
I would
We keep a global seed for the legacy BSD round-robin selector, but in
our testing of multiple simultaneous client workloads, a random seed
spreads the load more evenly. (As even as an initial round-robin selector
can be!) Removing the global is one less variable we have to find a home
for!
We can
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
For the default I915_EXEC_BSD round robin selector, it may select any
available VCS engine. Make it so.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
Cc: Joonas Lahtinen
Reviewed-by: Joonas Lahtinen
---
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 3 ++-
1 file changed, 2 insertions(+),
== Series Details ==
Series: drm/i915/execlists: Backtrack along timeline
URL : https://patchwork.freedesktop.org/series/64942/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6663 -> Patchwork_13932
Summary
---
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
Quoting Chris Wilson (2019-08-09 11:38:20)
> For the default I915_EXEC_BSD round robin selector, it may select any
> available VCS engine. Make it so.
>
> Signed-off-by: Chris Wilson
> Cc: Tvrtko Ursulin
> Cc: Joonas Lahtinen
We most likely want to share the code to count the vcs engines.
I
Quoting Chris Wilson (2019-08-09 08:13:54)
> 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
Hi Chris,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[cannot apply to v5.3-rc3 next-20190809]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Chris Wilson writes:
> After a preempt-to-busy, we may find an active request that is caught
> between execution states. Walk back along the timeline instead of the
> execution list to be safe.
>
> [ 106.417541] i915 :00:02.0: Resetting rcs0 for preemption time out
> [ 106.417659]
>
On Fri, Aug 09, 2019 at 06:55:53AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Fix HW readout for crtc_clock in HDMI mode (rev2)
> URL : https://patchwork.freedesktop.org/series/64909/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_6657_full
On Thu 08-08-19 16:25:04, Weiny, Ira wrote:
> > I thought I'd caught things early enough to get away with the
> > rename and deletion of that. You could either:
> >
> > a) open code an implementation of vaddr_put_pages_dirty_lock() that
> > doesn't call any of the *put_user_pages_dirty*()
For the default I915_EXEC_BSD round robin selector, it may select any
available VCS engine. Make it so.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
Cc: Joonas Lahtinen
---
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff
On Wed 07-08-19 19:36:37, Ira Weiny wrote:
> On Wed, Aug 07, 2019 at 10:46:49AM +0200, Michal Hocko wrote:
> > > So I think your debug option and my suggested renaming serve a bit
> > > different purposes (and thus both make sense). If you do the renaming, you
> > > can just grep to see
We keep a global seed for the legacy BSD round-robin selector, but in
our testing of multiple simultaneous client workloads, a random seed
spreads the load more evenly. (As even as an initial round-robin selector
can be!) Removing the global is one less variable we have to find a home
for!
We can
Quoting Joonas Lahtinen (2019-08-09 09:04:56)
> Quoting Chris Wilson (2019-08-08 12:27:48)
> > We keep a global seed for the legacy BSD round-robin selector, but in
> > our testing of multiple simultaneous client workloads, a random seed
> > spreads the load more evenly. (As even as an initial
Quoting Chris Wilson (2019-08-08 12:27:48)
> We keep a global seed for the legacy BSD round-robin selector, but in
> our testing of multiple simultaneous client workloads, a random seed
> spreads the load more evenly. (As even as an initial round-robin selector
> can be!)
A sentence could be
== Series Details ==
Series: drm/i915: Restore relaxed padding (OCL_OOB_SUPPRES_ENABLE) for skl+
URL : https://patchwork.freedesktop.org/series/64920/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6657_full -> Patchwork_13924_full
On Thu, 08 Aug 2019, Lucas De Marchi wrote:
> On Thu, Aug 08, 2019 at 09:47:56AM -0700, Daniele Ceraolo Spurio wrote:
>>
>>
>>On 8/8/19 6:58 AM, Jani Nikula wrote:
>>>On Thu, 08 Aug 2019, Chris Wilson wrote:
Quoting Daniele Ceraolo Spurio (2019-08-08 02:44:20)
>I've been trying to
After a preempt-to-busy, we may find an active request that is caught
between execution states. Walk back along the timeline instead of the
execution list to be safe.
[ 106.417541] i915 :00:02.0: Resetting rcs0 for preemption time out
[ 106.417659]
== Series Details ==
Series: drm/i915: split out uncore_mmio_debug
URL : https://patchwork.freedesktop.org/series/64941/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6661 -> Patchwork_13931
Summary
---
**SUCCESS**
== Series Details ==
Series: drm/i915: split out uncore_mmio_debug
URL : https://patchwork.freedesktop.org/series/64941/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: split out uncore_mmio_debug
+drivers/gpu/drm/i915/intel_uncore.c:1231:1:
== Series Details ==
Series: drm/i915: Fix HW readout for crtc_clock in HDMI mode (rev2)
URL : https://patchwork.freedesktop.org/series/64909/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6657_full -> Patchwork_13923_full
From: Daniele Ceraolo Spurio
Multiple uncore structures will share the debug infrastructure, so
move it to a common place and add extra locking around it.
Also, since we now have a separate object, it is cleaner to have
dedicated functions working on the object to stop and restart the
mmio
Runtime suspend kicks in quicker if we flush any idle work that may been
accrued.
Signed-off-by: Chris Wilson
---
tests/perf_pmu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/perf_pmu.c b/tests/perf_pmu.c
index d392a67d4..351090710 100644
--- a/tests/perf_pmu.c
+++
== Series Details ==
Series: drm/i915: Make debugfs/per_file_stats scale better
URL : https://patchwork.freedesktop.org/series/64919/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6657_full -> Patchwork_13922_full
Summary
301 - 343 of 343 matches
Mail list logo
