All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Stephen Hemminger" <sthemmin@microsoft.com>,
	kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
	"Haiyang Zhang" <haiyangz@microsoft.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	devel@linuxdriverproject.org,
	"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Roman Kagan" <rkagan@virtuozzo.com>,
	"Andy Lutomirski" <luto@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Mohammed Gamal" <mmorsy@redhat.com>
Subject: Re: [PATCH v2 4/7] x86/hyper-v: redirect reenlightment notifications on CPU offlining
Date: Mon, 15 Jan 2018 11:44:12 +0100	[thread overview]
Message-ID: <87y3kziepv.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1801142142280.2371@nanos> (Thomas Gleixner's message of "Sun, 14 Jan 2018 21:44:38 +0100 (CET)")

Thomas Gleixner <tglx@linutronix.de> writes:

> On Wed, 13 Dec 2017, Vitaly Kuznetsov wrote:
>> +static int hv_cpu_die(unsigned int cpu)
>> +{
>> +	struct hv_reenlightenment_control re_ctrl;
>> +	int i;
>> +	static DEFINE_SPINLOCK(lock);
>> +
>> +	if (hv_reenlightenment_cb == NULL)
>> +		return 0;
>> +
>> +	/* Make sure the CPU we migrate to is not going away too */
>> +	spin_lock(&lock);
>
> What kind of voodoo is this? CPU hotplug is serialized already...
>

Yes, someone around made a comment 'what happens if some day we'll have
parallel cpu hot[un]plug' and I added this. Not really needed, will drop
in v3.

>> +	rdmsrl(HV_X64_MSR_REENLIGHTENMENT_CONTROL, *((u64 *)&re_ctrl));
>> +	if (re_ctrl.target_vp == hv_vp_index[cpu]) {
>> +		/* Find some other online CPU */
>> +		for_each_online_cpu(i) {
>
>   		cpu = cpumask_any_but(cpu_online_mask);
>
> Hmm?
>

Cool, thanks)

-- 
  Vitaly

WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kvm@vger.kernel.org, x86@kernel.org,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	"Haiyang Zhang" <haiyangz@microsoft.com>,
	"Stephen Hemminger" <sthemmin@microsoft.com>,
	"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
	"Andy Lutomirski" <luto@kernel.org>,
	"Mohammed Gamal" <mmorsy@redhat.com>,
	"Cathy Avery" <cavery@redhat.com>,
	"Roman Kagan" <rkagan@virtuozzo.com>,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [PATCH v2 4/7] x86/hyper-v: redirect reenlightment notifications on CPU offlining
Date: Mon, 15 Jan 2018 11:44:12 +0100	[thread overview]
Message-ID: <87y3kziepv.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1801142142280.2371@nanos> (Thomas Gleixner's message of "Sun, 14 Jan 2018 21:44:38 +0100 (CET)")

Thomas Gleixner <tglx@linutronix.de> writes:

> On Wed, 13 Dec 2017, Vitaly Kuznetsov wrote:
>> +static int hv_cpu_die(unsigned int cpu)
>> +{
>> +	struct hv_reenlightenment_control re_ctrl;
>> +	int i;
>> +	static DEFINE_SPINLOCK(lock);
>> +
>> +	if (hv_reenlightenment_cb == NULL)
>> +		return 0;
>> +
>> +	/* Make sure the CPU we migrate to is not going away too */
>> +	spin_lock(&lock);
>
> What kind of voodoo is this? CPU hotplug is serialized already...
>

Yes, someone around made a comment 'what happens if some day we'll have
parallel cpu hot[un]plug' and I added this. Not really needed, will drop
in v3.

>> +	rdmsrl(HV_X64_MSR_REENLIGHTENMENT_CONTROL, *((u64 *)&re_ctrl));
>> +	if (re_ctrl.target_vp == hv_vp_index[cpu]) {
>> +		/* Find some other online CPU */
>> +		for_each_online_cpu(i) {
>
>   		cpu = cpumask_any_but(cpu_online_mask);
>
> Hmm?
>

Cool, thanks)

-- 
  Vitaly

  reply	other threads:[~2018-01-15 10:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 15:09 [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V Vitaly Kuznetsov
2017-12-13 15:09 ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 1/7] x86/hyper-v: check for required priviliges in hyperv_init() Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2018-01-14 20:32   ` Thomas Gleixner
2018-01-14 20:32     ` Thomas Gleixner
2017-12-13 15:09 ` [PATCH v2 2/7] x86/hyper-v: add a function to read both TSC and TSC page value simulateneously Vitaly Kuznetsov
2018-01-14 20:35   ` Thomas Gleixner
2018-01-14 20:35     ` Thomas Gleixner
2018-01-15 10:45     ` Vitaly Kuznetsov
2018-01-15 10:45       ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 3/7] x86/hyper-v: reenlightenment notifications support Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2018-01-14 20:42   ` Thomas Gleixner
2017-12-13 15:09 ` [PATCH v2 4/7] x86/hyper-v: redirect reenlightment notifications on CPU offlining Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2018-01-14 20:44   ` Thomas Gleixner
2018-01-15 10:44     ` Vitaly Kuznetsov [this message]
2018-01-15 10:44       ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 5/7] x86/irq: Count Hyper-V reenlightenment interrupts Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 6/7] x86/kvm: pass stable clocksource to guests when running nested on Hyper-V Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 7/7] x86/kvm: support Hyper-V reenlightenment Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2017-12-15  9:01 ` [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V Paolo Bonzini
2017-12-15  9:30   ` Vitaly Kuznetsov
2018-01-03 14:57     ` 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=87y3kziepv.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=Michael.H.Kelley@microsoft.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=mmorsy@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkagan@virtuozzo.com \
    --cc=rkrcmar@redhat.com \
    --cc=sthemmin@microsoft.com \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.