AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lang Yu <Lang.Yu@amd.com>
To: Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdkfd: Insert missing TLB flush on GFX10 and later
Date: Tue, 12 Sep 2023 10:52:37 +0800	[thread overview]
Message-ID: <ZP/SdUd9am/f2WJw@lang-desktop> (raw)
In-Reply-To: <20230911190023.193702-1-Harish.Kasiviswanathan@amd.com>

On 09/11/ , Harish Kasiviswanathan wrote:
> Heavy-weight TLB flush is required after unmap on all GPUs for
> correctness and security.
> 
> Signed-off-by: Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>
> ---
>  drivers/gpu/drm/amd/amdkfd/kfd_priv.h | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_priv.h b/drivers/gpu/drm/amd/amdkfd/kfd_priv.h
> index b315311dfe2a..b9950074aee0 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_priv.h
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_priv.h
> @@ -1466,8 +1466,7 @@ void kfd_flush_tlb(struct kfd_process_device *pdd, enum TLB_FLUSH_TYPE type);
>  
>  static inline bool kfd_flush_tlb_after_unmap(struct kfd_dev *dev)
>  {
> -	return KFD_GC_VERSION(dev) == IP_VERSION(9, 4, 3) ||
> -	       KFD_GC_VERSION(dev) == IP_VERSION(9, 4, 2) ||
> +	return KFD_GC_VERSION(dev) > IP_VERSION(9, 4, 2) ||
>  	       (KFD_GC_VERSION(dev) == IP_VERSION(9, 4, 1) && dev->sdma_fw_version >= 18) ||
>  	       KFD_GC_VERSION(dev) == IP_VERSION(9, 4, 0);
>  }

1, If TLB_FLUSH_HEAVYWEIGHT is required after unmap on all GPUs
as described in commmit message, why we have this whitelist
instead of a blacklist?

2, kfd_flush_tlb(pdd, TLB_FLUSH_HEAVYWEIGHT) is also called
in svm_range_unmap_from_gpus(). Why not add this whitelist there?

Regards,
Lang

> -- 
> 2.34.1
> 

  parent reply	other threads:[~2023-09-12  2:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 19:00 [PATCH] drm/amdkfd: Insert missing TLB flush on GFX10 and later Harish Kasiviswanathan
2023-09-12  0:55 ` Felix Kuehling
2023-09-12  2:52 ` Lang Yu [this message]
2023-09-13  0:48   ` Felix Kuehling
2023-09-13 10:23     ` Lang Yu
2023-09-13 13:46       ` Felix Kuehling
2023-09-14  5:58         ` Lang Yu
2023-09-13  8:25 ` Christian König

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=ZP/SdUd9am/f2WJw@lang-desktop \
    --to=lang.yu@amd.com \
    --cc=Harish.Kasiviswanathan@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