Wow, there's a whole lot of clueless people in this thread.
Announcement
Collapse
No announcement yet.
It's Going To Take More Time To Get Vega Compute Support With The Mainline Kernel
Collapse
X
-
Originally posted by bridgman View Post
We are working on a separate solution for OpenCL without PCIE atomics - with a bit of luck it will hit the next (18.10) release.
Just a little question: when 18.10 is planned to be released to the public?
Comment
-
Originally posted by schmidtbag View PostAs far as I'm aware, having a "uniform place" would not improve anything. If anything, it would slow down development, since you have to consider regressions and following a single release schedule rather than multiple independent ones.
Having a uniform hook, as is the case on Windows with WDDM, it is much easier to issue drivers that can do both. Perhaps bridgman can shed some light onto this case.
Comment
-
Originally posted by Meteorhead View PostThere must be some misunderstanding here. The fact that there is DRM and AMDKFD, one kernel hook that the Mesa drivers use and another that AMD uses solely for compute workloads immediately means that having graphics-compute interop is going to be a no go on AMD hardware in the near future, when all remnants of fglrx (inside AMDGPU-PRO) have been rooted out.
Having a uniform hook, as is the case on Windows with WDDM, it is much easier to issue drivers that can do both. Perhaps bridgman can shed some light onto this case.
Graphics and HSA/ROC/KFD compute use different addressing models anyways. CPU and GPU address spaces are distinct for graphics (and for compute running over amdgpu) but common for KFD compute so you need an API call to map from one to the other, but that's not a problem.Last edited by bridgman; 08 February 2018, 02:22 PM.Test signature
Comment
Comment