From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: david.vrabel@citrix.com, jgross@suse.com
Cc: xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Reinstate irq alloc/dealloc locking patch
Date: Wed, 3 Aug 2016 13:22:26 -0400 [thread overview]
Message-ID: <1470244948-17674-1-git-send-email-boris.ostrovsky@oracle.com> (raw)
Original version of that patch (commit a89941816726) had to be reverted
due to Xen allocating irqs in its cpu_up ops.
The first patch moves allocations into hotplug notifiers and the second
one restores the original patch (with minor adjustments to new hotplug
framework)
This originally went through tip tree but after a couple of failures
reportedby kbuild robot (due to various combinations of CONFIG_SMP and
CONFIG_XEN_PVH) I decided to take it through Xen tree (with config problems
hopefully finally fixed).
Boris Ostrovsky (2):
xen/x86: Move irq allocation from Xen smp_op.cpu_up()
hotplug: Prevent alloc/free of irq descriptors during cpu up/down
(again)
arch/x86/kernel/smpboot.c | 11 ---------
arch/x86/xen/enlighten.c | 61 +++++++++++++++++++++++++++++++++++++----------
arch/x86/xen/smp.c | 45 ++--------------------------------
arch/x86/xen/smp.h | 13 ++++++++++
kernel/cpu.c | 8 +++++++
5 files changed, 71 insertions(+), 67 deletions(-)
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-08-03 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 17:22 Boris Ostrovsky [this message]
2016-08-03 17:22 ` [PATCH v2 1/2] xen/x86: Move irq allocation from Xen smp_op.cpu_up() Boris Ostrovsky
2016-08-05 6:40 ` Juergen Gross
2016-08-03 17:22 ` [PATCH v2 2/2] hotplug: Prevent alloc/free of irq descriptors during cpu up/down (again) Boris Ostrovsky
2016-08-05 6:41 ` Juergen Gross
2016-08-24 17:46 ` [PATCH v2 0/2] Reinstate irq alloc/dealloc locking patch David Vrabel
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=1470244948-17674-1-git-send-email-boris.ostrovsky@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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).