[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h7j324w2.ffs@nanos.tec.linutronix.de>
Date: Sat, 15 May 2021 21:06:37 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Wei Liu <wei.liu@...nel.org>,
Michael Kelley <mikelley@...rosoft.com>
Cc: vkuznets <vkuznets@...hat.com>,
"linux-hyperv\@vger.kernel.org" <linux-hyperv@...r.kernel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Mohammed Gamal <mgamal@...hat.com>,
Wei Liu <wei.liu@...nel.org>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Dexuan Cui <decui@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] clocksource/drivers/hyper-v: Re-enable VDSO_CLOCKMODE_HVCLOCK on X86
On Sat, May 15 2021 at 15:43, Wei Liu wrote:
> On Thu, May 13, 2021 at 01:29:12PM +0000, Michael Kelley wrote:
>> From: Vitaly Kuznetsov <vkuznets@...hat.com> Sent: Thursday, May 13, 2021 12:33 AM
>> >
>> > Mohammed reports (https://bugzilla.kernel.org/show_bug.cgi?id=213029)
>> > the commit e4ab4658f1cf ("clocksource/drivers/hyper-v: Handle vDSO
>> > differences inline") broke vDSO on x86. The problem appears to be that
>> > VDSO_CLOCKMODE_HVCLOCK is an enum value in 'enum vdso_clock_mode' and
>> > '#ifdef VDSO_CLOCKMODE_HVCLOCK' branch evaluates to false (it is not
>> > a define). Use a dedicated HAVE_VDSO_CLOCKMODE_HVCLOCK define instead.
>> >
>> > Suggested-by: Thomas Gleixner <tglx@...utronix.de>
>> > Reported-by: Mohammed Gamal <mgamal@...hat.com>
>> > Fixes: e4ab4658f1cf ("clocksource/drivers/hyper-v: Handle vDSO differences inline")
>> > Signed-off-by: Vitaly Kuznetsov <vkuznets@...hat.com>
> [...]
>>
>> Reviewed-by: Michael Kelley <mikelley@...rosoft.com>
>>
> Applied to hyperv-fixes. Thanks.
It's already in the tip tree...
Powered by blists - more mailing lists