Re: [Nouveau] [PATCH] nouveau: fix the start/end range for migration

2020-08-31 Thread Ralph Campbell
On 8/31/20 11:02 AM, Jason Gunthorpe wrote: On Mon, Aug 31, 2020 at 10:21:41AM -0700, Ralph Campbell wrote: On 8/31/20 4:51 AM, Jason Gunthorpe wrote: On Thu, Aug 27, 2020 at 02:37:44PM -0700, Ralph Campbell wrote: The user level OpenCL code shouldn't have to align start and end addresses

Re: [Nouveau] [PATCH] nouveau: fix the start/end range for migration

2020-08-31 Thread Jason Gunthorpe
On Mon, Aug 31, 2020 at 10:21:41AM -0700, Ralph Campbell wrote: > > On 8/31/20 4:51 AM, Jason Gunthorpe wrote: > > On Thu, Aug 27, 2020 at 02:37:44PM -0700, Ralph Campbell wrote: > > > The user level OpenCL code shouldn't have to align start and end > > > addresses to a page boundary. That is

Re: [Nouveau] [PATCH] nouveau: fix the start/end range for migration

2020-08-31 Thread Ralph Campbell
On 8/31/20 4:51 AM, Jason Gunthorpe wrote: On Thu, Aug 27, 2020 at 02:37:44PM -0700, Ralph Campbell wrote: The user level OpenCL code shouldn't have to align start and end addresses to a page boundary. That is better handled in the nouveau driver. The npages field is also redundant since it

Re: [Nouveau] [PATCH] nouveau: fix the start/end range for migration

2020-08-31 Thread Jason Gunthorpe
On Thu, Aug 27, 2020 at 02:37:44PM -0700, Ralph Campbell wrote: > The user level OpenCL code shouldn't have to align start and end > addresses to a page boundary. That is better handled in the nouveau > driver. The npages field is also redundant since it can be computed > from the start and end

[Nouveau] [PATCH] nouveau: fix the start/end range for migration

2020-08-27 Thread Ralph Campbell
The user level OpenCL code shouldn't have to align start and end addresses to a page boundary. That is better handled in the nouveau driver. The npages field is also redundant since it can be computed from the start and end addresses. Signed-off-by: Ralph Campbell --- This is for Ben Skegg's