Announcement

Collapse
No announcement yet.

AMD Publishes Open-Source Linux HSA Kernel Driver

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

  • #61
    A10-7800 has 3500 MHz base and 3900 MHz max turbo frequency at 65 Watts, that was published when it was introduced on 3dr July.




    As apposed to when A8-7600 was introduced in January, they decided to this time not communicate the speeds for the 45 Watt mode. Same for the desktop "Pro" models, some of which come at 65/45W and 65/35W TDP, with only the speds for the higher TDP having been communicated. Sadly. AMD marketing often is a little questionable. To say it the sugarsweet way.

    And almost nobody seems to have delivered those news. Even more sadly.
    Die AMD Produkt-Webseiten bieten seit der Computex umfangreiche Spezifikationen zu weiteren Modellen der Kaveri-Prozessorenserie für den Desktop-Einsatz. Bislang waren aus dem ursprünglich einmal genannten Portfolio nur die Modellen A10-7700K und

    Comment


    • #62
      So, will earlier AMD APU generations (Bobcat and whatnot) be able to make use of any of this? They probably don't have the Youmu, err, IOMMU to make full use of it, but maybe there could be some minor gains out of this anyway?

      Comment


      • #63
        HSA requires application update ??

        Will HSA provide benefits to the kernel itself ? In other words, if I use existing applications will I see any benefit ? Or is this an API, where applications must be modified to see _any_ benefit. I understand that if applications are modified they can take advantage of HSA. The question is, are kernel level operations helped, even without application modification.

        Comment


        • #64
          Not expecting benefits to the kernel directly -- the kernel driver exposes functionality to userspace that toolchains can call on to let apps more-or-less invisibly run faster. The app may or may not need to be rebuilt in order to take advantage of the new functionality depending on the JIT-iness of the language & APIs already in use. As examples, a C++ AMP app would need a rebuild while a OpenCL app would probably not.
          Test signature

          Comment


          • #65
            Originally posted by bridgman View Post
            .... As examples, a C++ AMP app would need a rebuild while a OpenCL app would probably not.
            So, once the HSA commits go into the kernel, x264 will use HSA through OpenCL?

            Comment


            • #66
              3.17?

              Comment


              • #67
                AMD APU generations always Rocks

                Comment


                • #68
                  Originally posted by seandarcy View Post
                  So, once the HSA commits go into the kernel, x264 will use HSA through OpenCL?
                  Yes, your x264 app would have to be OpenCL aware in the first place. It is the OpenCL primitives that calls the HSA abstraction driver to perform the hardware/software function. In terms of dedicating specific HSA cores, it could be manual or automatic. Either explicitly specified or defaulted. This is great progress for APU users of Linux.

                  Comment

                  Working...
                  X