From: Dmitry Safonov <dima@arista.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Vitaly Kuznetsov" <vkuznets@redhat.com>,
linux-kernel@vger.kernel.org,
"Prasanna Panchamukhi" <panchamukhi@arista.com>,
"Andy Lutomirski" <luto@kernel.org>,
"Borislav Petkov" <bp@alien8.de>,
"Cathy Avery" <cavery@redhat.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Ingo Molnar" <mingo@redhat.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
"Mohammed Gamal" <mmorsy@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Roman Kagan" <rkagan@virtuozzo.com>,
"Sasha Levin" <sashal@kernel.org>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
devel@linuxdriverproject.org, kvm@vger.kernel.org,
linux-hyperv@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] x86/hyperv: Disable preemption while setting reenlightenment vector
Date: Fri, 14 Jun 2019 15:28:37 +0100 [thread overview]
Message-ID: <d0ea735e-487e-8205-9415-8708a686ede9@arista.com> (raw)
In-Reply-To: <20190614122726.GL3436@hirez.programming.kicks-ass.net>
On 6/14/19 1:27 PM, Peter Zijlstra wrote:
> On Fri, Jun 14, 2019 at 12:50:51PM +0100, Dmitry Safonov wrote:
>> On 6/14/19 11:08 AM, Vitaly Kuznetsov wrote:
>>> Peter Zijlstra <peterz@infradead.org> writes:
>>>
>>>> @@ -182,7 +182,7 @@ void set_hv_tscchange_cb(void (*cb)(void))
>>>> struct hv_reenlightenment_control re_ctrl = {
>>>> .vector = HYPERV_REENLIGHTENMENT_VECTOR,
>>>> .enabled = 1,
>>>> - .target_vp = hv_vp_index[smp_processor_id()]
>>>> + .target_vp = hv_vp_index[raw_smp_processor_id()]
>>>> };
>>>> struct hv_tsc_emulation_control emu_ctrl = {.enabled = 1};
>>>>
>>>
>>> Yes, this should do, thanks! I'd also suggest to leave a comment like
>>> /*
>>> * This function can get preemted and migrate to a different CPU
>>> * but this doesn't matter. We just need to assign
>>> * reenlightenment notification to some online CPU. In case this
>>> * CPU goes offline, hv_cpu_die() will re-assign it to some
>>> * other online CPU.
>>> */
>>
>> What if the cpu goes down just before wrmsrl()?
>> I mean, hv_cpu_die() will reassign another cpu, but this thread will be
>> resumed on some other cpu and will write cpu number which is at that
>> moment already down?
>>
>> (probably I miss something)
>>
>> And I presume it's guaranteed that during hv_cpu_die() no other cpu may
>> go down:
>> : new_cpu = cpumask_any_but(cpu_online_mask, cpu);
>> : re_ctrl.target_vp = hv_vp_index[new_cpu];
>> : wrmsrl(HV_X64_MSR_REENLIGHTENMENT_CONTROL, *((u64 *)&re_ctrl));
>
> Then cpus_read_lock() is the right interface, not preempt_disable().
>
> I know you probably can't change the HV interface, but I'm thinking its
> rather daft you have to specify a CPU at all for this. The HV can just
> pick one and send the notification there, who cares.
Heh, I thought cpus_read_lock() is more "internal" api and
preempt_diable() is prefered ;-)
Will send v2 with the suggested comment and cpus_read_lock().
--
Dima
next prev parent reply other threads:[~2019-06-14 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 21:20 [PATCH] x86/hyperv: Disable preemption while setting reenlightenment vector Dmitry Safonov
2019-06-12 9:35 ` Peter Zijlstra
2019-06-12 10:25 ` Vitaly Kuznetsov
2019-06-12 10:17 ` Vitaly Kuznetsov
2019-06-13 19:00 ` Thomas Gleixner
2019-06-14 8:06 ` Vitaly Kuznetsov
2019-06-14 8:28 ` Peter Zijlstra
2019-06-14 10:08 ` Vitaly Kuznetsov
2019-06-14 11:50 ` Dmitry Safonov
2019-06-14 12:27 ` Peter Zijlstra
2019-06-14 14:28 ` Dmitry Safonov [this message]
2019-06-14 21:44 ` Vitaly Kuznetsov
2019-06-14 21:36 ` Vitaly Kuznetsov
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=d0ea735e-487e-8205-9415-8708a686ede9@arista.com \
--to=dima@arista.com \
--cc=Michael.H.Kelley@microsoft.com \
--cc=bp@alien8.de \
--cc=cavery@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mmorsy@redhat.com \
--cc=panchamukhi@arista.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkagan@virtuozzo.com \
--cc=rkrcmar@redhat.com \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).