Messages in this thread | | | Date | Tue, 11 Sep 2018 12:25:04 +0200 | From | Borislav Petkov <> | Subject | Re: [PATCH v6 5/5] x86/kvm: Avoid dynamic allocation of pvclock data when SEV is active |
| |
On Tue, Sep 11, 2018 at 12:19:13PM +0200, Paolo Bonzini wrote: > That's exactly what kvmclock is for, it provides a stable and > synchronized clock on top of unsynchronized TSCs. But that's also why > you need one struct per vCPU, at least in the synchronized case.
Why?
Why can't it be a single pointer to a struct pvclock_vsyscall_time_info shared between all vCPUs?
Or does each vCPU write its own specific stuff into it so it has to be per-vCPU?
-- Regards/Gruss, Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --
| |