From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: John Allen <jallen@linux•vnet.ibm.com>,
Nathan Fontenot <nfont@linux•vnet.ibm.com>,
linuxppc-dev@lists•ozlabs.org
Cc: Michael Roth <mdroth@linux•vnet.ibm.com>
Subject: Re: [1/3] powerpc/pseries: Add pseries hotplug workqueue
Date: Wed, 20 Jul 2016 19:10:19 +1000 (AEST) [thread overview]
Message-ID: <3rvWMv15qLz9t0t@ozlabs.org> (raw)
In-Reply-To: <f03894c6-edf7-9fcc-c817-6e0ee6234dd6@linux.vnet.ibm.com>
On Thu, 2016-07-07 at 15:00:34 UTC, John Allen wrote:
> In support of PAPR changes to add a new hotplug interrupt, introduce a
> hotplug workqueue to avoid processing hotplug events in interrupt context.
> We will also take advantage of the queue on PowerVM to ensure hotplug
> events initiated from different sources (HMC and PRRN events) are handled
> and serialized properly.
>
> Signed-off-by: John Allen <jallen@linux•vnet.ibm.com>
> Reviewed-by: Nathan Fontenot <nfont@linux•vnet.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/9054619ef54a3a832863ae25d1
cheers
next prev parent reply other threads:[~2016-07-20 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 14:57 [PATCH 0/3] powerpc/pseries: Add pseries hotplug queue and PowerVM/PowerKVM use cases John Allen
2016-07-07 15:00 ` [PATCH 1/3] powerpc/pseries: Add pseries hotplug workqueue John Allen
2016-07-11 15:48 ` Nathan Fontenot
2016-07-20 9:10 ` Michael Ellerman [this message]
2016-07-07 15:03 ` [PATCH 2/3] powerpc/pseries: Add support for hotplug interrupt source John Allen
2016-07-11 15:49 ` Nathan Fontenot
2016-07-07 15:05 ` [PATCH 3/3] powerpc/pseries: Use kernel hotplug queue for PowerVM hotplug events John Allen
2016-07-11 15:52 ` Nathan Fontenot
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=3rvWMv15qLz9t0t@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=jallen@linux$(echo .)vnet.ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mdroth@linux$(echo .)vnet.ibm.com \
--cc=nfont@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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