Bug#474648: please re-enable CONFIG_SECCOMP, it's harmless (and needed)
CONFIG_SECCOMP was disabled for performance reasons, but it has always
been harmless. Quoting the author:
| On x86-64 SECCOMP generates absoutely zero performance hit.
| The original seccomp patch for x86 also generated absolutely zero
| performance hit, both pratically and theoretically too. _zero_ CPU
| cycles of difference, zero cachelines.
Please re-enable this feature. It is needed for CPUShare (see #417130).
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 18.104.22.168 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash