DOCSLIB.ORG

AMD Codexl 1.2 GA Release Notes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

AMD CodeXL 1.2 GA Release Notes Thank you for using CodeXL. We appreciate any feedback you have! Please use our CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: CodeXL Visual Studio 2012 and 2010 packages and Standalone application, for 32-bit and 64-bit Windows platforms CodeXL for 64-bit Linux platforms Kernel Analyzer v2 for both Windows and Linux platforms Note about 32-bit Windows CodeXL 1.2 Upgrade Error On 32-bit Windows platforms, upgrading from CodeXL 1.0 using the CodeXL 1.2 installer will remove the previous version and then display an error message without installing CodeXL 1.2. The recommended method is to uninstall previous CodeXL before installing CodeXL 1.2. If you ran the 1.2 installer to upgrade a previous installation and encountered the error mentioned above, ignore the error and run the installer again to install CodeXL 1.2. Note about installing CodeAnalyst after installing CodeXL for Windows CodeXL can be safely installed on a Windows station where AMD CodeAnalyst is already installed. However, do not install CodeAnalyst on a Windows station already installed with CodeXL. Uninstall CodeXL first, and then install CodeAnalyst. System Requirements CodeXL contains a host of development features with varying system requirements: GPU Profiling and OpenCL Kernel Debugging o An AMD GPU (Radeon HD 5xxx or newer, desktop or mobile version) or APU is required o The AMD Catalyst Driver must be installed, release 13.6 Beta or later. Catalyst Beta 13.6 is the recommended version. See ‘Getting the latest Catalyst release’ section below. For GPU API-Level Debugging, a working OpenCL/OpenGL configuration is required (AMD or other). CPU Profiling o Time Based Profiling can be performed on any x86 or AMD64 (x86-64) CPU/APU. o The Event Based Profiling (EBP) and Instruction Based Sampling (IBS) session types require an AMD CPU or APU processor. Supported platforms: Windows platforms o Windows 7, 8 and 8.1, 32-bit and 64-bit o Visual Studio 2010/2012 must be installed on the station before the CodeXL Visual Studio 2010/2012 Package is installed, respectively. o If Visual Studio 2010 is not installed, the VC++ 2010 x86 Redistributable package must be installed for CPU Profiling Source View of .NET applications to work. Linux platforms o Red Hat EL 6 u2 64-bit o Ubuntu 12.04 64-bit Getting the latest Catalyst release The way to get the latest beta driver is to use the links ‘Latest Windows Beta Driver’ and ‘Latest Linux Beta Driver’ on the Graphics Drivers support page: http://support.amd.com/us/gpudownload/Pages/index.aspx New in this version The following items are new in this version: Support for Windows 8.1, 32 and 64 bit. The CPU Profiler has a number of improved capabilities including: o A new user interface design to help ease navigation and use of key features o Support for profiling of Java/.NET applications o Support for Time-Based Profiling on Intel Win8 platforms o Support for AMD’s recently announced Kabini APU public registers The Kernel Analyzer now has a new analysis module for Southern Islands devices that performs emulation of kernel workloads We’ve also updated the AMD CodeXL tutorial to help familiarize you with all of the above. A load of bug fixes. User experience enhancements: o CodeXL Explorer tree is rearranged to display CPU and GPU profile sessions view-specific details for easy navigation between session views. o CodeXL has a new icon! Fixed Issues The following fixes were not part of the 1.1 release and are new to this version: CPU Profiling is disabled on Windows 8 and Windows Server 2012 platforms running on non- AMD CPUs. (385105) Program crashes at clBuildProgram when compiling a IL program used in CodeXL on Windows 8- 32 bit (382266) – fixed in Catalyst 13.4 Locals not showing Local memory variables properly (332624) – fixed in Catalyst 13.6 GPU Debugger Locals view shows constant numeric value 0x0000 for local memory variables although viewing local memory variables is unsupported (332624) – fixed in Catalyst 13.4 In CPU Profiling sessions of type Time-Based Profiling, wrong call stack info displayed - wrong parents/children (359247) Segmentation Fault while closing CodeXL on Linux (366197) – fixed in Catalyst 13.6 "Failed to Profile" error on collecting GPU Profiling application trace for teapot sample (366962) Segmentation Fault on launching CodeXL on Linux using putty/xming (367512) – fixed in Catalyst 13.6 CPU Profiling Call Graph view shows invalid samples on Red Hat (368631) CPU Profiling "Pause" option is not working for the second running instance of CodeXL (370991) During GPU Profiling the TransferOverlapCPP sample stops working for Perf counter session (371119) CodeXL stops responding while importing large atp file on Windows 8 (376470) System hang while GPU profiling with navigation to source code option enabled on Linux (376736) – fixed in Catalyst 13.6 CPU Profiling using System-wide profile shows a lot of “Unknown module pid” (377779) On KDE platform, CodeXL "Help/View Quick Start guide/AMD CodeXL support forum" fails to open. (380998) On Linux KernelAnalyzer, ISA is not generated after building kernel for Hainan GPU (382074) – fixed in Catalyst 13.6 For some samples GPU debugging stops automatically after 2-3 runs (382541) Kernel Analyzer - Incomplete Oland ISA is generated after building kernel (382758) – fixed in Catalyst 13.6. Show particular hidden row is not working in GPU Profiling Performance Counters session (382831) Tooltip for ‘Profile’ toolbar button does not match the selected profile mode if no project loaded (383094) CPU Profiling "Start Profile" remains disabled after importing invalid PRD raw data file (383397) Locals & watch are not showing correct values of variables of type ‘double’ (383644) Same names are accepted for profile sessions after renaming (383695) KernelAnalyzer Command Line Interface shows junk values for ThreadsPerWorkGroup, ReqdWorkGroupX/Y/Z (384740) Intel Core i7 with Windows 8 64-bit halts system on installing CodeXL (384949) Step-in operations on a kernel with a struct variable may exhibit wrong line order (384976) – fixed in Catalyst 13.6. BSOD while performing Time-Based Profiling using the Teapot sample on Intel platform (385723) Project setting options for GPU profiling are automatically reset to default once profiling begins (385729) GPU Profiler stores wrong OS identification in recorded files for Windows 8 and Windows Server 2012 (385884) Statistics display of the number of wglShareLists & glGetBufferParameteriv API calls is wrong (386957) Core affinity not fully honored for system wide profile run (387042) "Quick start guide" is not installed as part of the Visual Studio extension if only Visual Studio 2010 is installed on the station (387933) Visual Studio 2010 shuts down during GPU Debugging after pressing F11 at clGetDeviceInfo API (388008) Known Issues When enabling the “Enable navigation to source code” option for a “GPU: Application Trace” profile on Linux, you may not be able to go to the source code of every API shown in the API trace table. The initial APIs in the table should allow navigation, but as you move further down through the trace table, you may notice that at some point the navigation to source code feature stops working. (404851) ‘Navigation to Source Code’ option is disabled for GPU Profiling Application Trace on Tahiti GPUs on Linux platforms (376736) – fixed in Catalyst 13.8 (future release) Debugging OpenCL kernels that use read-modify-write atomic operations is not supported. GPU Debugging on OpenCL Static C++ Kernels is not supported. (345852) __read_only and __write_only Image variables are not shown in locals during GPU Debugging. (345852) OpenCL 1.2 keyword printf is not supported during kernel debugging. Building kernels with OpenCL 1.2 clCreateProgramWithBinaries and clLinkProgram API prevents debugging these kernels. (369183) Running CpuProfiling with Call-Stack Sampling (CSS) enabled, on systems with discrete graphics card (5000, 6000, 7000 series), may result in Linux kernel panic. This kernel panic does not occur with Linux kernel version 3.2 onwards. CPU Profiling on Linux platforms – Limitations of PERF o CPU profiling uses PERF which requires kernel 2.6.32 or later. CPU Profiling with Call Stack Sampling requires Linux kernel 3.0 or later. However, we recommend using kernel 3.2 and above which has shown to be more stable. o Call chain analysis on Linux currently depends on the call chain information provided by Linux PERF. This requires the profiled binaries to have stack frame pointer. (i.e. compiled with -fno-omit-frame-pointer). o For non-root users to run CodeXL CPU profiling, “/proc/sys/kernel/perf_event_paranoid” needs to be set to “-1”. o Instruction-Based Profiling on Linux requires Linux kernel 3.5 and above, and must be used with system-wide profiling. o Call chain information (stack trace) for inline functions is not available. Call Stack data collection may result in kernel panic on Ubuntu with kernel version 3.0 or lower. Workaround: Upgrade the Ubuntu kernel to 3.2 or above. (352399) PERF call chain which contains call stack across modules has shown to be truncated. This results in inaccurate "Deep Samples", "Downstream Samples", and "call path" analysis. Importing a thread based session generated from CodeAnalyst sometimes results in CodeXL crash. (356479) if gDEBugger is installed, mouse click doesn’t start text fields editing in CodeXL Visual Studio Extension. Workaround: Navigate to the text fields using TAB. (344811) Menu items are present but not visible after a minimization of CodeXL in Ubuntu system using Unity. Workaround: Use Unity 2D instead of Unity. (353082) Teapot sample may exhibit crash while debugging OpenCL kernel after multiple step in operations (45 or more) and Info level log or lower.
Recommended publications
  • An Introduction to Analysis and Optimization with AMD Codeanalyst™ Performance Analyzer

    An Introduction to Analysis and Optimization with AMD Codeanalyst™ Performance Analyzer

    An introduction to analysis and optimization with AMD CodeAnalyst™ Performance Analyzer Paul J. Drongowski AMD CodeAnalyst Team Advanced Micro Devices, Inc. Boston Design Center 8 September 2008 Introduction This technical note demonstrates how to use the AMD CodeAnalyst™ Performance Analyzer to analyze and improve the performance of a compute-bound program. The program that we chose for this demonstration is an old classic: matrix multiplication. We'll start with a "textbook" implementation of matrix multiply that has well-known memory access issues. We will measure and analyze its performance using AMD CodeAnalyst. Then, we will improve the performance of the program by changing its memory access pattern. 1. AMD CodeAnalyst AMD CodeAnalyst is a suite of performance analysis tools for AMD processors. Versions of AMD CodeAnalyst are available for both Microsoft® Windows® and Linux®. AMD CodeAnalyst may be downloaded (free of charge) from AMD Developer Central. (Go to http://developer.amd.com and click on CPU Tools.) Although we will use AMD CodeAnalyst for Windows in this tech note, engineers and developers can use the same techniques to analyze programs on Linux. AMD CodeAnalyst performs system-wide profiling and supports the analysis of both user applications and kernel- mode software. It provides five main types of data collection and analysis: • Time-based profiling (TBP), • Event-based profiling (EBP), • Instruction-based sampling (IBS), • Pipeline simulation (Windows-only feature), and • Thread profiling (Windows-only feature). We will look at the first three kinds of analysis in this note. Performance analysis usually begins with time-based profiling to identify the program hot spots that are candidates for optimization.
  • Software Optimization Guide for Amd Family 15H Processors (.Pdf)

    Software Optimization Guide for Amd Family 15H Processors (.Pdf)

    Software Optimization Guide for AMD Family 15h Processors Publication No. Revision Date 47414 3.06 January 2012 Advanced Micro Devices © 2012 Advanced Micro Devices, Inc. All rights reserved. The contents of this document are provided in connection with Advanced Micro Devices, Inc. (“AMD”) products. AMD makes no representations or warranties with respect to the accuracy or completeness of the contents of this publication and reserves the right to make changes to specifications and product descriptions at any time without notice. The infor- mation contained herein may be of a preliminary or advance nature and is subject to change without notice. No license, whether express, implied, arising by estoppel or other- wise, to any intellectual property rights is granted by this publication. Except as set forth in AMD’s Standard Terms and Conditions of Sale, AMD assumes no liability whatsoever, and disclaims any express or implied warranty, relating to its products including, but not limited to, the implied warranty of merchantability, fitness for a particular purpose, or infringement of any intellectual property right. AMD’s products are not designed, intended, authorized or warranted for use as compo- nents in systems intended for surgical implant into the body, or in other applications intended to support or sustain life, or in any other application in which the failure of AMD’s product could create a situation where personal injury, death, or severe property or environmental damage may occur. AMD reserves the right to discontinue or make changes to its products at any time without notice. Trademarks AMD, the AMD Arrow logo, and combinations thereof, AMD Athlon, AMD Opteron, 3DNow!, AMD Virtualization and AMD-V are trademarks of Advanced Micro Devices, Inc.
  • Candidate Features for Future Opengl 5 / Direct3d 12 Hardware and Beyond 3 May 2014, Christophe Riccio

    Candidate Features for Future Opengl 5 / Direct3d 12 Hardware and Beyond 3 May 2014, Christophe Riccio

    Candidate features for future OpenGL 5 / Direct3D 12 hardware and beyond 3 May 2014, Christophe Riccio G-Truc Creation Table of contents TABLE OF CONTENTS 2 INTRODUCTION 4 1. DRAW SUBMISSION 6 1.1. GL_ARB_MULTI_DRAW_INDIRECT 6 1.2. GL_ARB_SHADER_DRAW_PARAMETERS 7 1.3. GL_ARB_INDIRECT_PARAMETERS 8 1.4. A SHADER CODE PATH PER DRAW IN A MULTI DRAW 8 1.5. SHADER INDEXED LOSE STATES 9 1.6. GL_NV_BINDLESS_MULTI_DRAW_INDIRECT 10 1.7. GL_AMD_INTERLEAVED_ELEMENTS 10 2. RESOURCES 11 2.1. GL_ARB_BINDLESS_TEXTURE 11 2.2. GL_NV_SHADER_BUFFER_LOAD AND GL_NV_SHADER_BUFFER_STORE 11 2.3. GL_ARB_SPARSE_TEXTURE 12 2.4. GL_AMD_SPARSE_TEXTURE 12 2.5. GL_AMD_SPARSE_TEXTURE_POOL 13 2.6. SEAMLESS TEXTURE STITCHING 13 2.7. 3D MEMORY LAYOUT FOR SPARSE 3D TEXTURES 13 2.8. SPARSE BUFFER 14 2.9. GL_KHR_TEXTURE_COMPRESSION_ASTC 14 2.10. GL_INTEL_MAP_TEXTURE 14 2.11. GL_ARB_SEAMLESS_CUBEMAP_PER_TEXTURE 15 2.12. DMA ENGINES 15 2.13. UNIFIED MEMORY 16 3. SHADER OPERATIONS 17 3.1. GL_ARB_SHADER_GROUP_VOTE 17 3.2. GL_NV_SHADER_THREAD_GROUP 17 3.3. GL_NV_SHADER_THREAD_SHUFFLE 17 3.4. GL_NV_SHADER_ATOMIC_FLOAT 18 3.5. GL_AMD_SHADER_ATOMIC_COUNTER_OPS 18 3.6. GL_ARB_COMPUTE_VARIABLE_GROUP_SIZE 18 3.7. MULTI COMPUTE DISPATCH 19 3.8. GL_NV_GPU_SHADER5 19 3.9. GL_AMD_GPU_SHADER_INT64 20 3.10. GL_AMD_GCN_SHADER 20 3.11. GL_NV_VERTEX_ATTRIB_INTEGER_64BIT 21 3.12. GL_AMD_ SHADER_TRINARY_MINMAX 21 4. FRAMEBUFFER 22 4.1. GL_AMD_SAMPLE_POSITIONS 22 4.2. GL_EXT_FRAMEBUFFER_MULTISAMPLE_BLIT_SCALED 22 4.3. GL_NV_MULTISAMPLE_COVERAGE AND GL_NV_FRAMEBUFFER_MULTISAMPLE_COVERAGE 22 4.4. GL_AMD_DEPTH_CLAMP_SEPARATE 22 5. BLENDING 23 5.1. GL_NV_TEXTURE_BARRIER 23 5.2. GL_EXT_SHADER_FRAMEBUFFER_FETCH (OPENGL ES) 23 5.3. GL_ARM_SHADER_FRAMEBUFFER_FETCH (OPENGL ES) 23 5.4. GL_ARM_SHADER_FRAMEBUFFER_FETCH_DEPTH_STENCIL (OPENGL ES) 23 5.5. GL_EXT_PIXEL_LOCAL_STORAGE (OPENGL ES) 24 5.6. TILE SHADING 25 5.7. GL_INTEL_FRAGMENT_SHADER_ORDERING 26 5.8. GL_KHR_BLEND_EQUATION_ADVANCED 26 5.9.
  • AMD Codexl 1.7 GA Release Notes

    AMD Codexl 1.7 GA Release Notes

    AMD CodeXL 1.7 GA Release Notes Thank you for using CodeXL. We appreciate any feedback you have! Please use the CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: For 64-bit Windows platforms o CodeXL Standalone application o CodeXL Microsoft® Visual Studio® 2010 extension o CodeXL Microsoft® Visual Studio® 2012 extension o CodeXL Microsoft® Visual Studio® 2013 extension o CodeXL Remote Agent For 64-bit Linux platforms o CodeXL Standalone application o CodeXL Remote Agent Note about installing CodeAnalyst after installing CodeXL for Windows AMD CodeAnalyst has reached End-of-Life status and has been replaced by AMD CodeXL. CodeXL installer will refuse to install on a Windows station where AMD CodeAnalyst is already installed. Nevertheless, if you would like to install CodeAnalyst, do not install it on a Windows station already installed with CodeXL. Uninstall CodeXL first, and then install CodeAnalyst. System Requirements CodeXL contains a host of development features with varying system requirements: GPU Profiling and OpenCL Kernel Debugging o An AMD GPU (Radeon HD 5000 series or newer, desktop or mobile version) or APU is required. o The AMD Catalyst Driver must be installed, release 13.11 or later. Catalyst 14.12 (driver 14.501) is the recommended version. See "Getting the latest Catalyst release" section below. For GPU API-Level Debugging, a working OpenCL/OpenGL configuration is required (AMD or other). CPU Profiling o Time-Based Profiling can be performed on any x86 or AMD64 (x86-64) CPU/APU.
  • Porting Source to Linux

    Porting Source to Linux

    Porting Source to Linux Valve’s Lessons Learned Overview . Who is this talk for? . Why port? . Windows->Linux . Linux Tools . Direct3D->OpenGL Why port? 100% Why port? Nov Dec Jan Feb . Linux is open 10% . Linux (for gaming) is growing, and quickly 1% . Stepping stone to mobile . Performance 0% . Steam for Linux Linux Mac Windows % December January February Windows 94.79 94.56 94.09 Mac 3.71 3.56 3.07 Linux 0.79 1.12 2.01 Why port? – cont’d . GL exposes functionality by hardware capability—not OS. China tends to have equivalent GPUs, but overwhelmingly still runs XP — OpenGL can allow DX10/DX11 (and beyond) features for all of those users Why port? – cont’d . Specifications are public. GL is owned by committee, membership is available to anyone with interest (and some, but not a lot, of $). GL can be extended quickly, starting with a single vendor. GL is extremely powerful Windows->Linux Windowing issues . Consider SDL! . Handles all cross-platform windowing issues, including on mobile OSes. Tight C implementation—everything you need, nothing you don’t. Used for all Valve ports, and Linux Steam http://www.libsdl.org/ Filesystem issues . Linux filesystems are case-sensitive . Windows is not . Not a big issue for deployment (because everyone ships packs of some sort) . But an issue during development, with loose files . Solution 1: Slam all assets to lower case, including directories, then tolower all file lookups (only adjust below root) . Solution 2: Build file cache, look for similarly named files Other issues . Bad Defines — E.g. Assuming that LINUX meant DEDICATED_SERVER .
  • AMD Codexl 1.8 GA Release Notes

    AMD Codexl 1.8 GA Release Notes

    AMD CodeXL 1.8 GA Release Notes Contents AMD CodeXL 1.8 GA Release Notes ......................................................................................................... 1 New in this version .............................................................................................................................. 2 System Requirements .......................................................................................................................... 2 Getting the latest Catalyst release ....................................................................................................... 4 Note about installing CodeAnalyst after installing CodeXL for Windows ............................................... 4 Fixed Issues ......................................................................................................................................... 4 Known Issues ....................................................................................................................................... 5 Support ............................................................................................................................................... 6 Thank you for using CodeXL. We appreciate any feedback you have! Please use the CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: For 64-bit Windows platforms o CodeXL Standalone application o CodeXL Microsoft® Visual Studio®
  • Masterarbeit / Master's Thesis

    Masterarbeit / Master's Thesis

    MASTERARBEIT / MASTER'S THESIS Titel der Masterarbeit / Title of the Master`s Thesis "Reducing CPU overhead for increased real time rendering performance" verfasst von / submitted by Daniel Martinek BSc angestrebter Akademischer Grad / in partial fulfilment of the requirements for the degree of Diplom-Ingenieur (Dipl.-Ing.) Wien, 2016 / Vienna 2016 Studienkennzahl lt. Studienblatt / A 066 935 degree programme code as it appears on the student record sheet: Studienrichtung lt. Studienblatt / Masterstudium Medieninformatik UG2002 degree programme as it appears on the student record sheet: Betreut von / Supervisor: Univ.-Prof. Dipl.-Ing. Dr. Helmut Hlavacs Contents 1 Introduction 1 1.1 Motivation . .1 1.2 Outline . .2 2 Introduction to real-time rendering 3 2.1 Using a graphics API . .3 2.2 API future . .6 3 Related Work 9 3.1 nVidia Bindless OpenGL Extensions . .9 3.2 Introducing the Programmable Vertex Pulling Rendering Pipeline . 10 3.3 Improving Performance by Reducing Calls to the Driver . 11 4 Libraries and Utilities 13 4.1 SDL . 13 4.2 glm . 13 4.3 ImGui . 14 4.4 STB . 15 4.5 Assimp . 16 4.6 RapidJSON . 16 4.7 DirectXTex . 16 5 Engine Architecture 17 5.1 breach . 17 5.2 graphics . 19 5.3 profiling . 19 5.4 input . 20 5.5 filesystem . 21 5.6 gui . 21 5.7 resources . 21 5.8 world . 22 5.9 rendering . 23 5.10 rendering2d . 23 6 Resource Conditioning 25 6.1 Materials . 26 i 6.2 Geometry . 27 6.3 World Data . 28 6.4 Textures . 29 7 Resource Management 31 7.1 Meshes .
  • Getting Started with Codexl the Analysis Tab

    Getting Started with Codexl the Analysis Tab

    AMD CodeXL Quick Start Guide AMD Developer Tools Team Advanced Micro Devices, Inc. Version 1.5 Revision 1 Table of Contents INTRODUCTION .................................................................................................................... 3 LATEST VERSION OF THIS DOCUMENT .......................................................................... 3 PREREQUISITES ................................................................................................................... 3 DOWNLOAD AND INSTALL CODEXL ................................................................................ 4 Validate Installation .......................................................................................................................... 5 Installing the VC++ Redistributable Package...................................................................................... 7 CODEXL HELP ........................................................................................................................ 7 SYSTEM INFORMATION ...................................................................................................... 8 TEAPOT SAMPLE PROJECT .............................................................................................. 10 Debug the Teapot Sample Application ............................................................................................ 11 Basic Debugging .............................................................................................................................. 12 Source Code View
  • Codexl 2.6 GA Release Notes

    Codexl 2.6 GA Release Notes

    CodeXL 2.6 GA Release Notes Contents CodeXL 2.6 GA Release Notes ....................................................................................................................... 1 New in this version .................................................................................................................................... 2 System Requirements ............................................................................................................................... 2 Getting the latest Radeon™ Software release .......................................................................................... 3 Radeon software packages can be found here: .................................................................................... 3 Fixed Issues ............................................................................................................................................... 3 Known Issues ............................................................................................................................................. 4 Support ..................................................................................................................................................... 5 Thank you for using CodeXL. We appreciate any feedback you have! Please use the CodeXL Issues Page to provide your feedback. You can also check out the Getting Started guide and the latest CodeXL blog at GPUOpen.com This version contains: • For 64-bit Windows® platforms o CodeXL Standalone application o CodeXL Remote Agent
  • Heterogeneous System Architecture Pdf

    Heterogeneous System Architecture Pdf

    Heterogeneous system architecture pdf Continue The Heterogeneous System Architecture (HSA) is a cross-supplier set of specifications that allow for the integration of central processing processors and GPUs on the same bus, with shared memory and tasks. HSA is developed by the HSA Foundation, which includes (among many others) AMD and ARM. The stated goal of the platform is to reduce the delay in communication between processors, GPUs, and other computing devices and to make these different devices more compatible from the programmer's point of view, freeing the programmer from the task of scheduling the movement of data between disparate device memories (as should be done now with OpenCL or CUDA). CUDA and OpenCL, as well as most other fairly advanced programming languages, can use HSA to improve performance. Heterogeneous computing is widely used in chip system devices such as tablets, smartphones, other mobile devices, and game consoles. HSA allows programs to use a GPU to calculate floating currents without separate memory or planning. The rationale behind the HSA is to ease the burden on programmers when unloading calculations in the GPU. Originally driven exclusively by AMD and called the FSA, the idea has been expanded to cover processors other than GPUs such as other manufacturers' DSPs as well. Steps performed when unloading calculations in THED on non-HSA system steps performed when unloading calculations in the GPU on the HSA system, using HSA functionality, Modern GPUs are very well suited to one instruction, multiple data (SIMD) and one manual, multiple threads (SIMT), while modern processors are still optimized for branching.
  • Mellanox Corporate Deck

    Mellanox Corporate Deck

    UCX Community Meeting SC’19 November 2019 Open Meeting Forum and Publicly Available Work Product This is an open, public standards setting discussion and development meeting of UCF. The discussions that take place during this meeting are intended to be open to the general public and all work product derived from this meeting shall be made widely and freely available to the public. All information including exchange of technical information shall take place during open sessions of this meeting and UCF will not sponsor or support any closed or private working group, standards setting or development sessions that may take place during this meeting. Your participation in any non-public interactions or settings during this meeting are outside the scope of UCF's intended open-public meeting format. © 2019 UCF Consortium 2 UCF Consortium . Mission: • Collaboration between industry, laboratories, and academia to create production grade communication frameworks and open standards for data centric and high-performance applications . Projects https://www.ucfconsortium.org Join • UCX – Unified Communication X – www.openucx.org [email protected] • SparkUCX – www.sparkucx.org • Open RDMA . Board members • Jeff Kuehn, UCF Chairman (Los Alamos National Laboratory) • Gilad Shainer, UCF President (Mellanox Technologies) • Pavel Shamis, UCF treasurer (Arm) • Brad Benton, Board Member (AMD) • Duncan Poole, Board Member (Nvidia) • Pavan Balaji, Board Member (Argonne National Laboratory) • Sameh Sharkawi, Board Member (IBM) • Dhabaleswar K. (DK) Panda, Board Member (Ohio State University) • Steve Poole, Board Member (Open Source Software Solutions) © 2019 UCF Consortium 3 UCX History https://www.hpcwire.com/2018/09/17/ucf-ucx-and-a-car-ride-on-the-road-to-exascale/ © 2019 UCF Consortium 4 © 2019 UCF Consortium 5 UCX Portability .
  • Readthedocs-Breathe Documentation Release 1.0.0

    Readthedocs-Breathe Documentation Release 1.0.0

    ReadTheDocs-Breathe Documentation Release 1.0.0 Thomas Edvalson Feb 06, 2019 Contents 1 Going to 11: Amping Up the Programming-Language Run-Time Foundation3 2 Solid Compilation Foundation and Language Support5 2.1 Quick Start Guide............................................5 2.1.1 Current Release Notes.....................................5 2.1.2 Installation Guide........................................5 2.1.3 Programming Guide......................................6 2.1.4 ROCm GPU Tunning Guides..................................7 2.1.5 GCN ISA Manuals.......................................7 2.1.6 ROCm API References.....................................7 2.1.7 ROCm Tools..........................................8 2.1.8 ROCm Libraries........................................9 2.1.9 ROCm Compiler SDK..................................... 10 2.1.10 ROCm System Management.................................. 10 2.1.11 ROCm Virtualization & Containers.............................. 10 2.1.12 Remote Device Programming................................. 11 2.1.13 Deep Learning on ROCm.................................... 11 2.1.14 System Level Debug...................................... 11 2.1.15 Tutorial............................................. 11 2.1.16 ROCm Glossary......................................... 12 2.2 Current Release Notes.......................................... 12 2.2.1 New features and enhancements in ROCm 2.1......................... 12 2.2.1.1 RocTracer v1.0 preview release – ‘rocprof’ HSA runtime tracing and statistics sup- port