[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

AMD ROCm packaging session followup notes

Hi Debian AI Team,

I tried to gather the few notes following up on the meeting I
had with Cordell, and also added some complements of information
when typing in notes.  That was simply the two of us at the
meeting, so not sure things went according to the plan, but so
be it.  We formally covered three questions:

 Q: Where to find the source code as tarball?

 A: Most tools are duly git tagged, and source code is available
    on Github, so uscan(1) has documented ways to get us the
    latest versions easily.

    I did subsequent research and I think one source of
    confusion is that there seem to be distinct Github teams
    involved in the various ROCm components.  I gathered some
    components on RadeonOpenCompute [1], and some other such as
    the HIP compiler in ROCm-Developer-Tools [2].  There might
    be other locations, I didn't manage to locate rocclr for

    [1]: https://github.com/RadeonOpenCompute/
    [2]: https://github.com/ROCm-Developer-Tools/

 Q: In which order to build the different components?

 A: This is still not entirely clear, but trying to package
    targets will eventualy reveal dependency trees (hopefully
    without loops involved).

 Q: Where to put llvm related files?  (so it meets FHS [3])

 A: As changes brought to llvm-amdgpu are upstreamed, they make
    it to subsequent llvm versions, so making use of the latest
    upstream llvm/clang might actually be an option.

    [3]: https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html

The discussion then drifted on the level of support per
hardware, which is unfortunately quite uneven (I have an RX560,
and rocblas is non-functional at the moment, for instance).
Other cards such as Radeon VII have excellent support, but are
expansive and hard to procure.  Cordell also mentioned some
recent changes in the rocclr, in the build procedure IIUC.

In return I also tried to answer to Cordell's questions with
relations to our Debian's objective (make ROCm components one
`apt install` away of each Debian user, or provide alternate GPU
back ends to tensorflow, to take a more contextual issue), or
with relation to packaging the Debian way (e.g. from source
package, isolated and built by the means of pbuilder(8) or
sbuild(1); I'm afraid I only scratched the surface of the
packaging topic).

Repositories containing the work in progress for the packaging
or ROCm components on Debian side is available on Salsa [4].

[4]: https://salsa.debian.org/rocm-team/

Thanks Cordell for your time, don't hesitate to complement or
correct me; given the time of the day in my area at the moment
of the meeting, I might have overlooked some items.

Kind Regards,
Étienne Mollier <emollier@emlwks999.eu>
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/tty1, please excuse my verbosity.

Attachment: signature.asc
Description: PGP signature

Reply to: