From: Nathan Fontenot <nfont@linux.vnet.ibm.com>
To: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: [PATCH v2 1/6] pseries: Define rtas hotplug event sections
Date: Mon, 17 Nov 2014 15:48:36 -0600 [thread overview]
Message-ID: <546A6D34.9030206@linux.vnet.ibm.com> (raw)
In-Reply-To: <546A6C23.1080800@linux.vnet.ibm.com>
In order to handle device hotplug in the kernel on pseries hotplug
notifications will be communicated to the kernel in the form of a
rtas hotplug events. This patch adds the definition of rtas hotplug event
sections.
Signed-off-by: Nathan Fontenot <nfont@linux.vnet.ibm.com>
---
arch/powerpc/include/asm/rtas.h | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/arch/powerpc/include/asm/rtas.h b/arch/powerpc/include/asm/rtas.h
index b390f55..77e112e 100644
--- a/arch/powerpc/include/asm/rtas.h
+++ b/arch/powerpc/include/asm/rtas.h
@@ -273,6 +273,7 @@ inline uint32_t rtas_ext_event_company_id(struct rtas_ext_event_log_v6 *ext_log)
#define PSERIES_ELOG_SECT_ID_MANUFACT_INFO (('M' << 8) | 'I')
#define PSERIES_ELOG_SECT_ID_CALL_HOME (('C' << 8) | 'H')
#define PSERIES_ELOG_SECT_ID_USER_DEF (('U' << 8) | 'D')
+#define PSERIES_ELOG_SECT_ID_HOTPLUG (('H' << 8) | 'P')
/* Vendor specific Platform Event Log Format, Version 6, section header */
struct pseries_errorlog {
@@ -296,6 +297,31 @@ inline uint16_t pseries_errorlog_length(struct pseries_errorlog *sect)
return be16_to_cpu(sect->length);
}
+/* RTAS pseries hotplug errorlog section */
+struct pseries_hp_errorlog {
+ u8 resource;
+ u8 action;
+ u8 id_type;
+ u8 reserved;
+ union {
+ __be32 drc_index;
+ __be32 drc_count;
+ char drc_name[1];
+ } _drc_u;
+};
+
+#define PSERIES_HP_ELOG_RESOURCE_CPU 1
+#define PSERIES_HP_ELOG_RESOURCE_MEM 2
+#define PSERIES_HP_ELOG_RESOURCE_SLOT 3
+#define PSERIES_HP_ELOG_RESOURCE_PHB 4
+
+#define PSERIES_HP_ELOG_ACTION_ADD 1
+#define PSERIES_HP_ELOG_ACTION_REMOVE 2
+
+#define PSERIES_HP_ELOG_ID_DRC_NAME 1
+#define PSERIES_HP_ELOG_ID_DRC_INDEX 2
+#define PSERIES_HP_ELOG_ID_DRC_COUNT 3
+
struct pseries_errorlog *get_pseries_errorlog(struct rtas_error_log *log,
uint16_t section_id);
next prev parent reply other threads:[~2014-11-17 21:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 21:44 [PATCH v2 0/6] pseries: Move memory hotplug to the kernel Nathan Fontenot
2014-11-17 21:48 ` Nathan Fontenot [this message]
2014-11-17 21:50 ` [PATCH v2 2/6] pseries: Update of_drconf_cell struct for endian-ness Nathan Fontenot
2014-11-17 21:51 ` [PATCH v2 3/6] pseries: Create new device hotplug entry point Nathan Fontenot
2014-11-17 22:53 ` Gavin Shan
2014-11-18 18:18 ` Nathan Fontenot
2014-11-21 7:49 ` Cyril Bur
2014-11-24 14:45 ` Nathan Fontenot
2014-11-26 23:44 ` Benjamin Herrenschmidt
2014-11-17 21:53 ` [PATCH v2 4/6] pseries: Export the acquire/release drc index routines Nathan Fontenot
2014-11-17 21:54 ` [PATCH v2 5/6] pseries: Implement memory hotplug add in the kernel Nathan Fontenot
2014-11-21 7:49 ` Cyril Bur
2014-11-24 14:56 ` Nathan Fontenot
2014-11-17 21:56 ` [PATCH v2 6/6] pseries: Implement memory hotplug remove " Nathan Fontenot
2014-11-21 7:49 ` Cyril Bur
2014-11-24 15:03 ` Nathan Fontenot
2014-11-24 22:05 ` Cyril Bur
2014-11-18 2:00 ` [PATCH v2 0/6] pseries: Move memory hotplug to " Cyril Bur
2014-11-18 18:34 ` Nathan Fontenot
2014-11-18 22:59 ` Cyril Bur
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=546A6D34.9030206@linux.vnet.ibm.com \
--to=nfont@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).