Re: [PATCH 02/13] amdgpu: don't initialize range->list in amdgpu_hmm_init_range

On Wed, Jul 31, 2019 at 01:25:06PM +, Kuehling, Felix wrote: > On 2019-07-30 1:51 a.m., Christoph Hellwig wrote: > > The list is used to add the range to another list as an entry in the > > core hmm code, so there is no need to initialize it in a driver. > > I've seen code that uses

[PATCH 27/34] mm/memory.c: convert put_page() to 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

[PATCH 19/34] fsl_hypervisor: convert put_page() to 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

[PATCH 04/34] x86/kvm: convert put_page() to 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(). This is part a tree-wide conversion, as described in commit fc1d8e7cca2d ("mm: introduce put_user_page*(), placeholder versions"). Cc:

[PATCH 02/34] net/rds: convert put_page() to 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

[PATCH 15/34] staging/vc04_services: convert put_page() to 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

Re: [PATCH 00/34] put_user_pages(): miscellaneous call sites

On 8/1/19 7:16 PM, john.hubb...@gmail.com wrote: > From: John Hubbard > > Hi, > > These are best characterized as miscellaneous conversions: many (not all) > call sites that don't involve biovec or iov_iter, nor mm/. It also leaves > out a few call sites that require some more work. These are

[PATCH 09/34] media/v4l2-core/mm: convert put_page() to 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

Re: [PATCH/RFC 07/12] drm: rcar-du: lvds: Add support for dual link panels

Hi Fabrizio, Thank you for the patch. On Fri, Aug 02, 2019 at 08:34:04AM +0100, Fabrizio Castro wrote: > If the display comes with two ports, assume it supports dual > link. > > Signed-off-by: Fabrizio Castro > --- > drivers/gpu/drm/rcar-du/rcar_lvds.c | 3 +++ > 1 file changed, 3

[PATCH 05/34] drm/etnaviv: convert release_pages() to put_user_pages()

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

[PATCH 31/34] nfs: convert put_page() to 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

[PATCH 22/34] orangefs: convert put_page() to 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

[PATCH 00/34] put_user_pages(): miscellaneous call sites

From: John Hubbard Hi, These are best characterized as miscellaneous conversions: many (not all) call sites that don't involve biovec or iov_iter, nor mm/. It also leaves out a few call sites that require some more work. These are mostly pretty simple ones. It's probably best to send all of

[PATCH 18/34] fbdev/pvr2fb: convert put_page() to 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

[PATCH 08/34] media/ivtv: convert put_page() to 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

[PATCH 16/34] drivers/tee: convert put_page() to 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

[PATCH 00/34] put_user_pages(): miscellaneous call sites

From: John Hubbard Hi, These are best characterized as miscellaneous conversions: many (not all) call sites that don't involve biovec or iov_iter, nor mm/. It also leaves out a few call sites that require some more work. These are mostly pretty simple ones. It's probably best to send all of

Re: [PATCH v2 6/7] drm/panfrost: Add support for GPU heap allocations

