From: David Vrabel <david.vrabel@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<david.vrabel@citrix.com>, <jgross@suse.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH v2 0/2] Reinstate irq alloc/dealloc locking patch
Date: Wed, 24 Aug 2016 18:46:06 +0100 [thread overview]
Message-ID: <57BDDD5E.80304@citrix.com> (raw)
In-Reply-To: <1470244948-17674-1-git-send-email-boris.ostrovsky@oracle.com>
On 03/08/16 18:22, Boris Ostrovsky wrote:
> 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).
Applied to for-linus-4.9, thanks.
David
prev parent reply other threads:[~2016-08-24 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 17:22 [PATCH v2 0/2] Reinstate irq alloc/dealloc locking patch Boris Ostrovsky
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-10 18:10 ` [tip:smp/hotplug] cpu/hotplug: Prevent alloc/free of irq descriptors during CPU " tip-bot for Boris Ostrovsky
2016-08-11 12:53 ` Boris Ostrovsky
2016-08-11 13:20 ` Sebastian Andrzej Siewior
2016-08-11 14:11 ` Boris Ostrovsky
2016-08-11 14:17 ` Sebastian Andrzej Siewior
2016-08-11 14:30 ` Boris Ostrovsky
2016-08-11 14:44 ` Sebastian Andrzej Siewior
2016-08-11 15:06 ` Boris Ostrovsky
2016-08-11 15:12 ` Sebastian Andrzej Siewior
2016-08-24 17:46 ` David Vrabel [this message]
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=57BDDD5E.80304@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.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