Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-09 Thread Jason Gunthorpe
On Mon, Jul 08, 2019 at 09:30:20AM +1000, Stephen Rothwell wrote: > Hi all, > > On Wed, 3 Jul 2019 17:09:16 -0400 Alex Deucher wrote: > > > > On Wed, Jul 3, 2019 at 5:03 PM Kuehling, Felix > > wrote: > > > > > > On 2019-07-03 10:10 a.m., Jason Gunthorpe wrote: > > > > On Wed, Jul 03, 2019 at

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-08 Thread Stephen Rothwell
Hi Felix, On Mon, 8 Jul 2019 15:26:22 + "Kuehling, Felix" wrote: > > Thank you! Who will be that someone? It should probably be one of the > maintainers of the trees Linux pulls from ... That would be Dave (pushing drm) or Jason (pushing hmm), or both. -- Cheers, Stephen Rothwell pgpsV

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-08 Thread Kuehling, Felix
On 2019-07-07 7:30 p.m., Stephen Rothwell wrote: > Hi all, > > On Wed, 3 Jul 2019 17:09:16 -0400 Alex Deucher wrote: >> On Wed, Jul 3, 2019 at 5:03 PM Kuehling, Felix >> wrote: >>> On 2019-07-03 10:10 a.m., Jason Gunthorpe wrote: On Wed, Jul 03, 2019 at 01:55:08AM +, Kuehling, Felix wro

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-07 Thread Stephen Rothwell
Hi all, On Wed, 3 Jul 2019 17:09:16 -0400 Alex Deucher wrote: > > On Wed, Jul 3, 2019 at 5:03 PM Kuehling, Felix wrote: > > > > On 2019-07-03 10:10 a.m., Jason Gunthorpe wrote: > > > On Wed, Jul 03, 2019 at 01:55:08AM +, Kuehling, Felix wrote: > > >> From: Philip Yang > > >> > > >> In o

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-04 Thread Jason Gunthorpe
On Thu, Jul 04, 2019 at 09:11:33AM +1000, Dave Airlie wrote: > On Thu, 4 Jul 2019 at 07:32, Stephen Rothwell wrote: > > > > Hi Alex, > > > > On Wed, 3 Jul 2019 17:09:16 -0400 Alex Deucher > > wrote: > > > > > > Go ahead and respin your patch as per the suggestion above. then I > > > can apply i

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-04 Thread Jason Gunthorpe
On Wed, Jul 03, 2019 at 05:09:16PM -0400, Alex Deucher wrote: > On Wed, Jul 3, 2019 at 5:03 PM Kuehling, Felix wrote: > > > > On 2019-07-03 10:10 a.m., Jason Gunthorpe wrote: > > > On Wed, Jul 03, 2019 at 01:55:08AM +, Kuehling, Felix wrote: > > >> From: Philip Yang > > >> > > >> In order to

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-04 Thread Jason Gunthorpe
On Wed, Jul 03, 2019 at 01:55:08AM +, Kuehling, Felix wrote: > From: Philip Yang > > In order to pass mirror instead of mm to hmm_range_register, we need > pass bo instead of ttm to amdgpu_ttm_tt_get_user_pages because mirror > is part of amdgpu_mn structure, which is accessible from bo. > >

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-03 Thread Dave Airlie
On Thu, 4 Jul 2019 at 07:32, Stephen Rothwell wrote: > > Hi Alex, > > On Wed, 3 Jul 2019 17:09:16 -0400 Alex Deucher wrote: > > > > Go ahead and respin your patch as per the suggestion above. then I > > can apply it I can either merge hmm into amd's drm-next or we can just > > provide the confli

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-03 Thread Stephen Rothwell
Hi Felix, On Wed, 3 Jul 2019 21:03:32 + "Kuehling, Felix" wrote: > > It looks like Stephen already applied my patch as a conflict resolution > on linux-next, though. I see linux-next/master is getting updated > non-fast-forward. So is the idea that its history will updated again > with th

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-03 Thread Stephen Rothwell
Hi Alex, On Wed, 3 Jul 2019 17:09:16 -0400 Alex Deucher wrote: > > Go ahead and respin your patch as per the suggestion above. then I > can apply it I can either merge hmm into amd's drm-next or we can just > provide the conflict fix patch whichever is easier. Which hmm branch > is for 5.3? > h

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-03 Thread Alex Deucher
On Wed, Jul 3, 2019 at 5:03 PM Kuehling, Felix wrote: > > On 2019-07-03 10:10 a.m., Jason Gunthorpe wrote: > > On Wed, Jul 03, 2019 at 01:55:08AM +, Kuehling, Felix wrote: > >> From: Philip Yang > >> > >> In order to pass mirror instead of mm to hmm_range_register, we need > >> pass bo instea

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-03 Thread Kuehling, Felix
On 2019-07-03 10:10 a.m., Jason Gunthorpe wrote: > On Wed, Jul 03, 2019 at 01:55:08AM +, Kuehling, Felix wrote: >> From: Philip Yang >> >> In order to pass mirror instead of mm to hmm_range_register, we need >> pass bo instead of ttm to amdgpu_ttm_tt_get_user_pages because mirror >> is part of

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-03 Thread Stephen Rothwell
Hi all, On Wed, 3 Jul 2019 14:54:43 +1000 Stephen Rothwell wrote: > > On Wed, 3 Jul 2019 01:55:08 + "Kuehling, Felix" > wrote: > > > > From: Philip Yang > > > > In order to pass mirror instead of mm to hmm_range_register, we need > > pass bo instead of ttm to amdgpu_ttm_tt_get_user_pages

Re: [PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-02 Thread Stephen Rothwell
Hi all, On Wed, 3 Jul 2019 01:55:08 + "Kuehling, Felix" wrote: > > From: Philip Yang > > In order to pass mirror instead of mm to hmm_range_register, we need > pass bo instead of ttm to amdgpu_ttm_tt_get_user_pages because mirror > is part of amdgpu_mn structure, which is accessible from b

[PATCH 1/1] drm/amdgpu: adopt to hmm_range_register API change

2019-07-02 Thread Kuehling, Felix
From: Philip Yang In order to pass mirror instead of mm to hmm_range_register, we need pass bo instead of ttm to amdgpu_ttm_tt_get_user_pages because mirror is part of amdgpu_mn structure, which is accessible from bo. Signed-off-by: Philip Yang Reviewed-by: Felix Kuehling Signed-off-by: Felix