Skip to content

Commit 4e8fea4

Browse files
committed
README: mention verif and how to generate an iset to use it
Signed-off-by: Matheus Tavares Bernardino <[email protected]>
1 parent 4caa5ce commit 4e8fea4

File tree

2 files changed

+16
-0
lines changed

2 files changed

+16
-0
lines changed

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,12 @@ A comprehensive collection of 60+ system-level tests for the Hexagon Standalone
6161

6262
HVX (Hexagon Vector eXtensions) example programs demonstrating vector processing capabilities.
6363

64+
### Verif QEMU Hexagon
65+
66+
"This is a quick-n-dirty project to demonstrate a way to compare execution
67+
between QEMU and ISS." The project is located inside the `verif-hexagon`
68+
directory, together with instructions on how to use it.
69+
6470
## Usage
6571

6672

verif-hexagon/README.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,20 @@ Inspired by research from Hyunsik Jeong at [KAIST](https://en.wikipedia.org/wiki
1212

1313
## Usage
1414

15+
First, you will need an `iset.py` file with the instruction semantics. By
16+
default, verif will use one from the `/prj` NFS path at Qualcomm machines. If
17+
you are not connected to Qualcomm network, though, you can use the synthetic
18+
`iset.py` that is generated as part of the QEMU-hexagon build at
19+
`<BUILDDIR>/target/hexagon/iset.py`.
20+
1521
For an extensive test, with default parameters, run:
1622

1723
./packet_verif verif
1824

25+
If you have a custom iset file, use:
26+
27+
./packet_verif verif --iset <ISET_PATH>
28+
1929
For more customization options, check:
2030

2131
./packet_verif verif --help

0 commit comments

Comments
 (0)