xin/ysyx-workbench
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

> compile NEMU

Browse source 
ysyx_22040000 李心杨
Linux calcite 6.6.19 #1-NixOS SMP PREEMPT_DYNAMIC Fri Mar  1 12:35:11 UTC 2024 x86_64 GNU/Linux
 18:03:12  up   7:39,  2 users,  load average: 0.78, 0.67, 0.55
This commit is contained in:
tracer-ysyx 2024-03-13 18:03:12 +08:00 committed by xinyangli
parent 3a5bf0518a
commit 95aebe191e
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
nemu/Kconfig
View file

@ -164,7 +164,7 @@ config MTRACE
config MTRACE_RANGE config MTRACE_RANGE
depends on MTRACE depends on MTRACE
string "Memory trace active range" string "Memory trace active range"
default "0-fffffff" default "0-0xfffffff"
help help
Memory tracer will only print memory access in these ranges. Memory tracer will only print memory access in these ranges.
Use comma to seperate between ranges. Use comma to seperate between ranges.

2
nemu/src/memory/paddr.c
View file

@ -69,7 +69,7 @@ void init_mem() {
ptr = strtok_r(range, ",", &saveptr); ptr = strtok_r(range, ",", &saveptr);
for (range_count = 0; range_count < CONFIG_MTRACE_RANGE_MAX; ) { for (range_count = 0; range_count < CONFIG_MTRACE_RANGE_MAX; ) {
word_t start, end; word_t start, end;
Assert(sscanf(ptr, FMT_WORD "-" FMT_WORD, &start, &end) == 2, "Config option MTRACE_RANGE has wrong format"); Assert(sscanf(ptr, FMT_PADDR "-" FMT_PADDR, &start, &end) == 2, "Config option MTRACE_RANGE has wrong format");
mtrace_start[range_count] = start; mtrace_start[range_count] = start;
mtrace_end[range_count] = end; mtrace_end[range_count] = end;