[PATCH v3 03/41] net/xdp: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 33/41] fs/nfs: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

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

2019-08-06 Thread john . hubbard
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*() var

[PATCH v3 37/41] security/tomoyo: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 09/41] drm/radeon: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 29/41] mm/memory.c: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 36/41] fs/binfmt_elf: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 vers

[PATCH v3 34/41] goldfish_pipe: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 13/41] scif: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 30/41] mm/madvise.c: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 16/41] oradax: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 19/41] vfio: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 25/41] uprobes: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 23/41] fs/exec.c: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 39/41] mm/mlock.c: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 12/41] genwqe: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

[PATCH v3 38/41] powerpc: convert put_page() to put_user_page*()

2019-08-06 Thread john . hubbard
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 v

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

2019-08-06 Thread john . hubbard
From: John Hubbard Hi, This consolidates everything into a "here's what's remaining for Andrew to add to his tree (for now)" series: * The first patch is an updated version of one that is already in the akpm tree. * The next two patches are already in the akpm tree, included here for complet

[PATCH 3/5] drm/amdkfd: Postpone memory mapping flags calculation to mapping time

2019-08-06 Thread Zeng, Oak
Some mapping flags are decided by memory mapping destination which is not know at memory object allocation time. So it is reasonable to decide memory mapping flags at mapping time, instead of alloc time. Record memory allocation flags during allocation time and calculate mapping flags during memory

[PATCH 1/5] drm/amdgpu: Extends amdgpu vm definitions

2019-08-06 Thread Zeng, Oak
Add definition of all supported mtypes. The RW mtype is recently introduced for arcturus. Also add definition for the cachable/snoopable bit, which will be used later in this series. Change-Id: I96fc9bb4b6b1e62bdc10b600d8aaa6a802128d6d Signed-off-by: Oak Zeng --- drivers/gpu/drm/amd/amdgpu/amdgp

[PATCH 5/5] amd/amdgpu: Introduce new page mapping scheme for arcturus

2019-08-06 Thread Zeng, Oak
The new memory mapping scheme is: Fine-grain coherency: local CC and remote UC, with snoop. Coarse-grain coherency: local RW and remote UC, with snoop. Change-Id: I6a071249f953cbed813bfd953b6a2e0826f54f86 Signed-off-by: Oak Zeng --- drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c | 1 + drivers/gpu/drm/a

[PATCH 4/5] drm/amdgpu: Support snooped PTE flag

2019-08-06 Thread Zeng, Oak
Set snooped PTE flag according to mapping flag Change-Id: I799f68ec7a5a1abf32075f5ef31051641a0b3736 Signed-off-by: Oak Zeng --- drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c b/drivers/gpu/drm/amd/amdgpu/gmc_v9_

[PATCH 2/5] drm/amdgpu: Support new arcturus mtype

2019-08-06 Thread Zeng, Oak
Arcturus repurposed mtype WC to RW. Modify gmc functions to support the new mtype Change-Id: Idc338e5386a57020f45262025e2664ab4ba9f291 Signed-off-by: Oak Zeng --- drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 61 ++- drivers/gpu/drm/amd/include/vega10_enum.h | 7

RE: [PATCH 1/2] drm/amdgpu: Export function to flush TLB of specific vm hub

