| Date | Mon, 21 Nov 2022 15:46:25 +0100 | From | Borislav Petkov <> | Subject | Re: [Patch v3 06/14] init: Call mem_encrypt_init() after Hyper-V hypercall init is done |
| |
On Wed, Nov 16, 2022 at 10:41:29AM -0800, Michael Kelley wrote: > Fix this by moving mem_encrypt_init() after late_time_init() and > related clock initializations. The intervening initializations don't > do any I/O that requires the swiotlb, so moving mem_encrypt_init() > slightly later has no impact.
I hope you're right. Our boot ordering is fragile as hell. But mem_encrypt_init() doesn't do a whole lot of important setup - that has happened a lot earlier already - so I'm not too worried.
But we'll see what breaks in wider testing.
-- Regards/Gruss, Boris.
https://people.kernel.org/tglx/notes-about-netiquette
|