Messages in this thread | | | Subject | Re: [PATCH v6 1/4] x86/pvclock: add setter for pvclock_pvti_cpu0_va | From | Joao Martins <> | Date | Thu, 19 Oct 2017 14:40:15 +0100 |
| |
On 10/17/2017 04:34 PM, Joao Martins wrote: > On 10/03/2017 12:55 PM, Joao Martins wrote: >> Right now there is only a pvclock_pvti_cpu0_va() which is defined >> on kvmclock since: >> >> commit dac16fba6fc5 >> ("x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap") >> >> The only user of this interface so far is kvm. This commit adds a >> setter function for the pvti page and moves pvclock_pvti_cpu0_va >> to pvclock, which is a more generic place to have it; and would >> allow other PV clocksources to use it, such as Xen. >> >> Signed-off-by: Joao Martins <joao.m.martins@oracle.com> >> Acked-by: Andy Lutomirski <luto@kernel.org> > > Ping? > > While the rest of series has been acked, I think that this patch (per > maintainers file) still misses x86 and (or?) kvm ack/review.
I found out an issue with ptp_kvm modinit (if attempted to be loaded) under Xen related to this series, so I resent with that fixed. Hopefully things can be taken from there - Sorry for the noise.
Thanks, Joao
| |