程序代写 SDK 64 bit from http://developer.amd.com/tools-

OS (H) Assessed Exercise: OpenCL Host Programming – Part II
The aim of this coursework is to create a simple host-side driver routine run driver() to interact with an OpenCL-compliant device (e.g. a GPU). This run driver() routine is called from a multithreaded testbench which will take care of initialisation and shutdown of the device, creation of the data to be sent to the device and validation of the returned result. Source code for such a testbench will be provided for the second part of the assignment.
2 What to submit
NOTE: In this section, the use of the words must or should means you will lose marks if you don’t do this.

Copyright By PowCoder代写 加微信 powcoder

For the second part of the assignment, you have to write the code for the run driver() based on the provided skeleton and the required OpenCL and POSIX pthread mutex API calls to protect the critical section. You are encouraged to read the relevant OpenCL API specification in detail.
• You must start from the provided code and you should only add your own code in driver.c, you must not modify or remove any part of the provided code.
• You must use the variable err for the error code for all API calls and report the error to stderr using fprintf.
• If you use printf statements in your code, they must be enclosed by an #ifdef VERBOSE … #endif guard.
• You must submit this code in a gzipped tar archive (other formats will not be ac- cepted) through the Moodle submission system, and the filename must be .tgz, so for example if your matric number is 1107023m then your archive must be named 1107023m.tgz. This archive must contain a single folder named . This folder must contain following files:

– driver.h as provided
– driver.c in which you must implement the functionality for the run driver
subroutine
– testbench.c as provided
– firmware.cl as provided
– Makefile as provided
3 What is provided
On Moodle you will find:
The official specification of the OpenCL API version 1.2
An archive opencl driver skeleton.tgz containing a the files listed above with a skeleton for run driver().
How to test your OpenCL code
There are three possible ways to test your OpenCL code:
1. Install OpenCL on your . For instructions on how to install OpenCL on your , see this tutorial.
2. Install OpenCL on your own machine. To install OpenCL locally, do the following:
• Download the AMD OpenCL SDK 64 bit from http://developer.amd.com/tools-
and-sdks/opencl-zone/amd-accelerated-parallel-processing-app-sdk/
• Unpack the archive
$ tar -jxf AMD-APP-SDKInstaller-v3.0.130.135-GA-linux64.tar.bz2
• Run the installer and choose the defaults
$ ./AMD-APP-SDK-v3.0.130.135-GA-linux64.sh
• Log out and log back in or open a new shell (the installer modifies your .bashrc)
• Now you can use the provided Makefile, testbench and driver code skeletons and
kernel source to build and test your OpenCL application.
3. Use the OpenCL pre-installed on the lab machines. The OpenCL SDK is available in /opt/intel/opencl.

Your code will be marked using a test script. This script will test if your code builds correctly and runs correctly for a number of use cases. I will not modify the testbench code but may run modified firmware and change the number of threads and the buffer size. The script will also perform source code analysis to see if you have used the correct API calls, control structures etc. There is one and only one correct order to execute all the API calls and the test script will heavily examine your use of error checks and handling of failures.
This part of the coursework is marked out of 60 (out of a total 70 for both parts), the marking scheme is as follows:
• Compilation 2/60
• Running and passing tests 8/60
• Code correctness 50/60, based on
– Correct use of pthread API calls 4/50
– Correct use of all required OpenCL API calls 28/50 – Correct order of all API calls 12/50
– Correct error handling 6/50
A penalty of two bands will apply if you use the wrong folder structure so make sure you generate the correctly compressed submission! I suggest compressing on a Linux machine as windows often add hidden folder structures.
Marks and feedback for Part 1 will be released on Moodle. Marks and feedback for Part 2 will be sent to you via email. A combined mark for Part 1 + Part 2 will become available on the SoCS Online (LTC) platform.

程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com