powerpc/powernv: Read opal error log and export it through sysfs interface.
PATCH 1/1 powerpc/powernv: Read opal error log and export it through sysfs interface.
From: Mahesh Salgaonkar <[email protected]>
This patch adds support to read error logs from OPAL and export them to userspace through sysfs interface /sys/firmware/opa/opal-elog.
This patch buffers 128 error log records until it is consumed by userspace tool. This patch provides an sysfs interface '/sys/firmware/opa/opal-elog-ack' to user to receive an acknowledgement of successful log consumption.
This is what user space tool would do:
- Read error log from /sys/firmware/opa/opal-elog.
- Save it to the disk.
- Send an acknowledgement on successful consumption by writing error log id to /sys/firmware/opa/opal-elog-ack.
--- arch/powerpc/include/asm/opal.h | 11 + arch/powerpc/platforms/powernv/Makefile | 2 arch/powerpc/platforms/powernv/opal-elog.c | 309 ++++++++++++++++++++++++ arch/powerpc/platforms/powernv/opal-wrappers.S | 5 arch/powerpc/platforms/powernv/opal.c | 2 5 files changed, 328 insertions(+), 1 deletion(-) create mode 100644 arch/powerpc/platforms/powernv/opal-elog.c
arch/powerpc/include/asm/opal.h +11 -0
@@ -129,6 +129,11 @@ extern int opal_enter_rtas(struct rtas_args *args,#define OPAL_LPC_READ 67#define OPAL_LPC_WRITE 68#define OPAL_RETURN_CPU 69 +#define OPAL_ELOG_READ 71 +#define OPAL_ELOG_WRITE 72 +#define OPAL_ELOG_ACK 73 +#define OPAL_ELOG_RESEND 74 +#define OPAL_ELOG_SIZE 75#define OPAL_FLASH_VALIDATE 76#define OPAL_FLASH_MANAGE 77#define OPAL_FLASH_UPDATE 78
@@ -727,6 +732,11 @@ int64_t opal_lpc_write(uint32_t chip_id, enum OpalLPCAddressType addr_type, uint32_t addr, uint32_t data, uint32_t sz);int64_t opal_lpc_read (uint32_t chip_id,enum OpalLPCAddressType addr_type,uint32_t addr,uint32_t *data,uint32_t sz); +int64_t opal_read_elog (uint64_t buffer,size_t size,uint64_t log_id); +int64_t opal_get_elog_size (uint64_t *log_id,size_t *size,uint64_t *elog_type); +int64_t opal_write_elog (uint64_t buffer,uint64_t size,uint64_t offset); +int64_t opal_send_ack_elog (uint64_t log_id); +void opal_resend_pending_logs (void );int64_t opal_validate_flash (uint64_t buffer,uint32_t *size,uint32_t *result);int64_t opal_manage_flash (uint8_t op);int64_t opal_update_flash (uint64_t blk_list);
@@ -761,6 +771,7 @@ extern void opal_get_rtc_time(struct rtc_time *tm);extern unsigned long opal_get_boot_time (void );extern void opal_nvram_init (void );extern void opal_flash_init (void ); +extern int opal_elog_init (void );extern int opal_machine_check (struct pt_regs *regs);extern bool opal_mce_check_early_recovery (struct pt_regs *regs);
arch/powerpc/platforms/powernv/Makefile +1 -1
@@ -1,6 +1,6 @@ obj-y += setup.o opal-takeover.o opal-wrappers.o opal.o obj-y += opal-rtc.o opal-nvram.o opal-lpc.o opal-flash.o -obj-y += rng.o +obj-y += rng.o opal-elog.o obj-$(CONFIG_SMP) += smp.o obj-$(CONFIG_PCI) += pci.o pci-p5ioc2.o pci-ioda.o
arch/powerpc/platforms/powernv/opal-elog.c new file +309 -0
309 lines not on this page · raw message
arch/powerpc/platforms/powernv/opal-wrappers.S +5 -0
@@ -123,6 +123,11 @@ OPAL_CALL(opal_xscom_write, OPAL_XSCOM_WRITE); OPAL_CALL(opal_lpc_read, OPAL_LPC_READ); OPAL_CALL(opal_lpc_write, OPAL_LPC_WRITE); OPAL_CALL(opal_return_cpu, OPAL_RETURN_CPU); +OPAL_CALL(opal_read_elog, OPAL_ELOG_READ); +OPAL_CALL(opal_send_ack_elog, OPAL_ELOG_ACK); +OPAL_CALL(opal_get_elog_size, OPAL_ELOG_SIZE); +OPAL_CALL(opal_resend_pending_logs, OPAL_ELOG_RESEND); +OPAL_CALL(opal_write_elog, OPAL_ELOG_WRITE); OPAL_CALL(opal_validate_flash, OPAL_FLASH_VALIDATE); OPAL_CALL(opal_manage_flash, OPAL_FLASH_MANAGE); OPAL_CALL(opal_update_flash, OPAL_FLASH_UPDATE);
arch/powerpc/platforms/powernv/opal.c +2 -0
@@ -475,6 +475,8 @@ static int __init opal_init(void)/* Create "opal" kobject under /sys/firmware */ rc =opal_sysfs_init ();if (rc ==0 ) { +/* Setup error log interface */ + rc =opal_elog_init ();/* Setup code update interface */ opal_flash_init (); }
Quoted 2 lines · Mahesh J Salgaonkar
This patch adds support to read error logs from OPAL and export them to userspace through sysfs interface
/sys/firmware/opa/opal-elog.
I think we could provide a better interface with instead having a file per log message appear in sysfs. We're never going to have more than 128 of these at any one time on the Linux side, so it's not going to bee too many files.
e.g. /sys/firmware/opal/elog/<id>
that way, any new file in /sys/firmware/opal/elog/ means there's a new log entry available. I believe there's
To ack a log, you could just echo 'ack' to the file.
The other option woudl be to more closely follow what sysfs is meant to be - ascii text. This would mean having more (any) of the parser in kernel for the error logs - which may/may not be a bad idea.
However, it would make the end user code for consuming them much much simpler, and that may be a good thing.
Having some way of getting some information out without a userspace parser is probably good though, I'm pretty sure having only a binary interface in /sys is at least partially frowned upon.
Quoted 5 lines
This is what user space tool would do:
- Read error log from/sys/firmware/opa/opal-elog.
- Save it to the disk.
- Send an acknowledgement on successful consumption by writing error log id to/sys/firmware/opa/opal-elog-ack.
A userspace tool may want to explicitly *not* ack the log too, or only ack some entries, so the interface sohuld be sane for this use case too.
e.g. we could display them in petitboot.
arch/powerpc/platforms/powernv/opal-elog.c
Quoted 2 lines
arch/powerpc/platforms/powernv/opal-elog.c +0
-0
[ 2 more citation lines. Click/Enter to show. ]
Quoted 5 lines
new file mode 100644
index 0000000..fc891aearch/powerpc/platforms/powernv/opal-elog.c new file +0
-0@@ -0,0 +1,309 @@
<snip>
arch/powerpc/platforms/powernv/opal-elog.c line 23
Quoted 2 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +2
-0+/* Maximum size of a single log on FSP is 16KB */ +#define OPAL_MAX_ERRLOG_SIZE 16384
I've seen some conflicting things on this - is it 2kb or 16kb?
arch/powerpc/platforms/powernv/opal-elog.c line 30
Quoted 4 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +4
-0+ +struct opal_err_log { +struct list_head link; +uint64_t opal_log_id;
why is this uint64_t and not uint32_t? It appears that the log id is 32bits.
arch/powerpc/platforms/powernv/opal-elog.c line 36
Quoted 6 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +6
-0+size_t opal_log_size; +uint8_t data[OPAL_MAX_ERRLOG_SIZE ]; +}; + +/* Pre-allocated temp buffer to pull error log from opal. */ +static uint8_t err_log_data[OPAL_MAX_ERRLOG_SIZE ];
Why do we need temporary space? Why not just store directly into struct opal_err_log?
arch/powerpc/platforms/powernv/opal-elog.c line 38
Quoted 2 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +2
-0+/* Protect err_log_data buf */ +static DEFINE_MUTEX (err_log_data_mutex);
[ 15 more citation lines. Click/Enter to show. ]
Quoted 8 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +8
-0+ +static uint64_t total_log_size; +static bool opal_log_available; +static LIST_HEAD (elog_list); +static LIST_HEAD (elog_ack_list); + +/* lock to protect elog_list and elog-ack_list. */ +static DEFINE_SPINLOCK (opal_elog_lock);
arch/powerpc/platforms/powernv/opal-elog.c line 56
Quoted 10 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +10
-0+ +static DECLARE_WAIT_QUEUE_HEAD (opal_log_wait); + +/* +* Interface for user to acknowledge the error log. +* +* Once user acknowledge the log, we delete that record entry from the +* list and move it ack list. +*/ +void opal_elog_ack (uint64_t ack_id)
s/ack_id/log_id/
arch/powerpc/platforms/powernv/opal-elog.c
Quoted 2 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +2
-0+ +static ssize_t elog_ack_store(struct kobject *kobj,
[ 7 more citation lines. Click/Enter to show. ]
arch/powerpc/platforms/powernv/opal-elog.c line 94
Quoted 10 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +10
-0+struct kobj_attribute *attr, + const char *buf, size_t count) +{ + uint32_t log_ack_id; + log_ack_id = *(uint32_t *) buf; + +/* send acknowledgment to FSP */ +opal_elog_ack (log_ack_id); +return 0 ; +}
This function has a few problems:
Consider the following actions:
$ echo 1 > /sys/firmware/opal/opal-elog-ack $ echo 'abcde' > /sys/firmware/opal/opal-elog-ack
The former will read undefined memory and the latter will make a kernel thread, rsyslogd and systemd-journal all each a CPU each.
Basically, the problems are:
1) not endian safe
2) not following store API of returning nr bytes read
3) binary interface. Use sscanf to read numbers instead.
Quoted 2 lines
+/*
+ * Show error log records to user.
[ 9 more citation lines. Click/Enter to show. ]
arch/powerpc/platforms/powernv/opal-elog.c
Quoted 12 lines
+ */
arch/powerpc/platforms/powernv/opal-elog.c new file +11
-0+static ssize_t opal_elog_show (struct file *filp,struct kobject *kobj, +struct bin_attribute *bin_attr,char *buf, +loff_t pos,size_t count) +{ +unsigned long flags; +struct opal_err_log *record, *next; +size_t size =0 ; +size_t data_to_copy =0 ; +int error =0 ; + +/* Display one log@a time. */
use words, not @.
arch/powerpc/platforms/powernv/opal-elog.c line 111
Quoted 2 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +2
-0+if (count >OPAL_MAX_ERRLOG_SIZE ) + count =OPAL_MAX_ERRLOG_SIZE ;
[ 23 more citation lines. Click/Enter to show. ]
Quoted 16 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +16
-0+spin_lock_irqsave (&opal_elog_lock, flags); +/* Align the pos to point within total errlog size. */ +if (total_log_size && pos > total_log_size) + pos = pos % total_log_size; + +/* +* if pos goes beyond total_log_size then we know we don't have any +* new record to show. +*/ +if (total_log_size ==0 || pos >= total_log_size) { + opal_log_available =0 ; +if (filp->f_flags &O_NONBLOCK ) { +spin_unlock_irqrestore (&opal_elog_lock, flags); + error = -EAGAIN ; + goto out; + }
arch/powerpc/platforms/powernv/opal-elog.c line 138
Quoted 10 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +10
-0+spin_unlock_irqrestore (&opal_elog_lock, flags); + pos =0 ; + +/* Wait until we get log from sapphire */ + error =wait_event_interruptible (opal_log_wait, + opal_log_available); +if (error) + goto out; +spin_lock_irqsave (&opal_elog_lock, flags); + }
Why should we wait for there to be a log message? If there's not one then there's not one and that's fine.
I also wonder if we really need total_log_size and opal_log_available, this information seems readily available from the list of events.
Instead, for notification (as i understand it) we should be using sysfs_notify() from kernel and then in userspace we can just call select() to wait for something to happen.
Quoted 2 lines
+/*
+ * Pre-allocate a buffer to hold handful of error logs until user space
[ 5 more citation lines. Click/Enter to show. ]
arch/powerpc/platforms/powernv/opal-elog.c line 262
Quoted 8 lines
+ * consumes it.
+ */arch/powerpc/platforms/powernv/opal-elog.c new file +6
-0+static int init_err_log_buffer (void ) +{ +int i =0 ; +struct opal_err_log *buf_ptr; + + buf_ptr =vmalloc (sizeof (struct opal_err_log ) *MAX_NUM_RECORD );
This means we constantly use 128 * sizeof(struct opal_err_log) which equates to somewhere north of 2MB of memory (due to list overhead).
I don't think we need to statically allocate this, we can probably just allocate on-demand as in a typical system you're probably quite unlikely to have too many of these sitting around (besides, if for whatever reason we cannot allocate memory at some point, that's okay because we can read it again later).
Oh, I forgot to mention, since this is sysfs there should be documentation in Documentation/ABI/ somewhere.
Quoted 3 lines · Stewart Smith
Quoted 2 lines · Mahesh J Salgaonkar
This patch adds support to read error logs from OPAL and export them to userspace through sysfs interface
/sys/firmware/opa/opal-elog.
Hi Stewart,
Thanks for the review. This code definitely needs improvement.
Quoted 5 lines
I think we could provide a better interface with instead having a file per log message appear in sysfs. We're never going to have more than 128 of these at any one time on the Linux side, so it's not going to bee too many files.
It is not just about 128 files, we may be adding/removing sysfs node for every new log id that gets informed to kernel and ack-ed. In worst case, when we have flood of elog errors with user daemon consuming it and ack-ing back to get ready for next log in a tight poll, we may continuously add/remove the sysfs node for each new <id>.
Quoted 39 lines
e.g. /sys/firmware/opal/elog/<id>
that way, any new file in
/sys/firmware/opal/elog/means there's a new log entry available. I believe there'sTo ack a log, you could just echo 'ack' to the file.
The other option woudl be to more closely follow what sysfs is meant to be - ascii text. This would mean having more (any) of the parser in kernel for the error logs - which may/may not be a bad idea.
However, it would make the end user code for consuming them much much simpler, and that may be a good thing.
Having some way of getting some information out without a userspace parser is probably good though, I'm pretty sure having only a binary interface in /sys is at least partially frowned upon.
Quoted 5 lines
This is what user space tool would do:
- Read error log from/sys/firmware/opa/opal-elog.
- Save it to the disk.
- Send an acknowledgement on successful consumption by writing error log id to/sys/firmware/opa/opal-elog-ack.A userspace tool may want to explicitly *not* ack the log too, or only ack some entries, so the interface sohuld be sane for this use case too.
e.g. we could display them in petitboot.
arch/powerpc/platforms/powernv/opal-elog.c
Quoted 2 lines
arch/powerpc/platforms/powernv/opal-elog.c +0
-0[ 2 more citation lines. Click/Enter to show. ]
Quoted 5 lines
new file mode 100644
index 0000000..fc891aearch/powerpc/platforms/powernv/opal-elog.c new file +0
-0@@ -0,0 +1,309 @@<snip>
Quoted 4 lines
arch/powerpc/platforms/powernv/opal-elog.c line 23
Quoted 2 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +2
-0+/* Maximum size of a single log on FSP is 16KB */ +#define OPAL_MAX_ERRLOG_SIZE 16384I've seen some conflicting things on this - is it 2kb or 16kb?
We choose 16kb because we want to pull all the log data and not partial.
Quoted 7 lines
arch/powerpc/platforms/powernv/opal-elog.c line 30
Quoted 5 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +4
-0+ +struct opal_err_log { +struct list_head link; +uint64_t opal_log_id;why is this
uint64_tand notuint32_t? It appears that the log id is 32bits.
Agree, This needs to be changed to uint_32.
Quoted 26 lines
arch/powerpc/platforms/powernv/opal-elog.c line 36
Quoted 7 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +6
-0+size_t opal_log_size; +uint8_t data[OPAL_MAX_ERRLOG_SIZE ]; +}; + +/* Pre-allocated temp buffer to pull error log from opal. */ +static uint8_t err_log_data[OPAL_MAX_ERRLOG_SIZE ];Why do we need temporary space? Why not just store directly into struct
opal_err_log?arch/powerpc/platforms/powernv/opal-elog.c line 38
Quoted 2 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +2
-0+/* Protect err_log_data buf */ +static DEFINE_MUTEX (err_log_data_mutex);[ 15 more citation lines. Click/Enter to show. ]
Quoted 12 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +12
-0+ +static uint64_t total_log_size; +static bool opal_log_available; +static LIST_HEAD (elog_list); +static LIST_HEAD (elog_ack_list); + +/* lock to protect elog_list and elog-ack_list. */ +static DEFINE_SPINLOCK (opal_elog_lock); + +static DECLARE_WAIT_QUEUE_HEAD (opal_log_wait); + +/*
Quoted 8 lines
Quoted 6 lines
+ * Interface for user to acknowledge the error log.
+ *
+ * Once user acknowledge the log, we delete that record entry from the
+ * list and move it ack list.
+ */
+voidopal_elog_ack(uint64_t ack_id)s/ack_id/log_id/
Yup. makes sense.
Quoted 102 lines
arch/powerpc/platforms/powernv/opal-elog.c
Quoted 3 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +2
-0+ +static ssize_t elog_ack_store(struct kobject *kobj,[ 7 more citation lines. Click/Enter to show. ]
arch/powerpc/platforms/powernv/opal-elog.c line 94
Quoted 10 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +10
-0+struct kobj_attribute *attr, + const char *buf, size_t count) +{ + uint32_t log_ack_id; + log_ack_id = *(uint32_t *) buf; + +/* send acknowledgment to FSP */ +opal_elog_ack (log_ack_id); +return 0 ; +}This function has a few problems:
Consider the following actions:
$ echo 1 > /sys/firmware/opal/opal-elog-ack $ echo 'abcde' > /sys/firmware/opal/opal-elog-ackThe former will read undefined memory and the latter will make a kernel thread, rsyslogd and systemd-journal all each a CPU each.
Basically, the problems are:
1) not endian safe
2) not following store API of returning nr bytes read
3) binary interface. Use sscanf to read numbers instead.Quoted 2 lines
+/*
+ * Show error log records to user.[ 9 more citation lines. Click/Enter to show. ]
arch/powerpc/platforms/powernv/opal-elog.c
Quoted 12 lines
+ */
arch/powerpc/platforms/powernv/opal-elog.c new file +11
-0+static ssize_t opal_elog_show (struct file *filp,struct kobject *kobj, +struct bin_attribute *bin_attr,char *buf, +loff_t pos,size_t count) +{ +unsigned long flags; +struct opal_err_log *record, *next; +size_t size =0 ; +size_t data_to_copy =0 ; +int error =0 ; + +/* Display one log@a time. */ use words, not @.
arch/powerpc/platforms/powernv/opal-elog.c line 111
Quoted 2 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +2
-0+if (count >OPAL_MAX_ERRLOG_SIZE ) + count =OPAL_MAX_ERRLOG_SIZE ;[ 23 more citation lines. Click/Enter to show. ]
Quoted 16 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +16
-0+spin_lock_irqsave (&opal_elog_lock, flags); +/* Align the pos to point within total errlog size. */ +if (total_log_size && pos > total_log_size) + pos = pos % total_log_size; + +/* +* if pos goes beyond total_log_size then we know we don't have any +* new record to show. +*/ +if (total_log_size ==0 || pos >= total_log_size) { + opal_log_available =0 ; +if (filp->f_flags &O_NONBLOCK ) { +spin_unlock_irqrestore (&opal_elog_lock, flags); + error = -EAGAIN ; + goto out; + }arch/powerpc/platforms/powernv/opal-elog.c line 138
Quoted 10 lines
arch/powerpc/platforms/powernv/opal-elog.c new file +10
-0+spin_unlock_irqrestore (&opal_elog_lock, flags); + pos =0 ; + +/* Wait until we get log from sapphire */ + error =wait_event_interruptible (opal_log_wait, + opal_log_available); +if (error) + goto out; +spin_lock_irqsave (&opal_elog_lock, flags); + }Why should we wait for there to be a log message? If there's not one then there's not one and that's fine.
I also wonder if we really need
total_log_sizeandopal_log_available, this information seems readily available from the list of events.Instead, for notification (as i understand it) we should be using
sysfs_notify()from kernel and then in userspace we can just callselect()to wait for something to happen.Quoted 2 lines
+/*
+ * Pre-allocate a buffer to hold handful of error logs until user space[ 5 more citation lines. Click/Enter to show. ]
arch/powerpc/platforms/powernv/opal-elog.c line 262
Quoted 8 lines
+ * consumes it.
+ */arch/powerpc/platforms/powernv/opal-elog.c new file +6
-0+static int init_err_log_buffer (void ) +{ +int i =0 ; +struct opal_err_log *buf_ptr; + + buf_ptr =vmalloc (sizeof (struct opal_err_log ) *MAX_NUM_RECORD );This means we constantly use 128 *
sizeof(struct opal_err_log)which equates to somewhere north of 2MB of memory (due to list overhead).
Quoted 5 lines
I don't think we need to statically allocate this, we can probably just allocate on-demand as in a typical system you're probably quite unlikely to have too many of these sitting around (besides, if for whatever reason we cannot allocate memory at some point, that's okay because we can read it again later).
The reason we choose to go for static allocation is, we can not afford to drop or delay a critical error log due to memory allocation failure. OR we can keep static allocations for critical errors and follow dynamic allocation for informative error logs. What do you say?
Thanks,
-Mahesh.
Quoted 10 lines · Mahesh Jagannath Salgaonkar
Quoted 4 lines
I think we could provide a better interface with instead having a file per log message appear in sysfs. We're never going to have more than 128 of these at any one time on the Linux side, so it's not going to bee too many files.
It is not just about 128 files, we may be adding/removing sysfs node for every new log id that gets informed to kernel and ack-ed. In worst case, when we have flood of elog errors with user daemon consuming it and ack-ing back to get ready for next log in a tight poll, we may continuously add/remove the sysfs node for each new <id>.
Do we ever get a storm of hundreds/thousands of them though? If many come it at once userspace may just be woken up one or two times, as it would just select() and wait for events.
Quoted 4 lines
Quoted 1 line
I've seen some conflicting things on this - is it 2kb or 16kb?
We choose 16kb because we want to pull all the log data and not partial.
So the max log size for any one entry is in fact 16kb?
Quoted 9 lines
Quoted 8 lines
This means we constantly use 128 *
sizeof(struct opal_err_log)which equates to somewhere north of 2MB of memory (due to list overhead).I don't think we need to statically allocate this, we can probably just allocate on-demand as in a typical system you're probably quite unlikely to have too many of these sitting around (besides, if for whatever reason we cannot allocate memory at some point, that's okay because we can read it again later).
Quoted 4 lines
The reason we choose to go for static allocation is, we can not afford to drop or delay a critical error log due to memory allocation failure. OR we can keep static allocations for critical errors and follow dynamic allocation for informative error logs. What do you say?
Userspace is probably going to have to do IO to get the log and ack it, so it's probably not a huge problem - if we can't allocate a few kb in a couple of attempts then we likely have bigger problems.
If we were going to have a sustained amount of hundreds/thousands of these per second then perhaps we'd have other issues, but from what I understand we're probably only going to have a handful per year on a typical system? (I am, of course, not talking about our dev systems, which are rather atypical :)
I'll likely have a patch today that shows kind of what I mean.
PATCH 1/1 powerpc/powernv: Read OPAL error log and export it through sysfs
Based on a patch by: Mahesh Salgaonkar <[email protected]>
This patch adds support to read error logs from OPAL and export them to userspace through a sysfs interface.
We export each log entry as a directory in /sys/firmware/opal/elog/
Currently, OPAL will buffer up to 128 error log records, we don't need to have any knowledge of this limit on the Linux side as that is actually largely transparent to us.
Each error log entry has the following files: id, type, acknowledge, raw. Currently we just export the raw binary error log in the 'raw' attribute. In a future patch, we may parse more of the error log to make it a bit easier for userspace (e.g. to be able to display a brief summary in petitboot without having to have a full parser).
If we have >128 logs from OPAL, we'll only be notified of 128 until userspace starts acknowledging them. This limitation may be lifted in the future and with this patch, that should "just work" from the linux side.
A userspace daemon should:
- wait for error log entries using normal mechanisms (we announce creation)
- read error log entry
- save error log entry safely to disk
- acknowledge the error log entry
- rinse, repeat.
On the Linux side, we read the error log when we're notified of it. This possibly isn't ideal as it would be better to only read them on-demand. However, this doesn't really work with current OPAL interface, so we read the error log immediately when notified at the moment.
I've tested this pretty extensively and am rather confident that the linux side of things works rather well. There is currently an issue with the service processor side of things for >128 error logs though.
--- Documentation/ABI/stable/sysfs-firmware-opal-elog | 60 ++++ arch/powerpc/include/asm/opal.h | 13 + arch/powerpc/platforms/powernv/Makefile | 2 +- arch/powerpc/platforms/powernv/opal-elog.c | 312 +++++++++++++++++++++ arch/powerpc/platforms/powernv/opal-wrappers.S | 5 + arch/powerpc/platforms/powernv/opal.c | 2 + 6 files changed, 393 insertions(+), 1 deletion(-) create mode 100644 Documentation/ABI/stable/sysfs-firmware-opal-elog create mode 100644 arch/powerpc/platforms/powernv/opal-elog.c
Documentation/ABI/stable/sysfs-firmware-opal-elog new file +60 -0
@@ -0,0 +1,60 @@ +What: /sys/firmware/opal/elog +Date: Feb 2014 +Contact: Stewart Smith <[email protected]> +Description: + This directory exposes error log entries retrieved + through the OPAL firmware interface. + + Each error log is identified by a unique ID and will + exist until explicitly acknowledged to firmware. + + Each log entry has a directory in /sys/firmware/opal/elog. + + Log entries may be purged by the service processor + before retrieved by firmware or retrieved/acknowledged by + Linux if there is no room for more log entries. + + In the event that Linux has retrieved the log entries + but not explicitly acknowledged them to firmware and + the service processor needs more room for log entries, + the only remaining copy of a log message may be in + Linux. + + Typically, a user space daemon will monitor for new + entries, read them out and acknowledge them. + + The service processor may be able to store more log + entries than firmware can, so after you acknowledge + an event from Linux you may instantly get another one + from the queue that was generated some time in the past. + + The raw log format is a binary format. We currently + do not parse this at all in kernel, leaving it up to + user space to solve the problem. In future, we may + do more parsing in kernel and add more files to make + it easier for simple user space processes to extract + more information. + + For each log entry (directory), there are the following + files: + + id: An ASCII representation of the ID of the + error log, in hex - e.g. "0x01". + + type: An ASCII representation of the type id and + description of the type of error log. + Currently just "0x00 PEL" - platform error log. + In the future there may be additional types. + + raw: A read-only binary file that can be read + to get the raw log entry. These are + <16kb, often just hundreds of bytes and + "average" 2kb. + + acknowledge: Writing 'ack' to this file will acknowledge + the error log to firmware (and in turn + the service processor, if applicable). + Shortly after acknowledging it, the log + entry will be removed from sysfs. + Reading this file will list the supported + operations (curently just acknowledge).
arch/powerpc/include/asm/opal.h +13 -0
@@ -151,6 +151,11 @@ extern int opal_enter_rtas(struct rtas_args *args,#define OPAL_LPC_READ 67#define OPAL_LPC_WRITE 68#define OPAL_RETURN_CPU 69 +#define OPAL_ELOG_READ 71 +#define OPAL_ELOG_WRITE 72 +#define OPAL_ELOG_ACK 73 +#define OPAL_ELOG_RESEND 74 +#define OPAL_ELOG_SIZE 75#define OPAL_FLASH_VALIDATE 76#define OPAL_FLASH_MANAGE 77#define OPAL_FLASH_UPDATE 78
@@ -823,6 +828,13 @@ int64_t opal_lpc_write(uint32_t chip_id, enum OpalLPCAddressType addr_type, uint32_t addr, uint32_t data, uint32_t sz);int64_t opal_lpc_read (uint32_t chip_id,enum OpalLPCAddressType addr_type,uint32_t addr,__be32 *data,uint32_t sz); + +int64_t opal_read_elog (uint64_t buffer,size_t size,uint64_t log_id); +int64_t opal_get_elog_size (uint64_t *log_id,size_t *size,uint64_t *elog_type); +int64_t opal_write_elog (uint64_t buffer,uint64_t size,uint64_t offset); +int64_t opal_send_ack_elog (uint64_t log_id); +void opal_resend_pending_logs (void ); +int64_t opal_validate_flash (uint64_t buffer,uint32_t *size,uint32_t *result);int64_t opal_manage_flash (uint8_t op);int64_t opal_update_flash (uint64_t blk_list);
@@ -861,6 +873,7 @@ extern void opal_get_rtc_time(struct rtc_time *tm);extern unsigned long opal_get_boot_time (void );extern void opal_nvram_init (void );extern void opal_flash_init (void ); +extern int opal_elog_init (void );extern int opal_machine_check (struct pt_regs *regs);
arch/powerpc/platforms/powernv/Makefile +1 -1
@@ -1,6 +1,6 @@ obj-y += setup.o opal-takeover.o opal-wrappers.o opal.o obj-y += opal-rtc.o opal-nvram.o opal-lpc.o opal-flash.o -obj-y += rng.o +obj-y += rng.o opal-elog.o obj-$(CONFIG_SMP) += smp.o obj-$(CONFIG_PCI) += pci.o pci-p5ioc2.o pci-ioda.o
arch/powerpc/platforms/powernv/opal-elog.c new file +312 -0
312 lines not on this page · raw message
arch/powerpc/platforms/powernv/opal-wrappers.S +5 -0
@@ -123,6 +123,11 @@ OPAL_CALL(opal_xscom_write, OPAL_XSCOM_WRITE); OPAL_CALL(opal_lpc_read, OPAL_LPC_READ); OPAL_CALL(opal_lpc_write, OPAL_LPC_WRITE); OPAL_CALL(opal_return_cpu, OPAL_RETURN_CPU); +OPAL_CALL(opal_read_elog, OPAL_ELOG_READ); +OPAL_CALL(opal_send_ack_elog, OPAL_ELOG_ACK); +OPAL_CALL(opal_get_elog_size, OPAL_ELOG_SIZE); +OPAL_CALL(opal_resend_pending_logs, OPAL_ELOG_RESEND); +OPAL_CALL(opal_write_elog, OPAL_ELOG_WRITE); OPAL_CALL(opal_validate_flash, OPAL_FLASH_VALIDATE); OPAL_CALL(opal_manage_flash, OPAL_FLASH_MANAGE); OPAL_CALL(opal_update_flash, OPAL_FLASH_UPDATE);
arch/powerpc/platforms/powernv/opal.c +2 -0
@@ -472,6 +472,8 @@ static int __init opal_init(void)/* Create "opal" kobject under /sys/firmware */ rc =opal_sysfs_init ();if (rc ==0 ) { +/* Setup error log interface */ + rc =opal_elog_init ();/* Setup code update interface */ opal_flash_init (); }
Signature · 1 line
1.7.10.4
Re: [PATCH] powerpc/powernv: Read OPAL error log and export it through sysfs
Quoted 133 lines · Stewart Smith
Based on a patch by: Mahesh Salgaonkar <[email protected]>
This patch adds support to read error logs from OPAL and export them to userspace through a sysfs interface.
We export each log entry as a directory in
/sys/firmware/opal/elog/Currently, OPAL will buffer up to 128 error log records, we don't need to have any knowledge of this limit on the Linux side as that is actually largely transparent to us.
Each error log entry has the following files: id, type, acknowledge, raw. Currently we just export the raw binary error log in the 'raw' attribute. In a future patch, we may parse more of the error log to make it a bit easier for userspace (e.g. to be able to display a brief summary in petitboot without having to have a full parser).
If we have >128 logs from OPAL, we'll only be notified of 128 until userspace starts acknowledging them. This limitation may be lifted in the future and with this patch, that should "just work" from the linux side.
A userspace daemon should:
- wait for error log entries using normal mechanisms (we announce creation)
- read error log entry
- save error log entry safely to disk
- acknowledge the error log entry
- rinse, repeat.On the Linux side, we read the error log when we're notified of it. This possibly isn't ideal as it would be better to only read them on-demand. However, this doesn't really work with current OPAL interface, so we read the error log immediately when notified at the moment.
I've tested this pretty extensively and am rather confident that the linux side of things works rather well. There is currently an issue with the service processor side of things for >128 error logs though.
Signed-off-by Stewart Smith <[email protected]>--- Documentation/ABI/stable/sysfs-firmware-opal-elog | 60 ++++ arch/powerpc/include/asm/opal.h | 13 + arch/powerpc/platforms/powernv/Makefile | 2 +- arch/powerpc/platforms/powernv/opal-elog.c | 312 +++++++++++++++++++++ arch/powerpc/platforms/powernv/opal-wrappers.S | 5 + arch/powerpc/platforms/powernv/opal.c | 2 + 6 files changed, 393 insertions(+), 1 deletion(-)create mode 100644
Documentation/ABI/stable/sysfs-firmware-opal-elogcreate mode 100644arch/powerpc/platforms/powernv/opal-elog.cDocumentation/ABI/stable/sysfs-firmware-opal-elog new file +60
-0@@ -0,0 +1,60 @@ +What: /sys/firmware/opal/elog +Date: Feb 2014 +Contact: Stewart Smith <[email protected]> +Description: + This directory exposes error log entries retrieved + through the OPAL firmware interface. + + Each error log is identified by a unique ID and will + exist until explicitly acknowledged to firmware. + + Each log entry has a directory in /sys/firmware/opal/elog. + + Log entries may be purged by the service processor + before retrieved by firmware or retrieved/acknowledged by + Linux if there is no room for more log entries. + + In the event that Linux has retrieved the log entries + but not explicitly acknowledged them to firmware and + the service processor needs more room for log entries, + the only remaining copy of a log message may be in + Linux. + + Typically, a user space daemon will monitor for new + entries, read them out and acknowledge them. + + The service processor may be able to store more log + entries than firmware can, so after you acknowledge + an event from Linux you may instantly get another one + from the queue that was generated some time in the past. + + The raw log format is a binary format. We currently + do not parse this at all in kernel, leaving it up to + user space to solve the problem. In future, we may + do more parsing in kernel and add more files to make + it easier for simple user space processes to extract + more information. + + For each log entry (directory), there are the following + files: + + id: An ASCII representation of the ID of the + error log, in hex - e.g. "0x01". + + type: An ASCII representation of the type id and + description of the type of error log. + Currently just "0x00 PEL" - platform error log. + In the future there may be additional types. + + raw: A read-only binary file that can be read + to get the raw log entry. These are + <16kb, often just hundreds of bytes and + "average" 2kb. + + acknowledge: Writing 'ack' to this file will acknowledge + the error log to firmware (and in turn + the service processor, if applicable). + Shortly after acknowledging it, the log + entry will be removed from sysfs. + Reading this file will list the supported + operations (curently just acknowledge).arch/powerpc/include/asm/opal.h +5
-0@@ -151,6 +151,11 @@ extern int opal_enter_rtas(struct rtas_args *args,#define OPAL_LPC_READ 67#define OPAL_LPC_WRITE 68#define OPAL_RETURN_CPU 69 +#define OPAL_ELOG_READ 71 +#define OPAL_ELOG_WRITE 72 +#define OPAL_ELOG_ACK 73 +#define OPAL_ELOG_RESEND 74 +#define OPAL_ELOG_SIZE 75#define OPAL_FLASH_VALIDATE 76#define OPAL_FLASH_MANAGE 77#define OPAL_FLASH_UPDATE 78
arch/powerpc/include/asm/opal.h int64_t opal_lpc_write(uint32_t chip_id, enum OpalLPCAddressType addr_type, · line 835
Quoted 8 lines
arch/powerpc/include/asm/opal.h +5
-0@@ -823,6 +828,13 @@ int64_t opal_lpc_write(uint32_t chip_id, enum OpalLPCAddressType addr_type, uint32_t addr, uint32_t data, uint32_t sz);int64_t opal_lpc_read (uint32_t chip_id,enum OpalLPCAddressType addr_type,uint32_t addr,__be32 *data,uint32_t sz); + +int64_t opal_read_elog (uint64_t buffer,size_t size,uint64_t log_id); +int64_t opal_get_elog_size (uint64_t *log_id,size_t *size,uint64_t *elog_type); +int64_t opal_write_elog (uint64_t buffer,uint64_t size,uint64_t offset); +int64_t opal_send_ack_elog (uint64_t log_id);
Stewart,
Why are you creating 64bit log ID when actual ID is 32bit ?
Rest looks good.
-Vasant
Quoted 373 lines
arch/powerpc/include/asm/opal.h +3
-0+void opal_resend_pending_logs (void ); +int64_t opal_validate_flash (uint64_t buffer,uint32_t *size,uint32_t *result);int64_t opal_manage_flash (uint8_t op);int64_t opal_update_flash (uint64_t blk_list);@@ -861,6 +873,7 @@ extern void opal_get_rtc_time(struct rtc_time *tm);extern unsigned long opal_get_boot_time (void );extern void opal_nvram_init (void );extern void opal_flash_init (void ); +extern int opal_elog_init (void );extern int opal_machine_check (struct pt_regs *regs);arch/powerpc/platforms/powernv/Makefile +1
-1@@ -1,6 +1,6 @@ obj-y += setup.o opal-takeover.o opal-wrappers.o opal.o obj-y += opal-rtc.o opal-nvram.o opal-lpc.o opal-flash.o -obj-y += rng.o +obj-y += rng.o opal-elog.o obj-$(CONFIG_SMP) += smp.o obj-$(CONFIG_PCI) += pci.o pci-p5ioc2.o pci-ioda.oarch/powerpc/platforms/powernv/opal-elog.c new file +312
-0@@ -0,0 +1,312 @@ +/* +* Error log support on PowerNV. +* +* Copyright 2013,2014 IBM Corp. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version +* 2 of the License, or (at your option) any later version. +*/ +#include <linux/kernel.h> +#include <linux/init.h> +#include <linux/of.h> +#include <linux/slab.h> +#include <linux/sysfs.h> +#include <linux/fs.h> +#include <linux/vmalloc.h> +#include <linux/fcntl.h> +#include <asm/uaccess.h> +#include <asm/opal.h> + +struct elog_obj { +struct kobject kobj; +struct bin_attribute raw_attr; +uint64_t id; +uint64_t type; +size_t size; +char *buffer; +}; +#define to_elog_obj (x) container_of(x, struct elog_obj, kobj) + +struct elog_attribute { +struct attribute attr; +ssize_t (*show)(struct elog_obj *elog,struct elog_attribute *attr, +char *buf); +ssize_t (*store)(struct elog_obj *elog,struct elog_attribute *attr, +const char *buf,size_t count); +}; +#define to_elog_attr (x) container_of(x, struct elog_attribute, attr) + +static ssize_t elog_id_show (struct elog_obj *elog_obj, +struct elog_attribute *attr, +char *buf) +{ +return sprintf (buf,"0x%llx\n" , elog_obj->id); +} + +static const char *elog_type_to_string (uint64_t type) +{ +switch (type) { +case 0 :return "PEL" ; +default :return "unknown" ; + } +} + +static ssize_t elog_type_show (struct elog_obj *elog_obj, +struct elog_attribute *attr, +char *buf) +{ +return sprintf (buf,"0x%llx %s\n" , + elog_obj->type, +elog_type_to_string (elog_obj->type)); +} + +static ssize_t elog_ack_show (struct elog_obj *elog_obj, +struct elog_attribute *attr, +char *buf) +{ +return sprintf (buf,"ack - acknowledge log message\n" ); +} + +static void delay_release_kobj (void *kobj) +{ +kobject_put ((struct kobject *)kobj); +} + +static ssize_t elog_ack_store (struct elog_obj *elog_obj, +struct elog_attribute *attr, +const char *buf, +size_t count) +{ +opal_send_ack_elog (elog_obj->id); +sysfs_schedule_callback (&elog_obj->kobj, delay_release_kobj, + &elog_obj->kobj,THIS_MODULE ); +return count; +} + +static struct elog_attribute id_attribute = +__ATTR (id,0666 , elog_id_show,NULL ); +static struct elog_attribute type_attribute = +__ATTR (type,0666 , elog_type_show,NULL ); +static struct elog_attribute ack_attribute = +__ATTR (acknowledge,0660 , elog_ack_show, elog_ack_store); + +static struct kset *elog_kset; + +static ssize_t elog_attr_show (struct kobject *kobj, +struct attribute *attr, +char *buf) +{ +struct elog_attribute *attribute; +struct elog_obj *elog; + + attribute =to_elog_attr (attr); + elog =to_elog_obj (kobj); + +if (!attribute->show) +return -EIO ; + +return attribute->show (elog, attribute, buf); +} + +static ssize_t elog_attr_store (struct kobject *kobj, +struct attribute *attr, +const char *buf,size_t len) +{ +struct elog_attribute *attribute; +struct elog_obj *elog; + + attribute =to_elog_attr (attr); + elog =to_elog_obj (kobj); + +if (!attribute->store) +return -EIO ; + +return attribute->store (elog, attribute, buf, len); +} + +static const struct sysfs_ops elog_sysfs_ops = { + .show = elog_attr_show, + .store = elog_attr_store, +}; + +static void elog_release (struct kobject *kobj) +{ +struct elog_obj *elog; + + elog =to_elog_obj (kobj); +kfree (elog->buffer); +kfree (elog); +} + +static struct attribute *elog_default_attrs[] = { + &id_attribute.attr, + &type_attribute.attr, + &ack_attribute.attr, +NULL , +}; + +static struct kobj_type elog_ktype = { + .sysfs_ops = &elog_sysfs_ops, + .release = &elog_release, + .default_attrs = elog_default_attrs, +}; + +/* Maximum size of a single log on FSP is 16KB */ +#define OPAL_MAX_ERRLOG_SIZE 16384 + +static ssize_t raw_attr_read (struct file *filep,struct kobject *kobj, +struct bin_attribute *bin_attr, +char *buffer,loff_t pos,size_t count) +{ +int opal_rc; + +struct elog_obj *elog =to_elog_obj (kobj); + +/* We may have had an error reading before, so let's retry */ +if (!elog->buffer) { + elog->buffer =kzalloc (elog->size,GFP_KERNEL ); +if (!elog->buffer) +return -EIO ; + + opal_rc =opal_read_elog (__pa (elog->buffer), + elog->size, elog->id); +if (opal_rc !=OPAL_SUCCESS ) { +pr_err ("ELOG: log read failed for log-id=%llx\n" , + elog->id); +kfree (elog->buffer); + elog->buffer =NULL ; +return -EIO ; + } + } + +memcpy (buffer, elog->buffer + pos, count); + +return count; +} + +static struct elog_obj *create_elog_obj (uint64_t id,size_t size,uint64_t type) +{ +struct elog_obj *elog; +int rc; + + elog =kzalloc (sizeof (*elog),GFP_KERNEL ); +if (!elog) +return NULL ; + + elog->kobj.kset = elog_kset; + +kobject_init (&elog->kobj, &elog_ktype); + +sysfs_bin_attr_init (&elog->raw_attr); + + elog->raw_attr.attr.name ="raw" ; + elog->raw_attr.attr.mode =0400 ; + elog->raw_attr.size = size; + elog->raw_attr.read = raw_attr_read; + + elog->id = id; + elog->size = size; + elog->type = type; + + elog->buffer =kzalloc (elog->size,GFP_KERNEL ); + +if (elog->buffer) { + rc =opal_read_elog (__pa (elog->buffer), + elog->size, elog->id); +if (rc !=OPAL_SUCCESS ) { +pr_err ("ELOG: log read failed for log-id=%llx\n" , + elog->id); +kfree (elog->buffer); + elog->buffer =NULL ; + } + } + + rc =kobject_add (&elog->kobj,NULL ,"0x%llx" , id); +if (rc) { +kobject_put (&elog->kobj); +return NULL ; + } + + rc =sysfs_create_bin_file (&elog->kobj, &elog->raw_attr); +if (rc) { +kobject_put (&elog->kobj); +return NULL ; + } + +kobject_uevent (&elog->kobj,KOBJ_ADD ); + +return elog; +} + +static void elog_work_fn (struct work_struct *work) +{ +size_t elog_size; +uint64_t log_id; +uint64_t elog_type; +int rc; +char name[2 +16 +1 ]; + + rc =opal_get_elog_size (&log_id, &elog_size, &elog_type); +if (rc !=OPAL_SUCCESS ) { +pr_err ("ELOG: Opal log read failed\n" ); +return ; + } + +BUG_ON (elog_size >OPAL_MAX_ERRLOG_SIZE ); + +if (elog_size >=OPAL_MAX_ERRLOG_SIZE ) + elog_size =OPAL_MAX_ERRLOG_SIZE ; + +sprintf (name,"0x%llx" , log_id); + +/* we may get notified twice, let's handle +* that gracefully and not create two conflicting +* entries. +*/ +if (kset_find_obj (elog_kset, name)) +return ; + +create_elog_obj (log_id, elog_size, elog_type); +} + +static DECLARE_WORK(elog_work, elog_work_fn); + +static int elog_event (struct notifier_block *nb, +unsigned long events,void *change) +{ +/* check for error log event */ +if (events &OPAL_EVENT_ERROR_LOG_AVAIL ) +schedule_work (&elog_work); +return 0 ; +} + +static struct notifier_block elog_nb = { + .notifier_call = elog_event, + .next =NULL , + .priority =0 +}; + +int __init opal_elog_init (void ) +{ +int rc =0 ; + + elog_kset =kset_create_and_add ("elog" ,NULL , opal_kobj); +if (!elog_kset) { +pr_warn ("%s: failed to create elog kset\n" , __func__); +return -1 ; + } + + rc =opal_notifier_register (&elog_nb); +if (rc) { +pr_err ("%s: Can't register OPAL event notifier (%d)\n" , + __func__, rc); +return rc; + } + +/* We are now ready to pull error logs from opal. */ +opal_resend_pending_logs (); + +return 0 ; +}arch/powerpc/platforms/powernv/opal-wrappers.S +5
-0@@ -123,6 +123,11 @@ OPAL_CALL(opal_xscom_write, OPAL_XSCOM_WRITE); OPAL_CALL(opal_lpc_read, OPAL_LPC_READ); OPAL_CALL(opal_lpc_write, OPAL_LPC_WRITE); OPAL_CALL(opal_return_cpu, OPAL_RETURN_CPU); +OPAL_CALL(opal_read_elog, OPAL_ELOG_READ); +OPAL_CALL(opal_send_ack_elog, OPAL_ELOG_ACK); +OPAL_CALL(opal_get_elog_size, OPAL_ELOG_SIZE); +OPAL_CALL(opal_resend_pending_logs, OPAL_ELOG_RESEND); +OPAL_CALL(opal_write_elog, OPAL_ELOG_WRITE); OPAL_CALL(opal_validate_flash, OPAL_FLASH_VALIDATE); OPAL_CALL(opal_manage_flash, OPAL_FLASH_MANAGE); OPAL_CALL(opal_update_flash, OPAL_FLASH_UPDATE);arch/powerpc/platforms/powernv/opal.c +2
-0@@ -472,6 +472,8 @@ static int __init opal_init(void)/* Create "opal" kobject under /sys/firmware */ rc =opal_sysfs_init ();if (rc ==0 ) { +/* Setup error log interface */ + rc =opal_elog_init ();/* Setup code update interface */ opal_flash_init (); }
Re: [PATCH] powerpc/powernv: Read OPAL error log and export it through sysfs
Quoted 5 lines · Vasant Hegde
Quoted 1 line
+int64_t
opal_send_ack_elog(uint64_t log_id);Stewart,
Why are you creating 64bit log ID when actual ID is 32bit ?
IIRC it's what OPAL gives us, even though FSP MBOX spec says 32bit.
Re: [PATCH] powerpc/powernv: Read OPAL error log and export it through sysfs
Quoted 9 lines · Stewart Smith
Quoted 5 lines · Vasant Hegde
Quoted 1 line
+int64_t
opal_send_ack_elog(uint64_t log_id);Stewart,
Why are you creating 64bit log ID when actual ID is 32bit ?
IIRC it's what OPAL gives us, even though FSP MBOX spec says 32bit.
Stewart,
Better ask OPAL folks to fix in firmware ?
-Vasant
Re: [PATCH] powerpc/powernv: Read OPAL error log and export it through sysfs
In reply to Stewart SmithQuoted 9 lines · Stewart Smith
Quoted 5 lines · Vasant Hegde
Quoted 1 line
+int64_t
opal_send_ack_elog(uint64_t log_id);Stewart,
Why are you creating 64bit log ID when actual ID is 32bit ?
IIRC it's what OPAL gives us, even though FSP MBOX spec says 32bit.
Stewart,
Better ask OPAL folks to fix in firmware ?
-Vasant
Re: [PATCH] powerpc/powernv: Read OPAL error log and export it through sysfs
Quoted 6 lines · Vasant Hegde
Quoted 5 lines · Stewart Smith
Quoted 4 lines · Vasant Hegde
Quoted 1 line
+int64_t
opal_send_ack_elog(uint64_t log_id);Stewart,
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
Why are you creating 64bit log ID when actual ID is 32bit ?
IIRC it's what OPAL gives us, even though FSP MBOX spec says 32bit.
Stewart,
Better ask OPAL folks to fix in firmware ?
Why bother ? That way if future versions of OPAL want to use 64-bit IDs, they can.
Cheers,
Ben.
Re: [PATCH] powerpc/powernv: Read OPAL error log and export it through sysfs
Quoted 12 lines · Benjamin Herrenschmidt
Quoted 11 lines · Vasant Hegde
Quoted 9 lines · Stewart Smith
Quoted 5 lines · Vasant Hegde
Quoted 1 line
+int64_t
opal_send_ack_elog(uint64_t log_id);Stewart,
Why are you creating 64bit log ID when actual ID is 32bit ?
IIRC it's what OPAL gives us, even though FSP MBOX spec says 32bit.
Quoted 6 lines
Quoted 3 lines
Stewart,
Better ask OPAL folks to fix in firmware ?
Why bother ? That way if future versions of OPAL want to use 64-bit IDs, they can.
Yeah, that was my thought. The number of error logs on some POWER8 systems almost needs 64bit already :)