Skip to content
Snippets Groups Projects
Commit e7098190 authored by Luis Gerhorst's avatar Luis Gerhorst
Browse files

Headings

parent 570c2000
No related branches found
No related tags found
No related merge requests found
...@@ -41,6 +41,8 @@ from user space, usually mounted in `/sys/kernel/debug/intsight`. INTspect uses ...@@ -41,6 +41,8 @@ from user space, usually mounted in `/sys/kernel/debug/intsight`. INTspect uses
this interface to communicate a given benchmark configuration to the kernel, this interface to communicate a given benchmark configuration to the kernel,
trigger its execution, and finally retrieve the generated data. trigger its execution, and finally retrieve the generated data.
### Documentation
The following table documents the virtual files created. When INTspect executes The following table documents the virtual files created. When INTspect executes
a benchmark, it creates a complete copy of this folder. The following a benchmark, it creates a complete copy of this folder. The following
description therefore also documents the structure of the result folders description therefore also documents the structure of the result folders
...@@ -63,6 +65,8 @@ produced by INTspect. ...@@ -63,6 +65,8 @@ produced by INTspect.
| vmalloc_checkpoint_matrix | Read-only Boolean | Determine whether the checkpoint buffer was small enough to be allocated using `kmalloc()`, or whether `vmalloc()` was required | | vmalloc_checkpoint_matrix | Read-only Boolean | Determine whether the checkpoint buffer was small enough to be allocated using `kmalloc()`, or whether `vmalloc()` was required |
| do_trigger_since_boot | Read-only Integer | Counts the number of benchmarks executed since booting the system | | do_trigger_since_boot | Read-only Integer | Counts the number of benchmarks executed since booting the system |
### Procedure
In general, the following procedure is followed when executing a benchmark: In general, the following procedure is followed when executing a benchmark:
1. Initialize INTsight by writing into `init`, this is only required once after 1. Initialize INTsight by writing into `init`, this is only required once after
...@@ -79,7 +83,7 @@ In general, the following procedure is followed when executing a benchmark: ...@@ -79,7 +83,7 @@ In general, the following procedure is followed when executing a benchmark:
parameters for the benchmark (the files used in step 2 can also be read out parameters for the benchmark (the files used in step 2 can also be read out
to reflect the current value). to reflect the current value).
### `csv_results` ### Results Format
For each timestamp enabled at compile time (see Kconfig option For each timestamp enabled at compile time (see Kconfig option
`INTSIGHT_TIMESTAMP_TYPE_*`), writing into `postprocess_trigger` creates a file `INTSIGHT_TIMESTAMP_TYPE_*`), writing into `postprocess_trigger` creates a file
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment