This IRON design flow example, called "Passthrough Kernel", demonstrates a simple AIE implementation for a non-vectorized (scalar) memcpy on a vector of integers. In this design, a single AIE core performs the memcpy operation on a vector with a default length 4096. The kernel, defined in Python code as a function, is configured to work on 1024 element-sized subvectors and is invoked multiple times to complete the full copy. The example consists of a primary design file passthrough_pykernel.py and a testbench test.cpp or test.py.
-
passthrough_pykernel.py: A Python script that defines the AIE array structural design using MLIR-AIE operations. The file generates MLIR that is then compiled usingaieccto produce design binaries (ie. XCLBIN and inst.bin for the NPU in Ryzen™ AI). -
passthrough_pykernel_placed.py: A Python script that defines an alternative AIE array structural design using MLIR-AIE operations defined with a lower-level version of IRON than that used inpassthrough_pykernel.py. The file generates MLIR that is then compiled usingaieccto produce design binaries (ie. XCLBIN and inst.bin for the NPU in Ryzen™ AI). -
test.cpp: This C++ code is a testbench for the Passthrough Kernel design example. The code is responsible for loading the compiled XCLBIN file, configuring the AIE module, providing input data, and executing the AIE design on the NPU. After executing, the script verifies the memcpy results and optionally outputs trace data. -
test.py: This Python code is a testbench for the Passthrough Kernel design example. The code is responsible for loading the compiled XCLBIN file, configuring the AIE module, providing input data, and executing the AIE design on the NPU. After executing, the script verifies the memcpy results and optionally outputs trace data. -
passthrough_pykernel.ipynb: This notebook contains the design (which is duplicated frompassthrough_pykernel_placed.py) and test code (which is duplicated fromtest.py) for an alternative way of interacting with the example.
This simple example effectively passes data through a single compute tile in the NPU's AIE array. The design is described as shown in the figure to the right. The overall design flow is as follows:
- An object FIFO called "of_in" connects a Shim Tile to a Compute Tile, and another called "of_out" connects the Compute Tile back to the Shim Tile.
- The runtime data movement is expressed to read
4096uint8_t data from host memory to the compute tile and write the4096data back to host memory. - The compute tile acquires this input data in "object" sized (
1024) blocks from "of_in" and copies them to another output "object" it has acquired from "of_out". A scalar kernel defined via a Python function is invoked on the Compute Tile's AIE core to copy the data from the input "object" to the output "object". - After the copy is performed, the Compute Tile releases the "objects", allowing the DMAs (abstracted by the object FIFO) to transfer the data back to host memory and copy additional blocks into the Compute Tile, "of_out" and "of_in" respectively.
It is important to note that the Shim Tile and Compute Tile DMAs move data concurrently, and the Compute Tile's AIE Core also processes data concurrently with the data movement. This is made possible by expressing depth is 2 when constructing the ObjectFifo, for example, ObjectFifo(line_ty, depth=2) to denote ping-pong buffers. By default, the depth is 2 in recognition of this common pattern.
This design performs a memcpy operation on a vector of input data. The AIE design is described in a Python module as follows:
-
Constants & Configuration: The script defines input/output dimension (
N), buffer sizes inlineWidthInBytesandlineWidthInInt32s. -
AIE Device Definition:
@devicedefines the target device. Thedevice_bodyfunction contains the AIE array design definition. -
Kernel Function Declarations:
passThroughLineis a function defined in Python that performs a scalar copy of the data. -
Tile Definitions:
ShimTilehandles data movement, andComputeTile2processes the memcpy operations. -
Object Fifos:
of_inandof_outare defined to facilitate communication betweenShimTileandComputeTile2. -
Tracing Flow Setup (Optional): A circuit-switched flow is set up for tracing information when enabled.
-
Core Definition: The
core_bodyfunction loops through sub-vectors of the input data, acquiring elements fromof_in, processing usingpassThroughLine, and outputting the result toof_out. -
Data Movement Configuration: The
aie.runtime_sequenceoperation configures data movement and synchronization on theShimTilefor input and output buffer management. -
Tracing Configuration (Optional): Trace control, event groups, and buffer descriptors are set up in the
aie.runtime_sequenceoperation when tracing is enabled. -
Generate the design: The
passthroughKernel()function triggers the code generation process. The final print statement outputs the MLIR representation of the AIE array configuration.
To compile the design:
makeTo compile the placed design:
env use_placed=1 makeTo complete compiling the C++ testbench and run the design:
make runTo run the design:
make run_py- Start a jupyter server at the root directory of your clone of
mlir-aie. Make sure you use a terminal that has run theutils/setup_env.shscript so that the correct environment variables are percolated to jupyter. Below is an example of how to start a jupyter server:python3 -m jupyter notebook --no-browser --port=8080
- In your browser, navigate to the URL (which includes a token) which is found in the output of the above command.
- Navigate to
programming_examples/basic/passthrough_pykernel - Double click
passthrough_pykernel.ipynbto start the notebook; choose the ipykernel calledironenv. - You should now be good to go!
make clean_notebook
make run_notebook