GNU bug report logs - #55111
CONFIG_HSA_AMD unset in recent kernels

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 55111 in the body.
You can then email your comments to 55111 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: John Kehayias <john.kehayias <at> protonmail.com>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: CONFIG_HSA_AMD unset in recent kernels
Date: Mon, 25 Apr 2022 15:59:54 +0000

Hi Guix,

In trying to update AMD's OpenCL stuff (ROCm) in Guix to the latest version, I found that CONFIG_HSA_AMD is not set in our kernel config which I think might be needed (for HSA, most visibly having a /dev/kfd if I'm understanding). I see it was set to 'm' in previous versions, like 4.19, but at some point has been unset.

Does anyone know why this was changed or have any reason not to set it in our kernel config?

I've tried building the kernel with this configuration change and it went fine, but haven't been able to properly test it just yet.

John

Message #8 received at 55111 <at> debbugs.gnu.org (full text, mbox):

From: John Kehayias <john.kehayias <at> protonmail.com>
To: "55111 <at> debbugs.gnu.org" <55111 <at> debbugs.gnu.org>
Subject: Re: CONFIG_HSA_AMD unset in recent kernels
Date: Tue, 26 Apr 2022 17:07:34 +0000

I can confirm setting CONFIG_HSA_AMD=y (setting it to 'm' didn't seem to work for me) made /dev/kfd available and the OpenCL ROCm work, including making OpenCL available to Darktable. Note that I tested this on a non linux-libre kernel (what I use) which may or may not be required for OpenCL on some hardware. This is on x86-64.

Are there any objections to enabling this option in our kernel config?

Message #11 received at 55111 <at> debbugs.gnu.org (full text, mbox):

From: John Kehayias <john.kehayias <at> protonmail.com>
To: "55111 <at> debbugs.gnu.org" <55111 <at> debbugs.gnu.org>
Subject: Re: CONFIG_HSA_AMD unset in recent kernels
Date: Thu, 16 Jun 2022 16:02:12 +0000

Hello,

------- Original Message -------
On Tuesday, April 26th, 2022 at 1:07 PM, John Kehayias <john.kehayias <at> protonmail.com> wrote:
>
> I can confirm setting CONFIG_HSA_AMD=y (setting it to 'm' didn't seem to work for me) made /dev/kfd available and the OpenCL ROCm work, including making OpenCL available to Darktable. Note that I tested this on a non linux-libre kernel (what I use) which may or may not be required for OpenCL on some hardware. This is on x86-64.
>
> Are there any objections to enabling this option in our kernel config?

Now that ROCm has been updated in #55948, I tested again if I needed this kernel config change. Indeed, without CONFIG_HSA_AMD I do not get OpenCL with ROCm (darktable-cltest fails, as does rocminfo). I again set this configuration option and it works.

Any obstacles to (re)enabling this configuration option?

Thanks!
John

Message #16 received at 55111-done <at> debbugs.gnu.org (full text, mbox):

From: John Kehayias <john.kehayias <at> protonmail.com>
To: "55111-done <at> debbugs.gnu.org" <55111-done <at> debbugs.gnu.org>
Subject: Re: CONFIG_HSA_AMD unset in recent kernels
Date: Wed, 29 Jun 2022 19:54:49 +0000

Addressed in #56200, pushed by Leo as 44f2c7c2ca5d0a275c61d5bfd9dde1205590504b

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.