Announcement

Collapse
No announcement yet.

It's Going To Take More Time To Get Vega Compute Support With The Mainline Kernel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    Wow, there's a whole lot of clueless people in this thread.

    Comment


    • #22
      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.
      I already git this insight info from this issue from ROCm project github, but thanks for double confirming this!
      Just a little question: when 18.10 is planned to be released to the public?

      Comment


      • #23
        Originally posted by duby229 View Post
        Wow, there's a whole lot of clueless people in this thread.
        This is not a helpful comment.

        Comment


        • #24
          Originally posted by schmidtbag View Post
          As 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.
          There 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.

          Comment


          • #25
            Originally posted by Meteorhead View Post
            There 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.
            I don't understand your comment - we have been supporting compute/graphics interop using KFD for a while in embedded engagements.

            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; 02-08-2018, 02:22 PM.

            Comment


            • #26
              Originally posted by uentity View Post
              Just a little question: when 18.10 is planned to be released to the public?
              Thought I already responded to this, sorry - some time around late March / early April.

              Comment

              Working...
              X