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

Previous Next

Package: guix;

Reported by: John Kehayias <john.kehayias <at> protonmail.com>

Date: Mon, 25 Apr 2022 16:01:02 UTC

Severity: normal

Done: John Kehayias <john.kehayias <at> protonmail.com>

Bug is archived. No further changes may be made.

Full log


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




This bug report was last modified 2 years and 326 days ago.

Previous Next


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