x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. x86/fpu: xstate_offset: 896, xstate_sizes: 64 x86/fpu: xstate_offset: 832, xstate_sizes: 64 x86/fpu: xstate_offset: 576, xstate_sizes: 256

x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'

x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600rc7-generic root=UUID=66c28cf8-41b0-4ae7-998d-8e3e76a3fed7 ro quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor initcall_debug psmouse.synaptics_intertouch=1 init=/lib/systemd/systemd-bootchart microcode: microcode updated early to revision 0x84, date = Add a debug option to make it easier to find out what takes so long? Do the initialization asynchronously? (At least from the Linuxģ. Add an option to disable IMA from the Linux kernel command line, forĢ. Users could decrease the boot time without having to rebuild the Linuxġ. The Ubuntu kernel configuration has `CONFIG_IMA=y`, and it be great, if

initcall init_ima+0x0/0x3a returned 0 after 112414 usecs That is quite a long time, and it’d be great to reduce Processor, `init_ima` takes 112 ms to execute according to With Linux 4.16-rc7 on a TUXEDO Book BU1406 with an Intel Kaby Lake To: Dmitry Kasatkin +Cc: linux-integrity, linux-kernel

How to move `init_ima` out of critical path to decrease boot time? LKML Archive on help / color / mirror / Atom feed * How to move `init_ima` out of critical path to decrease boot time? 7:37 Paul Menzel 0 siblings, 0 replies only message in thread

Bisoncam nb pro software