Let's separate out OpenCL from HCC/HIP and the rest of the ROCm stack. We are working on a solution to deliver OpenCL without requiring atomics, but not the rest of the ROCm stack. >-----Original Message----- >From: amd-gfx [mailto:amd-gfx-bounces at lists.freedesktop.org] On Behalf Of >Luke A. Guest >Sent: Monday, December 25, 2017 9:55 AM >To: amd-gfx at lists.freedesktop.org >Subject: Re: PCIe3 atomics requirement for amdkfd > >Hi, > >I have to agree here. At least there should be a non-PCIe-3.0 pathway which >implements them on the CPU, I mean, they're fairly simple atomics, CAS, >SWAP, FetchAdd. > >What AMD have actually done is royally screwed over anyone with an FX >chipset, i.e. no OpenCL - the open source AMD one requires ROCm, they >abandoned Clover, maybe PoCL will work? Who knows. > > >On 19/12/17 15:04, Tom Stellard wrote: >> Hi, >> >> How hard of a requirement is PCIe3 atomics for dGPUs with the amdkfd >> kernel driver? Is it possible to make modifications to the >> runtime/kernel driver to drop this requirement? >> >> -Tom >> _______________________________________________ >> amd-gfx mailing list >> amd-gfx at lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/amd-gfx > >_______________________________________________ >amd-gfx mailing list >amd-gfx at lists.freedesktop.org >https://lists.freedesktop.org/mailman/listinfo/amd-gfx
