RE: [PATCH 06/10] drm/ttm: fix busy memory to fail other user v10

2019-05-23 Thread Liang, Prike
Use Abaqus torturing the amdgpu driver more times will running into locking first busy BO deadlock .Then the caller will return EAGAIN and eventually dm_plane_helper_prepare_fb popups out pinned failed message .For this case, the patch#7 can we add EAGAIN as ERESTARTSYS which filter out the ann

Re: [PATCH v15 05/17] arms64: untag user pointers passed to memory syscalls

2019-05-23 Thread Evgenii Stepanov
On Thu, May 23, 2019 at 2:04 AM Catalin Marinas wrote: > > On Wed, May 22, 2019 at 02:16:57PM -0700, Evgenii Stepanov wrote: > > On Wed, May 22, 2019 at 4:49 AM Catalin Marinas > > wrote: > > > On Mon, May 06, 2019 at 06:30:51PM +0200, Andrey Konovalov wrote: > > > > This patch is a part of a se

RE: [PATCH] drm/amdgpu: Need to set the baco cap before baco reset

2019-05-23 Thread Deng, Emily
>-Original Message- >From: Alex Deucher >Sent: Friday, May 24, 2019 12:09 AM >To: Deng, Emily >Cc: amd-gfx list >Subject: Re: [PATCH] drm/amdgpu: Need to set the baco cap before baco >reset > >[CAUTION: External Email] > >On Thu, May 23, 2019 at 6:22 AM Emily Deng wrote: >> >> For pas

[PATCH 4/8] drm/amdgpu: Add function to add/remove gws to kfd process

2019-05-23 Thread Zeng, Oak
GWS bo is shared between all kfd processes. Add function to add gws to kfd process's bo list so gws can be evicted from and restored for process. Change-Id: I75d74cfdadb7075ff8b2b68634e205deb73dc1ea Signed-off-by: Oak Zeng Reviewed-by: Felix Kuehling --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd

[PATCH 3/8] drm/amdkfd: Allocate gws on device initialization

2019-05-23 Thread Zeng, Oak
On device initialization, KFD allocates all (64) gws which is shared by all KFD processes. Change-Id: I1f1274b8d4f6a8ad08785e2791a9a79def75e913 Signed-off-by: Oak Zeng Reviewed-by: Felix Kuehling --- drivers/gpu/drm/amd/amdkfd/kfd_device.c | 14 +- drivers/gpu/drm/amd/amdkfd/kfd_pri

[PATCH 7/8] drm/amdkfd: PM4 packets change to support GWS

2019-05-23 Thread Zeng, Oak
Add a field in map_queues packet to indicate whether this is a gws control queue. Only one queue per process can be gws control queue. Change num_gws field in map_process packet to 7 bits Change-Id: I0db91d99c6962d14f9202b2eb950f8e7e497b79e Signed-off-by: Oak Zeng Reviewed-by: Felix Kuehling ---

[PATCH 8/8] drm/amdkfd: Use kfd fd to mmap mmio

2019-05-23 Thread Zeng, Oak
TTM doesn't support CPU mapping of sg type bo (under which mmio bo is created). Switch mmaping of mmio page to kfd device file. Change-Id: I1a1a24f2ac0662be3783d460c137731ade007b83 Signed-off-by: Oak Zeng --- drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 46 drivers

[PATCH 6/8] drm/amdkfd: New IOCTL to allocate queue GWS

2019-05-23 Thread Zeng, Oak
Add a new kfd ioctl to allocate queue GWS. Queue GWS is released on queue destroy. Change-Id: I60153c26a577992ad873e4292e759e5c3d5bbd15 Signed-off-by: Oak Zeng --- drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 27 +++ include/uapi/linux/kfd_ioctl.h | 20 +++

[PATCH 1/8] drm/amdkfd: Add gws number to kfd topology node properties

2019-05-23 Thread Zeng, Oak
Add amdgpu_amdkfd interface to get num_gws and add num_gws to /sys/class/kfd/kfd/topology/nodes/x/properties. Only report num_gws if MEC FW support GWS barriers. Currently it is determined by a module parameter which will be replaced with MEC FW version check when firmware is ready. Change-Id: Ie0

