<@tflink:fedora.im>
16:33:15
!startmeeting fedora-ai-ml-sig
<@meetbot:fedora.im>
16:33:16
Meeting started at 2025-10-09 16:33:15 UTC
<@meetbot:fedora.im>
16:33:16
The Meeting name is 'fedora-ai-ml-sig'
<@tflink:fedora.im>
16:33:24
!topic hello and welcome
<@tflink:fedora.im>
16:33:26
!hi
<@zodbot:fedora.im>
16:33:26
Tim Flink (tflink)
<@dherrera:fedora.im>
16:33:38
!hi
<@zodbot:fedora.im>
16:33:39
Diego Herrera (dherrera) - he / him / his
<@gordonmessmer:fedora.im>
16:33:44
!hi
<@zodbot:fedora.im>
16:33:45
Gordon Messmer (gordonmessmer)
<@xanderlent:fedora.im>
16:34:02
!hi
<@zodbot:fedora.im>
16:34:02
Alexander Lent (xanderlent)
<@tflink:fedora.im>
16:34:44
welcome, everyone
<@tflink:fedora.im>
16:35:01
apologies for the late start, let's move on to the agenda
<@tflink:fedora.im>
16:35:08
#link https://board.net/p/fedora-aiml-sig-meeting-agenda
<@tflink:fedora.im>
16:35:23
#topic pytorch 2.9 looking for arm co-maintainer or dropping arm support
<@tflink:fedora.im>
16:35:32
bah, old habits
<@tflink:fedora.im>
16:35:39
!topic pytorch 2.9 looking for arm co-maintainer or dropping arm support
<@tflink:fedora.im>
16:35:51
Tom Rix: this one is yours
<@trix:fedora.im>
16:36:40
2.9 is coming this week. on list i expressed concern arm would not be tested _again_
<@trix:fedora.im>
16:37:10
but also requiring arm hw i don't believe most people would have.
<@trix:fedora.im>
16:37:58
i am working on pytorch_arches macro that will make it easy to drop arm.
<@trix:fedora.im>
16:38:10
anyone interested in arm enough ?
<@trix:fedora.im>
16:38:42
we do have while before f44 branches.
<@tflink:fedora.im>
16:39:43
to make sure I understand before making notes - you're looking for a pytorch comaintainer, specifically for the arm builds. If someone doesn't volunteer to handle the arm builds of pytorch by f44 branch time, you're planning to drop those builds?
<@trix:fedora.im>
16:40:34
i can keep the builds going as long as there isn't a serious problem with the build. atm i dependent on koji to do the build that isn't great.
<@trix:fedora.im>
16:41:42
building torch on a rpi or similar will be frustrating.
<@xanderlent:fedora.im>
16:41:51
FWIW scratch builds in Koji are a lot faster than mock+qemu (after trying to reproduce the build issue yesterday)
<@tflink:fedora.im>
16:42:13
Tom Rix: is available HW the issue or is your time/interest more of the issue?
<@trix:fedora.im>
16:42:20
both.
<@xanderlent:fedora.im>
16:42:25
But my problem is that all my arm hardware is slow, no Apple or Ampere access.
<@trix:fedora.im>
16:43:07
my day job is all x86-64 now, in the past it wasn't.
<@trix:fedora.im>
16:43:47
we can push off this topic if there are no taker. just warning folks.
<@tflink:fedora.im>
16:44:57
draft: current pytorch maintainer does not want to continue maintaining aarch64 builds of pytorch. Unless a co-maintainer for pytorch on arm steps up before f44 branch time, those arm builds will be dropped
<@tflink:fedora.im>
16:45:06
did I capture things well enough?
<@trix:fedora.im>
16:45:12
sounds good.
<@tflink:fedora.im>
16:45:22
!info current pytorch maintainer does not want to continue maintaining aarch64 builds of pytorch. Unless a co-maintainer for pytorch on arm steps up before f44 branch time, those arm builds will be dropped
<@tflink:fedora.im>
16:46:00
ok, it sounds like this topic is done, moving on if that's the case
<@trix:fedora.im>
16:46:31
in a slightly more positive question, if someone what's another torch backend and wants to do the work, i am up to help there too.
<@trix:fedora.im>
16:47:13
we can carry on.
<@tflink:fedora.im>
16:47:16
!topic ROCm 7 update
<@trix:fedora.im>
16:47:56
for the most part the stack is rebuild. the outlier is rocm-bandwidth-test, which is so broken its likely to stay borked for a while.
<@trix:fedora.im>
16:48:33
mostly i want to hear what other apps still need love.
<@trix:fedora.im>
16:48:55
torch and ollama still do.
<@tflink:fedora.im>
16:49:08
!info ROCm 7 update is mostly done in rawhide
<@tflink:fedora.im>
16:49:33
!info please let ROCm maintainers know if there are other apps that still need attention
<@tflink:fedora.im>
16:50:13
I assume that's all for that topic?
<@trix:fedora.im>
16:50:32
yes.
<@tflink:fedora.im>
16:50:56
cool, thanks for the update
<@tflink:fedora.im>
16:51:02
!topic PoCL 7.0 changes; pending PoCL 7.1 update
<@tflink:fedora.im>
16:51:09
Alexander Lent: this one is yours
<@xanderlent:fedora.im>
16:52:26
Thanks.
<@xanderlent:fedora.im>
16:53:27
I've tried to update PoCL to make sure that we're running the tests in Koji as well as align better with upstream (fixing the description, enabling arch-optimization on ppc64le, and building the compiler with GCC)
<@xanderlent:fedora.im>
16:54:08
I've got a few PRs to add various features, as well as to update to the latest 7.1 release against the repo, if anyone would like to take a look and provide feedback.
<@tflink:fedora.im>
16:56:50
!info There are PRs to update PoCL (implementation of OpenCL), run tests in koji and align more closely with upstream. Feedback on these updates is welcome
<@tflink:fedora.im>
16:56:59
<@xanderlent:fedora.im>
16:57:01
Specificall, the enhancements pending are
<@xanderlent:fedora.im>
16:57:01
- update to latest 7.1 -> this could use feedback due to a new bundled library
<@xanderlent:fedora.im>
16:57:01
- SPIR-V support in PoCL -> WIP
<@xanderlent:fedora.im>
16:57:01
- restore i686 support -> need to check if test fails are meaningful
<@xanderlent:fedora.im>
16:57:01
- add Level Zero backend (for Intel GPU/NPU) -> depends on SPIR-V, looks straightforward from there
<@xanderlent:fedora.im>
16:58:24
Thanks, that's all for now.
<@tflink:fedora.im>
16:59:26
thanks for the update
<@tflink:fedora.im>
16:59:53
that's all of the topics on the agenda for today, moving on to
<@tflink:fedora.im>
16:59:57
!topic open floor
<@tflink:fedora.im>
17:00:16
any other topics that folks want to bring up??
<@tflink:fedora.im>
17:03:11
I'm going to take silence as a "no" :)
<@tflink:fedora.im>
17:03:17
thanks for coming, everyone
<@tflink:fedora.im>
17:03:32
!endmeeting