You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have question about enabling logging in the simulator.
I would like to boot into linux with instruction logging disabled, and only log for a test binary within the simulator. Is there any mechanism to support this?
My current plan is to hack spike to listen for some hint instructions to toggle logging, then I will wrap my test binary in a script which executes these hint instructions.
Thanks :)
The text was updated successfully, but these errors were encountered:
It can be quite challenging to isolate a user space program log within a Linux environment. This is because these programs share the same virtual address space. You cannot simply identify your target program by addresses. Even if you add a wrapper, your program may be interrupted and not executed continuously. As a result, your log will contain logs from the kernel and other processes, which means you may also need to hack the kernel. If your test case doesn't require complex syscalls, maybe you can use the proxy kernel from riscv-pk to simplify your environment.
Hello, I have question about enabling logging in the simulator.
I would like to boot into linux with instruction logging disabled, and only log for a test binary within the simulator. Is there any mechanism to support this?
My current plan is to hack spike to listen for some hint instructions to toggle logging, then I will wrap my test binary in a script which executes these hint instructions.
Thanks :)
The text was updated successfully, but these errors were encountered: