#UnitedHealthcare new fitness incentive program only allows me to put reward earnings into #Optum#HSA. Guess who owns Optum? That’s right! United Healthcare. Fee is $3.75 a month. $20 to transfer out or rollover.
OK so I'm ready for today's #GPGPU lesson with the new laptop. My only gripe for the lesson will be that #Rusticl in #Mesa 23.2 doesn't support #profiling information. Apparently the feature was merged at a later commit https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24101
and I even tried upgrading to my distro's experimental 23.3-rc1 packages, but trying to use rusticl on those packages segfaults. So either I've messed up something with this mixed upgrade, or I've hit an actual bug.
I'm still moderately annoyed by the fact that there's no single #OpenCL platform to drive all computer devices on this machine. #PoCL comes close because it supports both the CPU and the #NVIDIA dGPU through #CUDA, but the not the #AMD iGPU (there's an #HSA device, but). #Rusticl supports the iGP (radeonsi) and the CPU (llvmpipe), but not the dGPU (partly because I'm running that on proprietary drivers for CUDA). Everything else has at best one supported device out of three available.
So I actually tried to give the #HSA#PoCL driver a go, and while I didn't actually get support for my #AMD integrated #GPU (but it should be doable) I actually discovered something interesting, which I hadn't noticed since I didn't compare the clinfo output for my iGP between #Rusticl and the proprietary driver.
So here's the weird thing: they report a different number of compute units!
How did I come across all this? By going over the #HSA header files and noticing that the AMD extension to query device properties has recently introduced a new property, called “cooperative compute unit count” whose description reads:
> Some processors support more CUs than can reliably be used in a cooperative dispatch. This queries the count of CUs which are fully enabled for cooperative dispatch.