On Tuesday 16 April 2013 11:50 AM, Aruna Balakrishnaiah wrote:
Currently with this patchset, pstore is not supporting compression of
oops-messages
since it involves some changes in the pstore framework.
big_oops_buf will hold the large part of oops data which will be compressed
and put
to o
On Tuesday 16 April 2013 12:44 PM, Benjamin Herrenschmidt wrote:
On Tue, 2013-04-16 at 11:50 +0530, Aruna Balakrishnaiah wrote:
Sure. I will have one #ifdef for declarations and one for function
definitions.
Declarations generally don't need #ifdef's
Sorry by declarations I meant variable dec
On Tue, 2013-04-16 at 11:50 +0530, Aruna Balakrishnaiah wrote:
>
> Sure. I will have one #ifdef for declarations and one for function
> definitions.
Declarations generally don't need #ifdef's
Cheers,
Ben.
___
Linuxppc-dev mailing list
Linuxppc-dev@l
Hi Michael,
Thanks for reviewing my patches.
On Monday 15 April 2013 01:25 PM, Michael Ellerman wrote:
On Wed, Apr 10, 2013 at 12:53:03PM +0530, Aruna Balakrishnaiah wrote:
This patch exploits pstore infrastructure in power systems.
IBM's system p machines provide persistent storage for LPARs
On Wed, Apr 10, 2013 at 12:53:03PM +0530, Aruna Balakrishnaiah wrote:
> This patch exploits pstore infrastructure in power systems.
> IBM's system p machines provide persistent storage for LPARs
In the kernel we use "pseries" instead of "system p".
> through NVRAM. NVRAM's lnx,oops-log partition
This patch exploits pstore infrastructure in power systems.
IBM's system p machines provide persistent storage for LPARs
through NVRAM. NVRAM's lnx,oops-log partition is used to log
oops messages. In case pstore registration fails it will
fall back to kmsg_dump mechanism.
This patch will read/writ
