Messages in this thread | | | Date | Mon, 10 Sep 2018 17:53:29 +0200 | From | Borislav Petkov <> | Subject | Re: [PATCH v6 5/5] x86/kvm: Avoid dynamic allocation of pvclock data when SEV is active |
| |
On Mon, Sep 10, 2018 at 08:15:38AM -0500, Brijesh Singh wrote: > > Now, the real question from all this SNAFU is, why can't all those point > > to a single struct pvclock_vsyscall_time_info and all CPUs read a single > > thing? Why do they have to be per-CPU and thus waste so much memory?
You forgot to answer to the real question - why do we need those things to be perCPU and why can't we use a single instance to share with *all* CPUs?
Because if we can, then we're golden!
-- Regards/Gruss, Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --
| |