mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: liu.song13@zte.com.cn
Cc: alexander.deucher@amd.com, christian.koenig@amd.com,
	airlied@gmail.com, simona@ffwll.ch,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, liu.xuemei1@zte.com.cn,
	jiang.xuexin@zte.com.cn, xue.zhihong@zte.com.cn
Subject: Re: [PATCH] drm/amdkfd: enable kfd on RISCV systems
Date: Mon, 28 Apr 2025 10:17:26 -0400	[thread overview]
Message-ID: <0b1e1a00-2cb9-4793-a439-06fcec3e71ec@amd.com> (raw)
In-Reply-To: <202504270413.53R4DUco001600@mse-db.zte.com.cn>

On 2025-04-26 21:25, liu.song13@zte.com.cn wrote:
> From: Xuemei Liu <liu.xuemei1@zte.com.cn>
>
> KFD has been confirmed that can run on RISCV systems. It's necessary to
> support CONFIG_HSA_AMD on RISCV.

Is there a public user mode branch with any changes needed to make ROCm 
user mode work with RISCV?

One more question inline.


> Signed-off-by: Xuemei Liu <liu.xuemei1@zte.com.cn>
> ---
>   drivers/gpu/drm/amd/amdkfd/Kconfig | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/Kconfig b/drivers/gpu/drm/amd/amdkfd/Kconfig
> index d3c3d3ab7225..9d4a5f8ef43f 100644
> --- a/drivers/gpu/drm/amd/amdkfd/Kconfig
> +++ b/drivers/gpu/drm/amd/amdkfd/Kconfig
> @@ -5,7 +5,7 @@
>
>   config HSA_AMD
>    bool "HSA kernel driver for AMD GPU devices"
> - depends on DRM_AMDGPU && (X86_64 || ARM64 || PPC64)
> + depends on DRM_AMDGPU && (X86_64 || ARM64 || PPC64 || RISCV)

The KFD memory model only works on 64-bit architectures. Is there a way 
to express that in the RISCV dependency?

Regards,
   Felix


>    select HMM_MIRROR
>    select MMU_NOTIFIER
>    select DRM_AMDGPU_USERPTR

  reply	other threads:[~2025-04-28 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-27  1:25 liu.song13
2025-04-28 14:17 ` Felix Kuehling [this message]
2025-04-29  9:29   ` liu.song13

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=0b1e1a00-2cb9-4793-a439-06fcec3e71ec@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jiang.xuexin@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liu.song13@zte.com.cn \
    --cc=liu.xuemei1@zte.com.cn \
    --cc=simona@ffwll.ch \
    --cc=xue.zhihong@zte.com.cn \
    /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®