Jarkko Sakkinen

* v3: https://lore.kernel.org/linux-sgx/[email protected]/T/#t * Arch Linux packages: https://github.com/jarkkojs/aur-linux-sgx/actions/runs/2094138421 * Gave reviewed-by for https://lore.kernel.org/linux-sgx/[email protected]/T/#m80374894660b23d56ca1f1fa74bca99e1057a833.

I ended up acking about 80-90% of the patches.

v4 is out looking good.

E.g. ``` 2022-04-02T06:29:48.2149957Z syscall write = 16 2022-04-02T06:29:48.2150769Z syscall exit [src/backend/sgx/thread.rs:265] &syscall = Payload { ``` Improves the developer experience a lot.

@haraldh, @npmccallum: What do you think?

Maybe CI could produce a supplemental log with this post-processing? It does not take long, as long as long as `sys_clock_gettime` is filtered out.

After: ``` Finished test [unoptimized + debuginfo] target(s) in 0.23s Running tests/wasmldr_tests.rs (target/debug/deps/wasmldr_tests-e49c216cecd40c1f) running 1 test syscall mmap M 0x007f2ffffff000 0x00000000000548 = 0x7f2ffffff000 syscall arch_prctl = 0 syscall set_tid_address =...

@haraldh What do you think?

IMHO, there should be at least a feature to suppress also `clock_gettime`. I.e. optimal would be: ``` Compiling enarx v0.3.0 (/home/jarkko/Projects/enarx) Finished test [unoptimized + debuginfo] target(s) in 10.70s Running...

@npmccallum, @haraldh, @platten: Can we close this or not?