amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/amdkfd: set prefetch GPU has access attribute
Date: Wed, 5 May 2021 16:01:56 -0400	[thread overview]
Message-ID: <2d145a22-a185-22d2-7ab2-a3ae06ccc97f@amd.com> (raw)
In-Reply-To: <20210505175617.30404-1-Philip.Yang@amd.com>

Am 2021-05-05 um 1:56 p.m. schrieb Philip Yang:
> After svm range prefetch and migrate to GPU, if GPU has no access or
> access in place attribute, add GPU to range access_bitmap to be able to
> update GPU page table.

I don't think we should change the bitmap_access, because this is
persistent and can be queried by user mode. Changing this would not be
expected by the application. I think instead we should either pass the
prefetch location to the gpuidx parameter of validate_and_map (we should
only do that is xnack is enabled), or change the logic in
validate_and_map to add the prefetch location to the bitmap.

I think to make this reliable we'll need to add more sanity checks to
prefetch to make sure the prefetch location is compatible with all GPUs
that have access_in_place. Otherwise we have to reject the prefetch.

Regards,
  Felix


>
> Signed-off-by: Philip Yang <Philip.Yang@amd.com>
> ---
>  drivers/gpu/drm/amd/amdkfd/kfd_svm.c | 11 +++++++++++
>  1 file changed, 11 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_svm.c b/drivers/gpu/drm/amd/amdkfd/kfd_svm.c
> index d9111fea724b..3b640772d9c5 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_svm.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_svm.c
> @@ -2869,6 +2869,17 @@ svm_range_set_attr(struct kfd_process *p, uint64_t start, uint64_t size,
>  			continue;
>  		}
>  
> +		if (migrated && prange->prefetch_loc) {
> +			int gpuidx;
> +
> +			gpuidx = kfd_process_gpuidx_from_gpuid(p,
> +							prange->prefetch_loc);
> +			if (gpuidx >= 0 &&
> +			    !test_bit(gpuidx, prange->bitmap_access) &&
> +			    !test_bit(gpuidx, prange->bitmap_aip))
> +				bitmap_set(prange->bitmap_access, gpuidx, 1);
> +		}
> +
>  		r = svm_range_validate_and_map(mm, prange, MAX_GPU_INSTANCE,
>  					       true, true);
>  		if (r)
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2021-05-05 20:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 17:56 [PATCH 1/2] drm/amdkfd: set prefetch GPU has access attribute Philip Yang
2021-05-05 17:56 ` [PATCH 2/2] drm/amdkfd: set new unregistered range accessible by GPU Philip Yang
2021-05-05 20:03   ` Felix Kuehling
2021-05-07 19:07   ` [PATCH 2/2] drm/amdkfd: unregistered range accessible by all GPUs Philip Yang
2021-05-10 12:56     ` Felix Kuehling
2021-05-11 15:14       ` philip yang
2021-05-11 15:15   ` [PATCH v2 2/2] drm/amdkfd: new " Philip Yang
2021-05-11 15:39     ` Felix Kuehling
2021-05-05 20:01 ` Felix Kuehling [this message]
2021-05-05 20:10   ` [PATCH 1/2] drm/amdkfd: set prefetch GPU has access attribute Felix Kuehling

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=2d145a22-a185-22d2-7ab2-a3ae06ccc97f@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    /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;
as well as URLs for NNTP newsgroup(s).