lkml.org 
[lkml]   [2018]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [patch 0/7] x86/kvmclock: Remove memblock dependency and further cleanups
    > So this still will have some overhead when kvmclock is not in use, but
    > bringing it down to zero would be a massive trainwreck and even more
    > indirections.

    Hi Thomas,

    In my opinion, having kvmclock page in __initdata for boot cpu, and
    setup it in init_hypervisor_platform(). Later, switch to memblock
    allocated memory in x86_init.hyper.guest_late_init() for all CPUs
    would not be too bad, and might be even use fewer lines of code. In
    addition, it won't have any overhead when kvm is not used.

    Pavel
    \
     
     \ /
      Last update: 2018-07-15 22:05    [W:3.476 / U:0.788 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site