Announcement

Collapse
No announcement yet.

Radeon ROCm 3.5.1 Open-Source Compute Stack Released

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Radeon ROCm 3.5.1 Open-Source Compute Stack Released

    Phoronix: Radeon ROCm 3.5.1 Open-Source Compute Stack Released

    Two weeks after ROCm 3.5, the AMD Radeon team has now issued a patch update to this Radeon Open Compute stack...

    http://www.phoronix.com/scan.php?pag...eon-ROCm-3.5.1

  • #2
    Originally posted by phoronix View Post
    Phoronix: Radeon ROCm 3.5.1 Open-Source Compute Stack Released

    Two weeks after ROCm 3.5, the AMD Radeon team has now issued a patch update to this Radeon Open Compute stack...

    http://www.phoronix.com/scan.php?pag...eon-ROCm-3.5.1
    In relation to the "allegedly missing" Navi support, a snippet of text printed by rocminfo-3.5.0 on my machine:
    Code:
    $ rocminfo-3.5.0
    *******
    Agent 2
    *******
    Name: gfx1012
    Marketing Name: Navi 14 [Radeon RX 5500/5500M / Pro 5500M]
    And clinfo:
    Code:
    $ clinfo
    Platform Name AMD Accelerated Parallel Processing
    Number of devices 1
    Device Name gfx1012
    Device Vendor Advanced Micro Devices, Inc.
    Device Vendor ID 0x1002
    Device Version OpenCL 2.0
    Driver Version 3137.0 (HSA1.1,LC)
    Device OpenCL C Version OpenCL C 2.0
    Device Type GPU
    Device Board Name (AMD) Navi 14 [Radeon RX 5500/5500M / Pro 5500M]

    Comment


    • #3
      I'm not 100% sure, but AFAIK we have been using the ROCm back end for OpenCL on Navi+Linux from day one so even the packaged drivers contain fully functional lower level ROCm components including amdkfd, libhsakmt and the ROC runtime.

      What was missing was HIP/HCC and associated library support, but that would have been a bit of a throw-away because of the timing of the HIP/HCC to HIP/Clang transition.

      We don't really have anything to announce in the release notes re: Navi support until all of the components are ready.
      Last edited by bridgman; 06-20-2020, 03:19 PM.

      Comment


      • #4
        Has anyone tried ROCm on the new APUs? I was wondering if it can be used on the Ideapad 5 (4700U) that I ordered, or if unofficial builds are still required.

        Comment


        • #5
          Originally posted by halo9en View Post
          Has anyone tried ROCm on the new APUs? I was wondering if it can be used on the Ideapad 5 (4700U) that I ordered, or if unofficial builds are still required.
          ROCm for Ryzen APU is still unspported. Installing the dkms-rocm is a bad idea as it will trash the initrd. For OpenCL, amdpgu-pro is still a better option despite detecting the GPU part of Ryzen APU as unknown.
          The attached link for the unofficial builds is specific for Ubuntu. For Fedora users, no luck so far.

          Comment


          • #6
            I believe Renoir was the first shipping APU where we switched over to dGPU code paths, using GPUVM page tables rather than ATC/IOMMUv2. What I don't remember is whether we are using the ROCm back end for OpenCL in the packaged drivers.

            Don't remember if Michael tested the packaged drivers on his Renoir laptops (IIRC running clinfo would tell whether PAL or ROCm back end was being used) but will check.
            Last edited by bridgman; 06-21-2020, 02:42 PM.

            Comment


            • #7
              Does it really need PCIe atomics? This requirement leaves many old (and performant) machines out of ROCm.

              Comment


              • #8
                Originally posted by angrypie View Post
                Does it really need PCIe atomics? This requirement leaves many old (and performant) machines out of ROCm.
                Vega does not, Polaris and earlier do.

                Not sure about Navi but assume it needs them as well for now (ie unless you hear otherwise).

                Comment


                • #9
                  Originally posted by bridgman View Post
                  I believe Renoir was the first shipping APU where we switched over to dGPU code paths, using GPUVM page tables rather than ATC/IOMMUv2. What I don't remember is whether we are using the ROCm back end for OpenCL in the packaged drivers.
                  Will these changes get backport for the integrated GPU part of Raven Ridge like Ryzen 2500u?

                  Comment


                  • #10
                    Originally posted by bridgman View Post
                    I'm not 100% sure, but AFAIK we have been using the ROCm back end for OpenCL on Navi+Linux from day one so even the packaged drivers contain fully functional lower level ROCm components including amdkfd, libhsakmt and the ROC runtime.

                    What was missing was HIP/HCC and associated library support, but that would have been a bit of a throw-away because of the timing of the HIP/HCC to HIP/Clang transition.

                    We don't really have anything to announce in the release notes re: Navi support until all of the components are ready.
                    Could AMD just say OpenCL is working but HIP isn't? ROCm not supporting Navi is becoming a meme.

                    Comment

                    Working...
                    X