Benjamin Herrenschmidt writes:
> On Wed, 2014-03-05 at 08:56 +0530, Vasant Hegde wrote:
>> On 03/05/2014 07:26 AM, Stewart Smith wrote:
>> > Vasant Hegde writes:
>> >>> +int64_t opal_send_ack_elog(uint64_t log_id);
>> >>
>> >> Stewart,
>> >>
>> >> Why are you creating 64bit log ID when actual ID
On Wed, 2014-03-05 at 08:56 +0530, Vasant Hegde wrote:
> On 03/05/2014 07:26 AM, Stewart Smith wrote:
> > Vasant Hegde writes:
> >>> +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 g
On 03/05/2014 07:26 AM, Stewart Smith wrote:
Vasant Hegde writes:
+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 fi
On 03/05/2014 07:26 AM, Stewart Smith wrote:
Vasant Hegde writes:
+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 fi
Vasant Hegde writes:
>> +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.
___
Linuxppc-dev mailing list
Linuxp
On 02/28/2014 06:28 AM, Stewart Smith wrote:
Based on a patch by: Mahesh Salgaonkar
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 t
Based on a patch by: Mahesh Salgaonkar
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
Mahesh Jagannath Salgaonkar writes:
>> 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 jus
On 02/21/2014 05:41 AM, Stewart Smith wrote:
> Mahesh J Salgaonkar writes:
> > 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.
Mahesh J Salgaonkar writes:
> 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
From: Mahesh Salgaonkar
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/op
11 matches
Mail list logo