[PATCH 2/8] drm/amdgpu: Add interface to alloc gws from amdgpu

2019-05-23 Thread Zeng, Oak
Add amdgpu_amdkfd interface to alloc and free gws from amdgpu Change-Id: I4eb418356e5a6051aa09c5e2c4a454263631d6ab Signed-off-by: Oak Zeng Reviewed-by: Felix Kuehling --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c | 34 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h |

[PATCH 5/8] drm/amdkfd: Add function to set queue gws

2019-05-23 Thread Zeng, Oak
Add functions in process queue manager to set/unset queue gws. Also set process's number of gws used. Currently only one queue in process can use and use all gws. Change-Id: I03e480c8692db3eabfc3a188cce8904d5d962ab7 Signed-off-by: Oak Zeng --- drivers/gpu/drm/amd/amdkfd/kfd_priv.h |

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Khalid Aziz
On 5/23/19 2:11 PM, Catalin Marinas wrote: > Hi Khalid, > > On Thu, May 23, 2019 at 11:51:40AM -0600, Khalid Aziz wrote: >> On 5/21/19 6:04 PM, Kees Cook wrote: >>> As an aside: I think Sparc ADI support in Linux actually side-stepped >>> this[1] (i.e. chose "solution 1"): "All addresses passed to

Re: [PATCH 6/7] drm/amdkfd: New IOCTL to allocate queue GWS

2019-05-23 Thread Kuehling, Felix
On 2019-05-23 2:41 p.m., Zeng, Oak wrote: > Add a new kfd ioctl to allocate queue GWS. Queue > GWS is released on queue destroy. > > Change-Id: I60153c26a577992ad873e4292e759e5c3d5bbd15 > Signed-off-by: Oak Zeng > --- > drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 30 +

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Khalid Aziz
On 5/23/19 2:11 PM, Catalin Marinas wrote: > Hi Khalid, > > On Thu, May 23, 2019 at 11:51:40AM -0600, Khalid Aziz wrote: >> On 5/21/19 6:04 PM, Kees Cook wrote: >>> As an aside: I think Sparc ADI support in Linux actually side-stepped >>> this[1] (i.e. chose "solution 1"): "All addresses passed to

Re: [PATCH 5/7] drm/amdkfd: Add function to set queue gws

