Searched hist:"3 dbbaf200f532e01e56168b8339f2981f2cb1d67" (Results 1 – 2 of 2) sorted by relevance
| /linux/arch/powerpc/include/asm/ |
| H A D | prom.h | diff 3dbbaf200f532e01e56168b8339f2981f2cb1d67 Tue Feb 21 02:12:18 CET 2017 Michael Roth <mdroth@linux.vnet.ibm.com> powerpc/pseries: Advertise Hot Plug Event support to firmware
With the inclusion of commit 333f7b76865b ("powerpc/pseries: Implement
indexed-count hotplug memory add") and commit 753843471cbb
("powerpc/pseries: Implement indexed-count hotplug memory remove"), 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 2 (5 in IBM numbering) 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.
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| /linux/arch/powerpc/kernel/ |
| H A D | prom_init.c | diff 3dbbaf200f532e01e56168b8339f2981f2cb1d67 Tue Feb 21 02:12:18 CET 2017 Michael Roth <mdroth@linux.vnet.ibm.com> powerpc/pseries: Advertise Hot Plug Event support to firmware
With the inclusion of commit 333f7b76865b ("powerpc/pseries: Implement
indexed-count hotplug memory add") and commit 753843471cbb
("powerpc/pseries: Implement indexed-count hotplug memory remove"), 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 2 (5 in IBM numbering) 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.
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|