From: Lyude Paul <lyude@redhat.com>
To: Alistair Popple <apopple@nvidia.com>,
bskeggs@redhat.com, rcampbell@nvidia.com
Cc: kherbst@redhat.com, airlied@linux.ie, daniel@ffwll.ch,
nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, jhubbard@nvidia.com
Subject: Re: [PATCH] nouveau/svm: Fix to migrate all requested pages
Date: Thu, 28 Jul 2022 16:17:14 -0400 [thread overview]
Message-ID: <63f7fdefca924ac5d192a5f617ea41cf266ba756.camel@redhat.com> (raw)
In-Reply-To: <20220720062745.960701-1-apopple@nvidia.com>
hi, in the future if it's taking a while for a review to come back feel free
to just send a poke on the thread for the patch you submitted, I do my best to
keep up with all of the patches coming in. But there's a lot of email that I
get so every now and then one slips through the cracks.
Anyway, this patch looks good to me:
Reviewed-by: Lyude Paul <lyude@redhat.com>
I will push it to the appropriate branch in a little bit
On Wed, 2022-07-20 at 16:27 +1000, Alistair Popple wrote:
> Users may request that pages from an OpenCL SVM allocation be migrated
> to the GPU with clEnqueueSVMMigrateMem(). In Nouveau this will call into
> nouveau_dmem_migrate_vma() to do the migration. If the total range to be
> migrated exceeds SG_MAX_SINGLE_ALLOC the pages will be migrated in
> chunks of size SG_MAX_SINGLE_ALLOC. However a typo in updating the
> starting address means that only the first chunk will get migrated.
>
> Fix the calculation so that the entire range will get migrated if
> possible.
>
> Signed-off-by: Alistair Popple <apopple@nvidia.com>
> Fixes: e3d8b0890469 ("drm/nouveau/svm: map pages after migration")
> ---
> drivers/gpu/drm/nouveau/nouveau_dmem.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nouveau_dmem.c
> b/drivers/gpu/drm/nouveau/nouveau_dmem.c
> index 7ba66ad68a8a..16356611b5b9 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_dmem.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_dmem.c
> @@ -680,7 +680,11 @@ nouveau_dmem_migrate_vma(struct nouveau_drm *drm,
> goto out_free_dma;
>
> for (i = 0; i < npages; i += max) {
> - args.end = start + (max << PAGE_SHIFT);
> + if (args.start + (max << PAGE_SHIFT) > end)
> + args.end = end;
> + else
> + args.end = args.start + (max << PAGE_SHIFT);
> +
> ret = migrate_vma_setup(&args);
> if (ret)
> goto out_free_pfns;
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
prev parent reply other threads:[~2022-07-28 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 6:27 Alistair Popple
2022-07-28 19:27 ` Ralph Campbell
2022-07-28 20:17 ` Lyude Paul [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63f7fdefca924ac5d192a5f617ea41cf266ba756.camel@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@linux.ie \
--cc=apopple@nvidia.com \
--cc=bskeggs@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jhubbard@nvidia.com \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rcampbell@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®