2019-08-06 Thread Zeng, Oak
Ok, will do it. BTW, does those codes below really needed, in function gmc_v10_0_flush_gpu_tlb. I think if we have the bug, then before below codes, when we flush TLB of gfxhub through mmio, it has already triggered the bug. Also as we already invalidated tlb on both mm and gfx hub (in the same

[PATCH] drm/amdgpu: replace readq/writeq with atomic64 operations

2019-08-06 Thread Tao Zhou
readq/writeq are not supported on all architectures Signed-off-by: Tao Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c index 55

RE: [PATCH][drm-next] drm/amd/powerplay: remove redundant duplicated return check

2019-08-06 Thread Quan, Evan
Thanks! Reviewed-by: Evan Quan > -Original Message- > From: Colin King > Sent: Monday, August 05, 2019 6:30 PM > To: Rex Zhu ; Quan, Evan ; > Deucher, Alexander ; Koenig, Christian > ; Zhou, David(ChunMing) > ; David Airlie ; Daniel Vetter > ; amd-gfx@lists.freedesktop.org; dri- > de...@

Re: [PATCH] drm/amdgpu: replace readq/writeq with atomic64 operations

2019-08-06 Thread Jisheng Zhang
On Wed, 7 Aug 2019 10:56:40 +0800 Tao Zhou wrote: > > > readq/writeq are not supported on all architectures > > Signed-off-by: Tao Zhou > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 8 ++-- > 1 file changed, 2 insertions(+), 6 deletions(-) > > diff --git a/drivers/gpu/drm/amd/amd

Re: [PATCH 2/5] drm/amdgpu: Support new arcturus mtype

2019-08-06 Thread Kuehling, Felix
On 2019-08-06 22:31, Zeng, Oak wrote: > Arcturus repurposed mtype WC to RW. Modify gmc functions > to support the new mtype > > Change-Id: Idc338e5386a57020f45262025e2664ab4ba9f291 > Signed-off-by: Oak Zeng > --- > drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 61 > ++-

Re: [PATCH] drm/amdgpu: replace readq/writeq with atomic64 operations

2019-08-06 Thread Alex Deucher
On Tue, Aug 6, 2019 at 11:31 PM Jisheng Zhang wrote: > > On Wed, 7 Aug 2019 10:56:40 +0800 Tao Zhou wrote: > > > > > > > > readq/writeq are not supported on all architectures > > > > Signed-off-by: Tao Zhou > > --- > > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 8 ++-- > > 1 file changed,

Re: [PATCH] drm/amdgpu: replace readq/writeq with atomic64 operations

2019-08-06 Thread Alex Deucher
On Tue, Aug 6, 2019 at 10:56 PM Tao Zhou wrote: > > readq/writeq are not supported on all architectures > > Signed-off-by: Tao Zhou Reviewed-by: Alex Deucher > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 8 ++-- > 1 file changed, 2 insertions(+), 6 deletions(-) > > diff --git a/dri

Re: [PATCH 3/5] drm/amdkfd: Postpone memory mapping flags calculation to mapping time

2019-08-06 Thread Kuehling, Felix
On 2019-08-06 22:31, Zeng, Oak wrote: > Some mapping flags are decided by memory mapping destination which is not > know at memory object allocation time. So it is reasonable to decide memory > mapping flags at mapping time, instead of alloc time. Record memory allocation > flags during allocation

Re: [PATCH 5/5] amd/amdgpu: Introduce new page mapping scheme for arcturus

2019-08-06 Thread Kuehling, Felix
On 2019-08-06 22:31, Zeng, Oak wrote: > The new memory mapping scheme is: > Fine-grain coherency: local CC and remote UC, with snoop. > Coarse-grain coherency: local RW and remote UC, with snoop. > > Change-Id: I6a071249f953cbed813bfd953b6a2e0826f54f86 > Signed-off-by: Oak Zeng > --- > drivers/

[PATCH v2 libdrm 0/3] add ras inject test for gfx and umc module

2019-08-06 Thread Guchun Chen
These patches are to support ras inject test for gfx and umc modules. Patch v2: Correct "eject" in all commits to "inject". Add more error checks and print when parsing configuration file. Add umc multi_uncorrectable test in default configuration file. Guchun Chen (3): amdgpu: add gfx ras injec

[PATCH v2 libdrm 1/3] amdgpu: add gfx ras inject configuration file

2019-08-06 Thread Guchun Chen
This configuration file will be picked up when running gfx ras inject tests by amdgpu_test tool. For the time being, only add those tests that are successfully trafficked. In addition, this file can also be modified by user to add or delete ras inject unit tests for different IP blocks/subblocks.

[PATCH v2 libdrm 2/3] tests/amdgpu/ras: refine ras inject test

2019-08-06 Thread Guchun Chen
Ras inject test framework is invalid with original codes, so refine it to make it work on top of kernel ras inject feature enablement. Change-Id: I63ac27707a69133cd08fa0da308f255b1b169c1f Signed-off-by: Dennis Li Signed-off-by: Guchun Chen --- configure.ac | 18 ++ meson.build

[PATCH v2 libdrm 3/3] amdgpu: add umc ras inject test configuration

2019-08-06 Thread Guchun Chen
Both umc single_correctable and multi_uncorrectable inject types are added. Change-Id: I779f2f4f59c69fb08fdc09b7adba5b36e3af20ce Signed-off-by: Dennis Li Signed-off-by: Guchun Chen --- data/amdgpu_ras.json | 17 + 1 file changed, 17 insertions(+) diff --git a/data/amdgpu_ras.js

Re: [PATCH 15/15] amdgpu: remove CONFIG_DRM_AMDGPU_USERPTR

2019-08-06 Thread Koenig, Christian
Am 06.08.19 um 22:03 schrieb Jason Gunthorpe: > On Tue, Aug 06, 2019 at 02:58:58PM -0400, Alex Deucher wrote: >> On Tue, Aug 6, 2019 at 1:51 PM Kuehling, Felix >> wrote: >>> On 2019-08-06 13:44, Jason Gunthorpe wrote: On Tue, Aug 06, 2019 at 07:05:53PM +0300, Christoph Hellwig wrote: > T

<    1   2