From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Roth <mdroth@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: David Gibson <david@gibson.dropbear.id.au>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>
Subject: Re: powerpc/pseries: advertise Hot Plug Event support to firmware
Date: Mon, 27 Feb 2017 21:11:05 +1100 (AEDT) [thread overview]
Message-ID: <3vWyCY60M9z9sNC@ozlabs.org> (raw)
In-Reply-To: <1487639538-25922-1-git-send-email-mdroth@linux.vnet.ibm.com>
On Tue, 2017-02-21 at 01:12:18 UTC, Michael Roth wrote:
> With the inclusion of:
>
> powerpc/pseries: Implement indexed-count hotplug memory remove
> powerpc/pseries: Implement indexed-count hotplug memory add
>
> we now have complete handling of the RTAS hotplug event format
> as described by PAPR via ACR "PAPR Changes for Hotplug RTAS Events".
>
> This capability is indicated by byte 6, bit 5 of architecture
> option vector 5, and allows for greater control over cpu/memory/pci
> hot plug/unplug operations.
>
> Existing pseries kernels will utilize this capability based on the
> existence of the /event-sources/hot-plug-events DT property, so we
> only need to advertise it via CAS and do not need a corresponding
> FW_FEATURE_* value to test for.
>
> Cc: Michael Ellerman <mpe@ellerman.id.au>
> Cc: Nathan Fontenot <nfont@linux.vnet.ibm.com>
> Cc: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/3dbbaf200f532e01e56168b8339f29
cheers
prev parent reply other threads:[~2017-02-27 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 1:12 [PATCH] powerpc/pseries: advertise Hot Plug Event support to firmware Michael Roth
2017-02-21 15:49 ` Nathan Fontenot
2017-02-22 0:58 ` David Gibson
2017-02-27 10:11 ` Michael Ellerman [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=3vWyCY60M9z9sNC@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.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.