On 30/07/2019 20:08, Rob Herring wrote: > On Tue, Jul 30, 2019 at 12:55 PM Alyssa Rosenzweig > wrote: >> >>> In any case, per process AS is a prerequisite to all this. >> >> Oh, I hadn't realized that was still a todo. In the meantime, what's the >> implication of shipping without it? (I.e. in

[PATCH 20/34] xen: convert put_page() to 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

[PATCH 01/34] mm/gup: add make_dirty arg to put_user_pages_dirty_lock()

From: John Hubbard Provide 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*()

[PATCH 17/34] vfio: convert put_page() to 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

[PATCH 21/34] fs/exec.c: convert put_page() to 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

[PATCH 10/34] genwqe: convert put_page() to 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

[PATCH 23/34] uprobes: convert put_page() to 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

[PATCH 28/34] mm/madvise.c: convert put_page() to 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

[PATCH 32/34] goldfish_pipe: convert put_page() to 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

[PATCH 30/34] crypt: convert put_page() to 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

[PATCH 25/34] mm/frame_vector.c: convert put_page() to 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

[PATCH 06/34] drm/i915: convert put_page() to 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

Re: [PATCH v19 00/15] arm64: untag user pointers passed to the kernel

On Thu, Aug 1, 2019 at 2:11 PM Kevin Brodsky wrote: > > On 31/07/2019 17:50, Dave Hansen wrote: > > On 7/23/19 10:58 AM, Andrey Konovalov wrote: > >> The mmap and mremap (only new_addr) syscalls do not currently accept > >> tagged addresses. Architectures may interpret the tag as a background >

[PATCH 29/34] mm/process_vm_access.c: convert put_page() to 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

Re: [LKP] [drm/mgag200] 90f479ae51: vm-scalability.median -18.8% regression

Hi Am 01.08.19 um 15:30 schrieb Michel Dänzer: > On 2019-08-01 8:19 a.m., Rong Chen wrote: >> Hi, >> >> On 7/31/19 6:21 PM, Michel Dänzer wrote: >>> On 2019-07-31 11:25 a.m., Huang, Ying wrote: Hi, Daniel, Daniel Vetter writes: > On Tue, Jul 30, 2019 at 10:27 PM Dave

Re: [PATCH v2 1/8] drm/etnaviv: simplify unbind checks

Hi, On Fri, Jul 05, 2019 at 07:17:20PM +0200, Lucas Stach wrote: > Remember if the GPU has been sucessfully initialized. Only in that case > do we need to clean up various structures in the unbind path. If the > GPU hasn't been sucessfully initialized all the cleanups should happen > in the

Re: [PATCH/RFC 06/12] drm: rcar-du: lvds: Do not look at ports for identifying bridges

Hi Fabrizio, Thank you for the patch. On Fri, Aug 02, 2019 at 08:34:03AM +0100, Fabrizio Castro wrote: > We may be connected to a dual LVDS display, therefore checking > if node != remote_input for identifying bridges is not going to > work anymore. > We could try to match the ports on the

[PATCH] drm/komeda: Initialize and enable output polling on Komeda

From: "Lowry Li (Arm Technology China)" Initialize and enable output polling on Komeda. Changes since v1: 1. Enable the polling before registering the driver; 2. Disable the polling after unregistering the driver. Changes since v2: 1. If driver register failed, disable the polling.

Re: [PATCH 00/34] put_user_pages(): miscellaneous call sites

On Thu, Aug 01, 2019 at 07:16:19PM -0700, john.hubb...@gmail.com wrote: > This is part a tree-wide conversion, as described in commit fc1d8e7cca2d > ("mm: introduce put_user_page*(), placeholder versions"). That commit > has an extensive description of the problem and the planned steps to > solve

Re: [PATCH/RFC 05/12] drm: rcar-du: lvds: Add data swap support

Hi Fabrizio, Thank you for the patch. On Fri, Aug 02, 2019 at 08:34:02AM +0100, Fabrizio Castro wrote: > When in vertical stripe mode of operation, there is the option > of swapping even data and odd data on the two LVDS interfaces > used to drive the video output. > Add data swap support by

Re: [PATCH/RFC 04/12] dt-bindings: display: Add bindings for Advantech IDK-2121WR

Hi Fabrizio, Thank you for the patch. On Fri, Aug 02, 2019 at 08:34:01AM +0100, Fabrizio Castro wrote: > This panel is handled through the generic lvds-panel bindings, > so only needs its additional compatible specified. > > Some panel specific documentation can be found here: s/panel

Re: [PATCH] drm/virtio: kick vq outside of the vq lock

> @@ -291,11 +291,9 @@ static int virtio_gpu_queue_ctrl_buffer_locked(struct > virtio_gpu_device *vgdev, > trace_virtio_gpu_cmd_queue(vq, > (struct virtio_gpu_ctrl_hdr *)vbuf->buf); > > - virtqueue_kick(vq); > + ret =

Re: [PATCH/RFC 03/12] dt-bindings: panel: lvds: Add dual-link LVDS display support

Hi Fabrizio, Thank you for the patch. On Fri, Aug 02, 2019 at 08:34:00AM +0100, Fabrizio Castro wrote: > Dual-link LVDS displays have two ports, therefore document this > with the bindings. > > Signed-off-by: Fabrizio Castro > --- > .../bindings/display/panel/panel-lvds.txt | 91 >

[PATCH] drm/komeda: Initialize and enable output polling on Komeda

From: "Lowry Li (Arm Technology China)" Initialize and enable output polling on Komeda. Changes since v1: 1. Enable the polling before registering the driver; 2. Disable the polling after unregistering the driver. Signed-off-by: Lowry Li (Arm Technology China) ---

[Bug 111281] When the s admin try to create different types of question in various difficulty level by single upload mode database error occurred

https://bugs.freedesktop.org/show_bug.cgi?id=111281 Andre Klapper changed: What|Removed |Added Status|NEW |RESOLVED Group|

Re: [PATCH/RFC 01/12] dt-bindings: display: renesas: lvds: RZ/G2E needs renesas,companion too

Hello Fabrizio, Thank you for the patch. On Fri, Aug 02, 2019 at 08:33:58AM +0100, Fabrizio Castro wrote: > Document RZ/G2E support for property renesas,companion. > > Signed-off-by: Fabrizio Castro Reviewed-by: Laurent Pinchart and taken in my tree. > --- >

Re: [PATCH/RFC 02/12] dt-bindings: display: renesas: lvds: Document renesas,swap-data

Hi Fabrizio, Thank you for the patch. On Fri, Aug 02, 2019 at 08:33:59AM +0100, Fabrizio Castro wrote: > R-Car D3, R-Car E3, and RZ/G2E support dual-link mode. > In such a mode, the first LVDS encoder emits even data, and the > second LVDS encoder emits odd data. This patch documents property >

[Bug 111281] When the s admin try to create different types of question in various difficulty level by single upload mode database error occurred

https://bugs.freedesktop.org/show_bug.cgi?id=111281 dhrisya changed: What|Removed |Added Status|ASSIGNED|NEW -- You are receiving this mail because:

Re: [PATCH v9 04/18] kunit: test: add kunit_stream a std::stream like logger

On 2019-08-01, Brendan Higgins wrote: > On Fri, Jul 26, 2019 at 1:31 AM Petr Mladek wrote: >> On Thu 2019-07-25 13:21:12, Brendan Higgins wrote: >>> On Wed, Jul 24, 2019 at 12:31 AM Petr Mladek wrote: On Mon 2019-07-22 16:54:10, Stephen Boyd wrote: > Quoting Brendan Higgins (2019-07-22

[PATCH/RFC 07/12] drm: rcar-du: lvds: Add support for dual link panels

If the display comes with two ports, assume it supports dual link. Signed-off-by: Fabrizio Castro --- drivers/gpu/drm/rcar-du/rcar_lvds.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/rcar-du/rcar_lvds.c b/drivers/gpu/drm/rcar-du/rcar_lvds.c index 2d54ae5..97c51c2

[PATCH/RFC 09/12] drm: rcar-du: lvds: Fix companion's mode

The companion encoder needs to be told to use the same mode as the primary encoder. Fixes: e9e8798ab7b8 ("drm: rcar-du: lvds: Add support for dual-link mode") Signed-off-by: Fabrizio Castro --- drivers/gpu/drm/rcar-du/rcar_lvds.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff

[PATCH/RFC 06/12] drm: rcar-du: lvds: Do not look at ports for identifying bridges

We may be connected to a dual LVDS display, therefore checking if node != remote_input for identifying bridges is not going to work anymore. We could try to match the ports on the remote end to the LVDS encoders, however the companion LVDS encoder instance doesn't hold a reference to the primary

[PATCH/RFC 04/12] dt-bindings: display: Add bindings for Advantech IDK-2121WR

This panel is handled through the generic lvds-panel bindings, so only needs its additional compatible specified. Some panel specific documentation can be found here: https://buy.advantech.eu/Displays/Embedded-LCD-Kits-High-Brightness/model-IDK-2121WR-K2FHA2E.htm Signed-off-by: Fabrizio Castro

[PATCH/RFC 08/12] drm: rcar-du: lvds: Fix bridge_to_rcar_lvds

Using name "bridge" for macro bridge_to_rcar_lvds argument doesn't work when the pointer name used by the caller is not "bridge". Rename the argument to "bridge_ptr" to allow for any pointer name. Fixes: c6a27fa41fab ("drm: rcar-du: Convert LVDS encoder code to bridge driver") Signed-off-by:

[PATCH/RFC 05/12] drm: rcar-du: lvds: Add data swap support

When in vertical stripe mode of operation, there is the option of swapping even data and odd data on the two LVDS interfaces used to drive the video output. Add data swap support by exposing a new DT property named "renesas,swap-data". Signed-off-by: Fabrizio Castro ---

[PATCH/RFC 02/12] dt-bindings: display: renesas: lvds: Document renesas,swap-data

R-Car D3, R-Car E3, and RZ/G2E support dual-link mode. In such a mode, the first LVDS encoder emits even data, and the second LVDS encoder emits odd data. This patch documents property renesas,swap-data, used to swap even and odd data around. Signed-off-by: Fabrizio Castro ---

[PATCH/RFC 01/12] dt-bindings: display: renesas: lvds: RZ/G2E needs renesas,companion too

Document RZ/G2E support for property renesas,companion. Signed-off-by: Fabrizio Castro --- Documentation/devicetree/bindings/display/bridge/renesas,lvds.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH/RFC 03/12] dt-bindings: panel: lvds: Add dual-link LVDS display support

Dual-link LVDS displays have two ports, therefore document this with the bindings. Signed-off-by: Fabrizio Castro --- .../bindings/display/panel/panel-lvds.txt | 91 -- 1 file changed, 67 insertions(+), 24 deletions(-) diff --git

[PATCH/RFC 00/12] Add dual-LVDS panel support to EK874

Dear All, this series adds support for dual-LVDS panel IDK-2121WR from Advantech: https://buy.advantech.eu/Displays/Embedded-LCD-Kits-High-Brightness/model-IDK-2121WR-K2FHA2E.htm Dual link support is very recent for R-Car Gen3, and I couldn't find much on dual link panels in the kernel either,

[Bug 111283] pending questions can not be downloaded by s admin,privileged admin,privileged examiner

https://bugs.freedesktop.org/show_bug.cgi?id=111283 dhrisya changed: What|Removed |Added Assignee|dri-devel@lists.freedesktop |terrence...@intel.com

[Bug 111283] pending questions can not be downloaded by s admin,privileged admin,privileged examiner

https://bugs.freedesktop.org/show_bug.cgi?id=111283 Bug ID: 111283 Summary: pending questions can not be downloaded by s admin,privileged admin,privileged examiner Product: DRI Version: unspecified Hardware: Other

Re: [LKP] [drm/mgag200] 90f479ae51: vm-scalability.median -18.8% regression

Hi, On 8/1/19 7:58 PM, Thomas Zimmermann wrote: Hi Am 01.08.19 um 13:25 schrieb Feng Tang: Hi Thomas, On Thu, Aug 01, 2019 at 11:59:28AM +0200, Thomas Zimmermann wrote: Hi Am 01.08.19 um 10:37 schrieb Feng Tang: On Thu, Aug 01, 2019 at 02:19:53PM +0800, Rong Chen wrote: commit:

Re: Threaded submission & semaphore sharing

On 02/08/2019 09:10, Koenig, Christian wrote: Am 02.08.2019 07:38 schrieb Lionel Landwerlin : On 02/08/2019 08:21, Koenig, Christian wrote: Am 02.08.2019 07:17 schrieb Lionel Landwerlin : On 02/08/2019 08:08,

Re: Threaded submission & semaphore sharing

Am 02.08.2019 07:38 schrieb Lionel Landwerlin : On 02/08/2019 08:21, Koenig, Christian wrote: Am 02.08.2019 07:17 schrieb Lionel Landwerlin : On 02/08/2019 08:08, Koenig, Christian wrote: Hi Lionel, Well that looks more like your test case is buggy.

<    1   2   3