2019-05-23 Thread Kuehling, Felix
On 2019-05-23 2:41 p.m., Zeng, Oak wrote: > Add functions in process queue manager to > set queue gws. Also set process's number > of gws used. Currently only one queue in > process can use and use all gws. > > Change-Id: I03e480c8692db3eabfc3a188cce8904d5d962ab7 > Signed-off-by: Oak Zeng > --- >

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Kees Cook
On Thu, May 23, 2019 at 06:43:46PM +0100, Catalin Marinas wrote: > On Thu, May 23, 2019 at 09:38:19AM -0700, Kees Cook wrote: > > What on this front would you be comfortable with? Given it's a new > > feature isn't it sufficient to have a CONFIG (and/or boot option)? > > I'd rather avoid re-buildi

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Catalin Marinas
Hi Khalid, On Thu, May 23, 2019 at 11:51:40AM -0600, Khalid Aziz wrote: > On 5/21/19 6:04 PM, Kees Cook wrote: > > As an aside: I think Sparc ADI support in Linux actually side-stepped > > this[1] (i.e. chose "solution 1"): "All addresses passed to kernel must > > be non-ADI tagged addresses." (An

Re: GPU passthrough support for Stoney [Radeon R2/R3/R4/R5 Graphics]?

2019-05-23 Thread Micah Morton
On Thu, May 23, 2019 at 9:55 AM Micah Morton wrote: > > On Wed, May 22, 2019 at 6:11 PM Alex Deucher wrote: > > > > On Wed, May 22, 2019 at 7:00 PM Micah Morton wrote: > > > > > > On Wed, May 22, 2019 at 1:39 PM Alex Deucher > > > wrote: > > > > > > > > On Tue, May 21, 2019 at 1:46 PM Micah Mo

[PATCH 7/7] drm/amdkfd: PM4 packets change to support GWS

2019-05-23 Thread Zeng, Oak
Add a field in map_queues packet to indicate whether this is a gws control queue. Only one queue per process can be gws control queue. Change num_gws field in map_process packet to 7 bits Change-Id: I0db91d99c6962d14f9202b2eb950f8e7e497b79e Signed-off-by: Oak Zeng Reviewed-by: Felix Kuehling ---

[PATCH 1/7] drm/amdkfd: Add gws number to kfd topology node properties

2019-05-23 Thread Zeng, Oak
Add amdgpu_amdkfd interface to get num_gws and add num_gws to /sys/class/kfd/kfd/topology/nodes/x/properties. Only report num_gws if MEC FW support GWS barriers. Currently it is determined by a module parameter which will be replaced with MEC FW version check when firmware is ready. Change-Id: Ie0

[PATCH 4/7] drm/amdgpu: Add function to add/remove gws to kfd process

2019-05-23 Thread Zeng, Oak
GWS bo is shared between all kfd processes. Add function to add gws to kfd process's bo list so gws can be evicted from and restored for process. Change-Id: I75d74cfdadb7075ff8b2b68634e205deb73dc1ea Signed-off-by: Oak Zeng Reviewed-by: Felix Kuehling --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd

[PATCH 6/7] drm/amdkfd: New IOCTL to allocate queue GWS

2019-05-23 Thread Zeng, Oak
Add a new kfd ioctl to allocate queue GWS. Queue GWS is released on queue destroy. Change-Id: I60153c26a577992ad873e4292e759e5c3d5bbd15 Signed-off-by: Oak Zeng --- drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 30 ++ include/uapi/linux/kfd_ioctl.h | 20

[PATCH 2/7] drm/amdgpu: Add interface to alloc gws from amdgpu

2019-05-23 Thread Zeng, Oak
Add amdgpu_amdkfd interface to alloc and free gws from amdgpu Change-Id: I4eb418356e5a6051aa09c5e2c4a454263631d6ab Signed-off-by: Oak Zeng Reviewed-by: Felix Kuehling --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c | 34 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h |

[PATCH 3/7] drm/amdkfd: Allocate gws on device initialization

2019-05-23 Thread Zeng, Oak
On device initialization, KFD allocates all (64) gws which is shared by all KFD processes. Change-Id: I1f1274b8d4f6a8ad08785e2791a9a79def75e913 Signed-off-by: Oak Zeng Reviewed-by: Felix Kuehling --- drivers/gpu/drm/amd/amdkfd/kfd_device.c | 14 +- drivers/gpu/drm/amd/amdkfd/kfd_pri

[PATCH 5/7] drm/amdkfd: Add function to set queue gws

2019-05-23 Thread Zeng, Oak
Add functions in process queue manager to set queue gws. Also set process's number of gws used. Currently only one queue in process can use and use all gws. Change-Id: I03e480c8692db3eabfc3a188cce8904d5d962ab7 Signed-off-by: Oak Zeng --- drivers/gpu/drm/amd/amdkfd/kfd_priv.h | 6 ++

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Khalid Aziz
On 5/21/19 6:04 PM, Kees Cook wrote: > As an aside: I think Sparc ADI support in Linux actually side-stepped > this[1] (i.e. chose "solution 1"): "All addresses passed to kernel must > be non-ADI tagged addresses." (And sadly, "Kernel does not enable ADI > for kernel code.") I think this was a mist

[PATCH] drm/amdgpu/ras: use GPU page size for page retirement

2019-05-23 Thread Alex Deucher
Bad pages are stored in GPU page size since they are VRAM pages. Signed-off-by: Alex Deucher --- drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c inde

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Catalin Marinas
On Thu, May 23, 2019 at 09:38:19AM -0700, Kees Cook wrote: > On Thu, May 23, 2019 at 03:44:49PM +0100, Catalin Marinas wrote: > > There is also the obvious requirement which I didn't mention: new user > > space continues to run on new/subsequent kernel versions. That's one of > > the points of cont

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Catalin Marinas
On Thu, May 23, 2019 at 08:44:12AM -0700, enh wrote: > On Thu, May 23, 2019 at 7:45 AM Catalin Marinas > wrote: > > On Wed, May 22, 2019 at 01:47:36PM -0700, Kees Cook wrote: > > > For userspace, how would a future binary choose TBI over MTE? If it's > > > a library issue, we can't use an ELF bit

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Catalin Marinas
On Thu, May 23, 2019 at 11:42:57AM +0100, Dave P Martin wrote: > On Wed, May 22, 2019 at 09:20:52PM -0300, Jason Gunthorpe wrote: > > On Wed, May 22, 2019 at 02:49:28PM +0100, Dave Martin wrote: > > > If multiple people will care about this, perhaps we should try to > > > annotate types more explic

Re: GPU passthrough support for Stoney [Radeon R2/R3/R4/R5 Graphics]?

2019-05-23 Thread Micah Morton
On Wed, May 22, 2019 at 6:11 PM Alex Deucher wrote: > > On Wed, May 22, 2019 at 7:00 PM Micah Morton wrote: > > > > On Wed, May 22, 2019 at 1:39 PM Alex Deucher wrote: > > > > > > On Tue, May 21, 2019 at 1:46 PM Micah Morton wrote: > > > > > > > > On Fri, May 17, 2019 at 9:59 AM Alex Deucher

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Kees Cook
On Thu, May 23, 2019 at 03:44:49PM +0100, Catalin Marinas wrote: > There is also the obvious requirement which I didn't mention: new user > space continues to run on new/subsequent kernel versions. That's one of > the points of contention for this series (ignoring MTE) with the > maintainers having

[PATCH] drm/amdgpu: enable PCIE atomics ops support

2019-05-23 Thread Xiao, Jack
GPU atomics operation depends on PCIE atomics support. Always enable PCIE atomics ops support in case that it hasn't been enabled. Signed-off-by: Jack Xiao --- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_

Re: [PATCH] drm/amdgpu: Need to set the baco cap before baco reset

2019-05-23 Thread Alex Deucher
On Thu, May 23, 2019 at 6:22 AM Emily Deng wrote: > > For passthrough, after rebooted the VM, driver will do > a baco reset before doing other driver initialization during loading > driver. For doing the baco reset, it will first > check the baco reset capability. So first need to set the > cap f

Re: Quick question for the mobile Raven Ridge auto-rotate function

2019-05-23 Thread Alex Deucher
On Thu, May 23, 2019 at 1:41 AM Luya Tshimbalanga wrote: > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello team, > > Thank for you making mobile Raven Ridge nearly fully functional with the > open source driver for multiple devices like HP Envy x360 Ryzen 2500u. > However, missing

Re: [PATCH] Revert "drm/amdgpu: Need to set the baco cap before baco reset"

2019-05-23 Thread Alex Deucher
On Thu, May 23, 2019 at 2:24 AM Emily Deng wrote: > > This reverts commit 13f2a375b58918873833cf6859332f960c6cf922. > > Signed-off-by: Emily Deng Please go ahead and revert. Acked-by: Alex Deucher > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 10 +- > drivers/gpu/drm/am

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread enh
On Thu, May 23, 2019 at 7:45 AM Catalin Marinas wrote: > > On Wed, May 22, 2019 at 01:47:36PM -0700, Kees Cook wrote: > > On Wed, May 22, 2019 at 05:35:27PM +0100, Catalin Marinas wrote: > > > The two hard requirements I have for supporting any new hardware feature > > > in Linux are (1) a single

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Catalin Marinas
On Wed, May 22, 2019 at 09:58:22AM -0700, enh wrote: > i was questioning the argument about the ioctl issues, and saying that > from my perspective, untagging bugs are not really any different than > any other kind of kernel bug. Once this series gets in, they are indeed just kernel bugs. What I w

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Catalin Marinas
On Wed, May 22, 2019 at 12:21:27PM -0700, Kees Cook wrote: > If a process wants to not tag, that's also up to the allocator where > it can decide not to ask the kernel, and just not tag. Nothing breaks in > userspace if a process is NOT tagging and untagged_addr() exists or is > missing. This, I th

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Catalin Marinas
On Wed, May 22, 2019 at 01:47:36PM -0700, Kees Cook wrote: > On Wed, May 22, 2019 at 05:35:27PM +0100, Catalin Marinas wrote: > > The two hard requirements I have for supporting any new hardware feature > > in Linux are (1) a single kernel image binary continues to run on old > > hardware while mak

Re: [PATCH] drm/amdgpu: sort probed modes before adding common modes

2019-05-23 Thread Kazlauskas, Nicholas
On 5/23/19 10:03 AM, Mohan Marimuthu, Yogesh wrote: > > [Why] > There are monitors which can have more than one preferred mode > set. There are chances in these monitors that if common modes are > added in function amdgpu_dm_connector_add_common_modes(), these > common modes can be calculated with

Re: [PATCH 06/10] drm/ttm: fix busy memory to fail other user v10

2019-05-23 Thread Koenig, Christian
Am 23.05.19 um 13:50 schrieb Zhou, David(ChunMing): > 在 2019/5/23 19:03, Christian König 写道: >> [CAUTION: External Email] >> >> Am 23.05.19 um 12:24 schrieb zhoucm1: >>> >>> On 2019年05月22日 20:59, Christian König wrote: [CAUTION: External Email] BOs on the LRU might be blocked during

[PATCH] drm/amdgpu: sort probed modes before adding common modes

2019-05-23 Thread Mohan Marimuthu, Yogesh
[Why] There are monitors which can have more than one preferred mode set. There are chances in these monitors that if common modes are added in function amdgpu_dm_connector_add_common_modes(), these common modes can be calculated with different preferred mode than the one used in function decide_cr

Re: [PATCH 06/10] drm/ttm: fix busy memory to fail other user v10

2019-05-23 Thread Chunming Zhou
在 2019/5/23 19:03, Christian König 写道: > [CAUTION: External Email] > > Am 23.05.19 um 12:24 schrieb zhoucm1: >> >> >> On 2019年05月22日 20:59, Christian König wrote: >>> [CAUTION: External Email] >>> >>> BOs on the LRU might be blocked during command submission >>> and cause OOM situations. >>> >>> A

Re: [PATCH 01/12] dma-buf: add dynamic caching of sg_table

2019-05-23 Thread Daniel Vetter
On Thu, May 23, 2019 at 1:30 PM Daniel Vetter wrote: > > On Thu, May 23, 2019 at 1:21 PM Koenig, Christian > wrote: > > > > Am 22.05.19 um 20:30 schrieb Daniel Vetter: > > > [SNIP] > > >> Well, it seems you are making incorrect assumptions about the cache > > >> maintenance of DMA-buf here. > > >

Re: [PATCH 01/12] dma-buf: add dynamic caching of sg_table

2019-05-23 Thread Daniel Vetter
On Thu, May 23, 2019 at 1:21 PM Koenig, Christian wrote: > > Am 22.05.19 um 20:30 schrieb Daniel Vetter: > > [SNIP] > >> Well, it seems you are making incorrect assumptions about the cache > >> maintenance of DMA-buf here. > >> > >> At least for all DRM devices I'm aware of mapping/unmapping an >

Re: [PATCH 01/12] dma-buf: add dynamic caching of sg_table

2019-05-23 Thread Koenig, Christian
Am 22.05.19 um 20:30 schrieb Daniel Vetter: > [SNIP] >> Well, it seems you are making incorrect assumptions about the cache >> maintenance of DMA-buf here. >> >> At least for all DRM devices I'm aware of mapping/unmapping an >> attachment does *NOT* have any cache maintenance implications. >> >> E.

Re: [PATCH 06/10] drm/ttm: fix busy memory to fail other user v10

2019-05-23 Thread Christian König
Am 23.05.19 um 12:24 schrieb zhoucm1: On 2019年05月22日 20:59, Christian König wrote: [CAUTION: External Email] BOs on the LRU might be blocked during command submission and cause OOM situations. Avoid this by blocking for the first busy BO not locked by the same ticket as the BO we are searchi

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Dave Martin
On Wed, May 22, 2019 at 09:20:52PM -0300, Jason Gunthorpe wrote: > On Wed, May 22, 2019 at 02:49:28PM +0100, Dave Martin wrote: > > On Tue, May 21, 2019 at 03:48:56PM -0300, Jason Gunthorpe wrote: > > > On Fri, May 17, 2019 at 03:49:31PM +0100, Catalin Marinas wrote: > > > > > > > The tagged point

Re: [PATCH 06/10] drm/ttm: fix busy memory to fail other user v10

2019-05-23 Thread zhoucm1
On 2019年05月22日 20:59, Christian König wrote: [CAUTION: External Email] BOs on the LRU might be blocked during command submission and cause OOM situations. Avoid this by blocking for the first busy BO not locked by the same ticket as the BO we are searching space for. v10: completely start ov

[PATCH] drm/amdgpu: Need to set the baco cap before baco reset

2019-05-23 Thread Emily Deng
For passthrough, after rebooted the VM, driver will do a baco reset before doing other driver initialization during loading driver. For doing the baco reset, it will first check the baco reset capability. So first need to set the cap from the vbios information or baco reset won't be enabled. Sign

Re: [PATCH 01/10] drm/ttm: Make LRU removal optional.

2019-05-23 Thread Christian König
Am 23.05.19 um 11:15 schrieb zhoucm1: On 2019年05月22日 20:59, Christian König wrote: [SNIP] @@ -203,7 +204,10 @@ void ttm_eu_fence_buffer_objects(struct ww_acquire_ctx *ticket, reservation_object_add_shared_fence(bo->resv, fence); else reservation_object_add_excl_fence(bo->resv,

Re: [PATCH 10/10] drm/amdgpu: stop removing BOs from the LRU v3

2019-05-23 Thread Christian König
Leaving BOs on the LRU is harmless. We always did this for VM page table and per VM BOs. The key point is that BOs which couldn't be reserved can't be evicted. So what happened is that an application used basically all of VRAM during CS and because of this X server couldn't pin a BO for scanou

Re: [PATCH 01/10] drm/ttm: Make LRU removal optional.

2019-05-23 Thread zhoucm1
On 2019年05月22日 20:59, Christian König wrote: [CAUTION: External Email] We are already doing this for DMA-buf imports and also for amdgpu VM BOs for quite a while now. If this doesn't run into any problems we are probably going to stop removing BOs from the LRU altogether. Signed-off-by: Chri

Re: [PATCH v15 05/17] arms64: untag user pointers passed to memory syscalls

2019-05-23 Thread Catalin Marinas
On Wed, May 22, 2019 at 02:16:57PM -0700, Evgenii Stepanov wrote: > On Wed, May 22, 2019 at 4:49 AM Catalin Marinas > wrote: > > On Mon, May 06, 2019 at 06:30:51PM +0200, Andrey Konovalov wrote: > > > This patch is a part of a series that extends arm64 kernel ABI to allow to > > > pass tagged use

RE: [PATCH 10/10] drm/amdgpu: stop removing BOs from the LRU v3

2019-05-23 Thread Liang, Prike
Hi, Christian Thanks for you patch .Those patches can fix amdgpu bo pinned failed issue during perform dm_plane_helper_prepare_fb and Abaqus performance seems improved. But there some error message can be observer. Do we need drop amdgpu_vm_validate_pt_bos() error message and other warning

Re: [PATCH v15 00/17] arm64: untag user pointers passed to the kernel

2019-05-23 Thread Catalin Marinas
On Wed, May 22, 2019 at 04:09:31PM -0700, enh wrote: > On Wed, May 22, 2019 at 4:03 PM Evgenii Stepanov wrote: > > On Wed, May 22, 2019 at 1:47 PM Kees Cook wrote: > > > On Wed, May 22, 2019 at 05:35:27PM +0100, Catalin Marinas wrote: > > > > I would also expect the C library or dynamic loader to