Page MenuHomeFreeBSD

dtrace: handle NOP instructions in RISC-V
ClosedPublic

Authored by christos on Apr 10 2023, 12:38 PM.
Tags
Referenced Files
Unknown Object (File)
Tue, Nov 18, 2:17 PM
Unknown Object (File)
Sat, Nov 15, 7:37 AM
Unknown Object (File)
Nov 5 2025, 4:15 AM
Unknown Object (File)
Oct 26 2025, 10:56 PM
Unknown Object (File)
Oct 23 2025, 9:00 PM
Unknown Object (File)
Oct 20 2025, 7:45 PM
Unknown Object (File)
Oct 17 2025, 3:43 AM
Unknown Object (File)
Oct 14 2025, 7:03 PM
Subscribers

Details

Summary

dtrace_invop_start() was panicking if the provider returned
MATCH_C_NOP (DTRACE_INVOP_NOP).

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

sys/cddl/dev/dtrace/riscv/dtrace_subr.c
275

It looks like fbt_invop() returns the original instruction, rather than using the DTRACE_INVOP_* constants. In particular, fbt->fbt_rval is not used anywhere.

We should thus return a nop instruction and match it the way other instructions are matched, rather than having multiple return types.

christos marked an inline comment as done.
christos retitled this revision from dtrace: handle DTRACE_INVOP_NOP in RISC-V to dtrace: handle NOP instructions in RISC-V.
christos edited the summary of this revision. (Show Details)
This revision is now accepted and ready to land.Apr 10 2023, 3:03 PM