[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ceb1504-205a-26fc-2fec-2d87f8601b31@gmail.com>
Date: Thu, 5 Aug 2021 20:45:43 +0800
From: Tianyu Lan <ltykernel@...il.com>
To: Praveen Kumar <kumarpraveen@...ux.microsoft.com>,
kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
wei.liu@...nel.org, decui@...rosoft.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, x86@...nel.org, hpa@...or.com,
michael.h.kelley@...rosoft.com
Cc: Tianyu Lan <Tianyu.Lan@...rosoft.com>,
linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org,
vkuznets@...hat.com
Subject: Re: [PATCH] x86/Hyper-V: Initialize Hyper-V stimer after enabling
lapic
Hi Praveen:
Thanks for your review.
On 8/5/2021 2:41 PM, Praveen Kumar wrote:
>> +
>> +static void __init hv_setup_initr_mode(void)
>> +{
>> + if (old_setup_initr_mode)
>> + old_setup_initr_mode();
>> +
>> + /*
>> + * The direct-mode STIMER depends on LAPIC and so allocate
>> + * STIMER after calling initr node callback.
>> + */
>> + (void)hv_stimer_alloc(false);
> In my understanding, in previous implementation we were ignoring the return error as there was a fallback handling for LAPIC.
> However, I'm not seeing the same here, or am I missing something ?
>
Nice catch. The original comment should be keep and will add back in the
next version.
Powered by blists - more mailing lists