Page MenuHomeFreeBSD

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

Authored by imp on Wed, Apr 15, 2:17 PM.
Tags
None
Referenced Files
F156484926: D56408.id175569.diff
Thu, May 14, 12:30 AM
F156483741: D56408.id175568.diff
Thu, May 14, 12:08 AM
F156479288: D56408.id175568.diff
Wed, May 13, 11:05 PM
F156479201: D56408.id175568.diff
Wed, May 13, 11:04 PM
F156433709: D56408.id175736.diff
Wed, May 13, 4:38 PM
Unknown Object (File)
Mon, May 11, 2:31 PM
Unknown Object (File)
Mon, May 11, 5:21 AM
Unknown Object (File)
Sat, May 9, 8:37 PM
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 Not Applicable
Unit
Tests Not Applicable

Event Timeline

imp requested review of this revision.Wed, Apr 15, 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
9

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

97–98

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.Thu, Apr 16, 8:18 AM
sys/tools/syscalls/scripts/syscall_json.lua
9

Oh, likely no.

97–98

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.