From: Prarit Bhargava <prarit@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Prarit Bhargava <prarit@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Seiji Aguchi <seiji.aguchi@hds.com>,
Andi Kleen <ak@linux.intel.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH 0/2] x86, Fix irq exhaustion issues with cpu hotplug
Date: Tue, 13 May 2014 11:39:33 -0400 [thread overview]
Message-ID: <1399995575-3129-1-git-send-email-prarit@redhat.com> (raw)
These patches have been previously submitted but appear to have been lost
on LKML.
There are still some issues with irq exhaustion when removing cpus. These
two patches fix two serious bugs. The first patch, from Yinghai Lu, corrects
the available vectors count for each cpu. The second patch takes into account
the numa-awareness of an irq when reassigning the irq.
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org
Cc: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
Cc: Yinghai Lu <yinghai@kernel.org>
Prarit Bhargava (1):
x86, make check_irq_vectors_for_cpu_disable() aware of numa node irqs
Yinghai Lu (1):
x86, irq: get correct available vectors for cpu disable
arch/x86/kernel/irq.c | 158 ++++++++++++++++++++++++++++++++++++-------------
1 file changed, 116 insertions(+), 42 deletions(-)
--
1.7.9.3
next reply other threads:[~2014-05-13 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 15:39 Prarit Bhargava [this message]
2014-05-13 15:39 ` [PATCH 1/2] x86, irq: get correct available vectors for cpu disable Prarit Bhargava
2014-05-13 15:39 ` [PATCH 2/2] x86, make check_irq_vectors_for_cpu_disable() aware of numa node irqs 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=1399995575-3129-1-git-send-email-prarit@redhat.com \
--to=prarit@redhat.com \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=seiji.aguchi@hds.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@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.