[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YB05/GIyD/UQRIGn@hirez.programming.kicks-ass.net>
Date: Fri, 5 Feb 2021 13:28:44 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Zhimin Feng <fengzhimin@...edance.com>
Cc: x86@...nel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
pbonzini@...hat.com, seanjc@...gle.com, vkuznets@...hat.com,
wanpengli@...cent.com, jmattson@...gle.com, joro@...tes.org,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, hpa@...or.com,
fweisbec@...il.com, zhouyibo@...edance.com,
zhanghaozhong@...edance.com
Subject: Re: [RFC: timer passthrough 1/9] KVM: vmx: hook set_next_event for
getting the host tscd
On Fri, Feb 05, 2021 at 06:03:09PM +0800, Zhimin Feng wrote:
> diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c
> index 6c9c342dd0e5..bc50f4a1a7c0 100644
> --- a/kernel/time/tick-common.c
> +++ b/kernel/time/tick-common.c
> @@ -26,6 +26,7 @@
> * Tick devices
> */
> DEFINE_PER_CPU(struct tick_device, tick_cpu_device);
> +EXPORT_SYMBOL_GPL(tick_cpu_device);
> /*
> * Tick next event: keeps track of the tick time
> */
Oh heck no. Modules have no business what so ever accessing this.
Powered by blists - more mailing lists