From: "H. Peter Anvin" <hpa@zytor.com>
To: "Luck, Tony" <tony.luck@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Prarit Bhargava <prarit@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
Michel Lespinasse <walken@google.com>,
Seiji Aguchi <seiji.aguchi@hds.com>,
"Zhang, Yang Z" <yang.z.zhang@intel.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
"Morgan, Janet" <janet.morgan@intel.com>,
"ruiv.wang@gmail.com" <ruiv.wang@gmail.com>,
"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>
Subject: Re: [PATCH] x86: Add check for number of available vectors before CPU down [v3]
Date: Fri, 20 Dec 2013 16:08:53 -0800 [thread overview]
Message-ID: <52B4DC15.6090004@zytor.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31D8F0E9@ORSMSX106.amr.corp.intel.com>
On 12/20/2013 03:06 PM, Luck, Tony wrote:
>> I haven't double checked, but I'm assuming the hot plug locks are held
>> while you are doing this.
>
> I dug into that when looking at v2 - the whole thing is under "stop_machine()"
> so locking was not an issue.
>
> Reviewed-by: Tony Luck <tony.luck@intel.com>
>
Awesome, thank you! I have queued this up for Linus already as a fix
for 3.13, as it seems important enough.
-hpa
next prev parent reply other threads:[~2013-12-21 0:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 15:50 [PATCH] x86: Add check for number of available vectors before CPU down [v3] Prarit Bhargava
2013-12-20 22:56 ` Andi Kleen
2013-12-20 23:06 ` Luck, Tony
2013-12-21 0:08 ` H. Peter Anvin [this message]
2013-12-20 23:39 ` [tip:x86/urgent] x86: Add check for number of available vectors before CPU down tip-bot for Prarit Bhargava
2013-12-20 23:39 ` [tip:x86/urgent] x86, irq: Change check_vectors() to check_irq_vectors_for_cpu_disable() tip-bot for H. Peter Anvin
2013-12-23 7:12 ` [PATCH] x86: Add check for number of available vectors before CPU down [v3] Chen, Gong
2013-12-23 12:32 ` Prarit Bhargava
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=52B4DC15.6090004@zytor.com \
--to=hpa@zytor.com \
--cc=ak@linux.intel.com \
--cc=gong.chen@linux.intel.com \
--cc=janet.morgan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=prarit@redhat.com \
--cc=ruiv.wang@gmail.com \
--cc=seiji.aguchi@hds.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=walken@google.com \
--cc=x86@kernel.org \
--cc=yang.z.zhang@intel.com \
/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.