> As Oleg mentioned, I have a cleanup/reimplementation of seccomp using > utrace. That is quite a trivial use--it demonstrates how easy the > utrace API makes it to do things like that, in contrast to previous > solutions with arch-specific assembly hacking and so forth. I can > dust that patch off and post it if anybody cares.
Do you have an estimate or better numbers how the overhead of seccomp-over-utrace compares to the current in-tree seccomp? -Andi -- a...@linux.intel.com -- Speaking for myself only.
