Page MenuHomeFreeBSD

riscv: improve KTR_TRAP trace entries
ClosedPublic

Authored by mhorne on Jun 17 2023, 4:59 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Dec 15, 11:45 PM
Unknown Object (File)
Nov 22 2025, 2:23 PM
Unknown Object (File)
Nov 12 2025, 10:02 AM
Unknown Object (File)
Nov 11 2025, 10:40 PM
Unknown Object (File)
Nov 11 2025, 5:49 PM
Unknown Object (File)
Nov 4 2025, 4:35 AM
Unknown Object (File)
Oct 30 2025, 3:15 AM
Unknown Object (File)
Oct 30 2025, 2:34 AM
Subscribers

Details

Summary

For more informative records of exceptions, include key details such as
the exception code and stval contents. Add a new KTR_TRAP trace record
for interrupts.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 52137
Build 49028: arc lint + arc unit

Event Timeline

sys/riscv/riscv/intr_machdep.c
167

KTR entries always contain a pointer to curthread (used to implement ktrdump -H), so including it here is redundant.

I wonder if the pointer to frame is ever useful?

sys/riscv/riscv/intr_machdep.c
167

Good point on curthread. For frame, probably not. It has a short lifetime and it's not like we can do much with it in ddb.

Drop curthread and trapframe arguments.

This revision is now accepted and ready to land.Jun 19 2023, 3:58 PM
This revision was automatically updated to reflect the committed changes.