From: Tianyu Lan <ltykernel@gmail.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Tianyu Lan <Tianyu.Lan@microsoft.com>,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, x86@kernel.org,
michael.h.kelley@microsoft.com, wei.liu@kernel.org
Subject: Re: [PATCH V2] x86/Hyper-V: don't allocate clockevent device when synthetic timer is unavailable
Date: Tue, 31 Mar 2020 20:06:03 +0800 [thread overview]
Message-ID: <eaa37ee8-8d16-95a5-c1b3-360fb8af58b5@gmail.com> (raw)
In-Reply-To: <87sgho22ki.fsf@vitty.brq.redhat.com>
On 3/31/2020 7:20 PM, Vitaly Kuznetsov wrote:
> ltykernel@gmail.com writes:
>
>> From: Tianyu Lan <Tianyu.Lan@microsoft.com>
>>
>> Current code initializes clock event data structure for syn timer
>> even when it's unavailable. Fix it.
>>
>> Signed-off-by: Tianyu Lan <Tianyu.Lan@microsoft.com>
>> ---
>> Change since v1:
>> Update title and commit log.
>>
>> drivers/hv/hv.c | 15 +++++++++------
>> 1 file changed, 9 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/hv/hv.c b/drivers/hv/hv.c
>> index 632d25674e7f..2e893768fc76 100644
>> --- a/drivers/hv/hv.c
>> +++ b/drivers/hv/hv.c
>> @@ -212,13 +212,16 @@ int hv_synic_alloc(void)
>> tasklet_init(&hv_cpu->msg_dpc,
>> vmbus_on_msg_dpc, (unsigned long) hv_cpu);
>>
>> - hv_cpu->clk_evt = kzalloc(sizeof(struct clock_event_device),
>> - GFP_KERNEL);
>> - if (hv_cpu->clk_evt == NULL) {
>> - pr_err("Unable to allocate clock event device\n");
>> - goto err;
>> + if (ms_hyperv.features & HV_MSR_SYNTIMER_AVAILABLE) {
>> + hv_cpu->clk_evt =
>> + kzalloc(sizeof(struct clock_event_device),
>> + GFP_KERNEL);
>> + if (hv_cpu->clk_evt == NULL) {
>> + pr_err("Unable to allocate clock event device\n");
>> + goto err;
>> + }
>> + hv_init_clockevent_device(hv_cpu->clk_evt, cpu);
>> }
>> - hv_init_clockevent_device(hv_cpu->clk_evt, cpu);
>>
>> hv_cpu->synic_message_page =
>> (void *)get_zeroed_page(GFP_ATOMIC);
>
> Thank you for fixing the subject! I had one more question on the
> previous version which still stands: which tree is this patch for?
> Upstream, clockevent allocation has moved to
> drivers/clocksource/hyperv_timer.c and the code there is different.
>
Yes, I just noticed I fixed an issue on the old code after Michael
reminded me. Sorry for noise. Please ignore it.
prev parent reply other threads:[~2020-03-31 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 2:17 ltykernel
2020-03-31 11:20 ` Vitaly Kuznetsov
2020-03-31 12:06 ` Tianyu Lan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eaa37ee8-8d16-95a5-c1b3-360fb8af58b5@gmail.com \
--to=ltykernel@gmail.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=bp@alien8.de \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.h.kelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wei.liu@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®