Even i was wrong current APU on PC..
Now can we stop acting like HSA will be something that you turn on with a driver.?
tormentos
Refer to https://github.com/HSA-Libraries/Bolt
AMD APU Family with AMD Radeon HD Graphics
- A-Series
- C-Series
- E-Series
- E2-Series
- G-Series
- R-Series
AMD Radeon HD Graphics
- 7900 Series (7990, 7970, 7950)
- 7800 Series (7870, 7850)
- 7700 Series (7770, 7750)
AMD Radeon HD Graphics
- 6900 Series (6990, 6970, 6950)
- 6800 Series (6870, 6850)
- 6700 Series (6790 , 6770, 6750)
- 6600 Series (6670)
- 6500 Series (6570)
- 6400 Series (6450)
- 6xxxM Series
Notice only AMD DX11 hardware.
More info on AMD HSA Bolt library from http://www.slideshare.net/hsafoundation/bolt-for-hsa-by-ben-sanders
PS; Only AMD GCN's ISA fully supports HSAIL. The above AMD HSA Bolt library slides has mentioned CPU fallback mode.
----------
3rd party example with HSA ecosystem http://www.slideshare.net/hsafoundation/what-fabric-engine-can-do-with-hsa
AMD has given beta HSA driver software to certain developers.
--------------------------
http://fabricengine.com/2012/07/gpu_computation_technology_preview/
This 3rd party app running on beta HSA on Radeon HD 7800.
The AMD HSA technology platform has the goal of providing a heterogeneous computation platform in which both CPU and GPU cores access and manipulate memory identically. HSA will enable complex data structures with pointer indirection to be shared between the CPU and GPU. Not only will no copying of data between different memory spaces be necessary, but the pointers imbedded in a complex data structure will be usable without change on both CPU and GPU cores.
In collaboration with AMD, the Fabric Engine development team has extended the KL compiler and Fabric Engine Core execution environment to support GPU computation on high-end AMD GPUs. The primary means by which this preliminary work was possible was the availability of an LLVM back end for AMD GPU hardware.
The animated scene was run on a workstation with an AMD A10-5800K APU with both integrated graphics and a discrete Radeon HD 7800 card; however, only the discrete card was used for GPU computation and OpenGL rendering for these tests.
--------------------------------------------------------
Notice the concurrent HSA compute and OpenGL on discrete Radeon HD 7800. The devs didn't even bother using the IGP in AMD A10-5800K APU.
PS; No copying would be involved when the right work allocation was given to the right processor unit from the beginning or GDDR5 is treated like hUMA with PCI-E bus acting like PS4's CPU I/O bus.
With AMD HSA ecosystem,
1. The CPU can directly access GPU's memory address locations (located in GDDR5 physical space) i.e. PCI-E version 3.0 16 lane (32 GB/s full duplex) acts like "<20GB/s CPU I/O bus" in the PS4. Radeon HD 7800's GDDR5 acts like GDDR5 memory in PS4. Can be treated like a hUMA.
2. GPU can directly access CPU's memory address locations (located in DDR3 physical space) i.e. the reverse of the above process. The DX11.2 tiled resource/AMD PRT would be important to JIT load textures from the larger DDR3 memory pool.
Current AMD Gaming Evolved PC box can be configured to act like PS4. The main physical difference is the non-single chip solution with the PC i.e. the PC hardware is not cheap compared to PS4.
AMD Gaming Evolved PC box act like X1 and PS4.
Btw, AMD Trinity's PCI-E version 2.0 16 lane bus (16 GB/s full duplex) would be lower than "<20 GB/s CPU I/O bus" in PS4.
Radeon HD 7800 is acting like an APU with it's GDDR5 memory and it's connected to an external CPU (connected via PCI-E) i.e. AMD Piledriver dual module is too large to be glued with Radeon HD 7800.
---
http://hsafoundation.com/hsa-developer-tools/
"LLVM HSAIL Code Generator"
Log in to comment