Page MenuHomeFreeBSD

syscall: Create a script to export the data as json
ClosedPublic

Authored by imp on Apr 15 2026, 2:17 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jul 3, 3:09 PM
Unknown Object (File)
Fri, Jul 3, 3:09 PM
Unknown Object (File)
Thu, Jun 25, 6:47 PM
Unknown Object (File)
Jun 5 2026, 1:49 AM
Unknown Object (File)
Jun 4 2026, 2:29 AM
Unknown Object (File)
May 29 2026, 3:51 AM
Unknown Object (File)
May 27 2026, 10:22 PM
Unknown Object (File)
May 26 2026, 10:32 AM
Subscribers
None

Details

Summary

Create a script to export the parsed data as json. Include the
annotations for the system call arguments, since they are helpful to
downstream uses.

Sponsored by: Netflix

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 72224
Build 69107: arc lint + arc unit

Event Timeline

imp requested review of this revision.Apr 15 2026, 2:17 PM
imp created this revision.

on second thought, simplify a bit: always write to stdout.

brooks added inline comments.
sys/tools/syscalls/scripts/syscall_json.lua
8

Does it actually make sense of this to be a module? I guess it's harmless.

96–97

I find it a little odd to be providing both of these things in one file, but I don't have a feel for what makes "good" use of JSON.

This revision is now accepted and ready to land.Apr 16 2026, 8:18 AM
sys/tools/syscalls/scripts/syscall_json.lua
8

Oh, likely no.

96–97

I find it a little odd to be providing both of these things in one file, but I don't have a feel for what makes "good" use of JSON.

I'm unsure as well, but I'll see if I wind up needing it. after noticing this after the commit (I missed it before somehow) I got to thinking about it and maybe it's not needed. It can be inferred by looking at all the other syscalls. It only saves about 50 lines in the output.