8000 riscv: implement decoding of riscv_hwprobe syscall by ziyao233 · Pull Request #321 · strace/strace · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

riscv: implement decoding of riscv_hwprobe syscall #321

New issue
8000

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ziyao233
Copy link
Contributor

This riscv-specific syscall was introduced by Linux kernel commits v6.4-rc188^211^2~4 for probing hardware capabilities

This riscv-specific syscall was introduced by Linux kernel commits
v6.4-rc1~88^2~11^2~4 for probing hardware capabilities.

Signed-off-by: Yao Zi <ziyao@disroot.org>
@ziyao233
Copy link
Contributor Author
ziyao233 commented Dec 5, 2024

Hi @ldv-alt, I pushed a new HEAD with test for the new syscall and tested it with

  • x86_64 Alpine Linux
  • riscv64 Arch Linux, kernel 6.11.2 (riscv_hwprobe introduced)
  • riscv64 Arch Linux, kernel 6.1.80 (riscv_hwprobe not introduced)

Here's an example of tracing output:

$ ./strace --trace=riscv_hwprobe ~/hwprobe_dump/hwprobe >/dev/null
riscv_hwprobe([{key=RISCV_HWPROBE_KEY_IMA_EXT_0}], 1, 0, NULL, 0 <unfinished ...>
<... riscv_hwprobe resumed>[{key=RISCV_HWPROBE_KEY_IMA_EXT_0, value=RISCV_HWPROBE_IMA_FD|RISCV_HWPROBE_IMA_C|RISCV_HWPROBE_EXT_ZBA|RISCV_HWPROBE_EXT_ZBB|RISCV_HWPROBE_EXT_ZCA|RISCV_HWPROBE_EXT_ZCD}], 1, 0, NULL, 0) = 0
riscv_hwprobe([{key=RISCV_HWPROBE_KEY_HIGHEST_VIRT_ADDRESS}], 1, 0, NULL, 0 <unfinished ...>
<... riscv_hwprobe resumed>[{key=RISCV_HWPROBE_KEY_HIGHEST_VIRT_ADDRESS, value=0x4000000000}], 1, 0, NULL, 0) = 0
+++ exited with 0 +++

Thanks for your time and review.

@ziyao233
Copy link
Contributor Author

@ldv-alt could we make some progress forward on this? It's 2025 now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0