Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in README.md #1

Open
wants to merge 2 commits into
base: public
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,14 @@ KERNEL_CONF ?= defconfig

# specific for Linux
# leave at least one core free
NCORES = $(shell echo $$((`grep -c ^processor /proc/cpuinfo`-2)))
# Determine the number of cores
ifeq ($(shell uname), Linux)
NCORES = $(shell echo $$((`grep -c ^processor /proc/cpuinfo` - 2)))
else ifeq ($(shell uname), Darwin)
NCORES = $(shell sysctl -n hw.physicalcpu | awk '{print $1 - 1}')
else
NCORES = 4 # Default to 4 cores if OS is not detected
endif
NRUNS = $(shell seq 0 $(NCORES))

# for running two campaigns at once with the same number of cores
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ Here, we provide a quick overview of the most interesting targets.
For further documentation about parameters look into the Makefile.
EL3XIR is designed to be extended with other secure monitor binaries.
If trying to fuzz a new secure monitor with EL3XIR the following steps are required:
* Implement rehosting environment: This includes a bootloader stub, secure world stub, normal world stup, and handling of hardware interactions.
* Implement rehosting environment: This includes a bootloader stub, secure world stub, normal world stub, and handling of hardware interactions.
You may look into `../secmonRehosting/rehostingEnvironments/` to find examples.
Section 4.1 of our paper explains a high-level systematic process for rehosting secure monitor binaries.
We note that our rehosting environments are directly dependent on the exact binary, i.e., if you use a new binary you need to adjust breakpoint locations.
Expand Down Expand Up @@ -169,4 +169,4 @@ The following output files should be found when successful:
| Path | Description |
| :--- | :--- |
| `/out/$TARGET/mmio-logs-$HARNESS-$MMIO_FUZZ.log` | Combined logging of all rerun test cases with MMIO read logging. You may search for `MMIO fuzz read` to find entries manually. |
| `/out/$TARGET/mmio-summary-$TARGET-$HARNESS-$MMIO_FUZZ.txt` | Summary of modeled MMIO registers, values, and affected runtime services. |
| `/out/$TARGET/mmio-summary-$TARGET-$HARNESS-$MMIO_FUZZ.txt` | Summary of modeled MMIO registers, values, and affected runtime services. |