From: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org, paulus@samba.org,
linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Cc: jkenisto@linux.vnet.ibm.com, tony.luck@intel.com,
keescook@chromium.org, mahesh@linux.vnet.ibm.com,
cbouatmailru@gmail.com, anton@samba.org, ccross@android.com
Subject: Re: [RFC PATCH 0/3] Nvram-to-pstore: compression support for oops data
Date: Thu, 06 Jun 2013 00:30:58 +0530 [thread overview]
Message-ID: <51AF8AEA.4030702@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130426094923.14323.80567.stgit@aruna-ThinkPad-T420>
Hi Ben,
There is no change in this patchset and it applies cleanly on top of
v4 of Nvram-to-pstorepatches.
> The patchset takes care of compressing oops messages while writing to NVRAM,
> so that more oops data can be captured in the given space.
>
> big_oops_buf (2.22 * oops_data_sz) is allocated for compression.
> oops_data_sz is oops header size less of oops partition size.
>
> Pstore will internally call kmsg_dump to capture messages from printk
> buffer. While returning the data to nvram it adds is own header.
>
> For compression:
> Register pstore with big_oops_buf.
>
> In case compression fails, copy header added by pstore and
> last oops_data_sz bytes (recent messages) of big_oops_buf to
> nvram for which we need to know header size.
>
> patch 01/03 will add a function in pstore to return the header size.
>
> pstore read callback of nvram will read the compressed data and return the
> decompressed data so that dmesg file (under /dev/pstore) is readable.
>
> In case decompression fails, instead of having the compressed data (junk) in the
> dmesg file it will skip and continue reading other partitions. This results in
> absence of dmesg file but will still have files relating to other parititons.
>
>
> ---
>
> Aruna Balakrishnaiah (3):
> Retreive header size from pstore.
> powerpc/pseries: Re-organise the oops compression code
> powerpc/pseries: Support compression of oops text via pstore
>
>
> arch/powerpc/platforms/pseries/nvram.c | 236 +++++++++++++++++++++++---------
> fs/pstore/platform.c | 7 +
> include/linux/pstore.h | 6 +
> 3 files changed, 182 insertions(+), 67 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org, paulus@samba.org,
linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Cc: jkenisto@linux.vnet.ibm.com, tony.luck@intel.com,
mahesh@linux.vnet.ibm.com, cbouatmailru@gmail.com,
anton@samba.org, ccross@android.com, keescook@chromium.org
Subject: Re: [RFC PATCH 0/3] Nvram-to-pstore: compression support for oops data
Date: Thu, 06 Jun 2013 00:30:58 +0530 [thread overview]
Message-ID: <51AF8AEA.4030702@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130426094923.14323.80567.stgit@aruna-ThinkPad-T420>
Hi Ben,
There is no change in this patchset and it applies cleanly on top of
v4 of Nvram-to-pstorepatches.
> The patchset takes care of compressing oops messages while writing to NVRAM,
> so that more oops data can be captured in the given space.
>
> big_oops_buf (2.22 * oops_data_sz) is allocated for compression.
> oops_data_sz is oops header size less of oops partition size.
>
> Pstore will internally call kmsg_dump to capture messages from printk
> buffer. While returning the data to nvram it adds is own header.
>
> For compression:
> Register pstore with big_oops_buf.
>
> In case compression fails, copy header added by pstore and
> last oops_data_sz bytes (recent messages) of big_oops_buf to
> nvram for which we need to know header size.
>
> patch 01/03 will add a function in pstore to return the header size.
>
> pstore read callback of nvram will read the compressed data and return the
> decompressed data so that dmesg file (under /dev/pstore) is readable.
>
> In case decompression fails, instead of having the compressed data (junk) in the
> dmesg file it will skip and continue reading other partitions. This results in
> absence of dmesg file but will still have files relating to other parititons.
>
>
> ---
>
> Aruna Balakrishnaiah (3):
> Retreive header size from pstore.
> powerpc/pseries: Re-organise the oops compression code
> powerpc/pseries: Support compression of oops text via pstore
>
>
> arch/powerpc/platforms/pseries/nvram.c | 236 +++++++++++++++++++++++---------
> fs/pstore/platform.c | 7 +
> include/linux/pstore.h | 6 +
> 3 files changed, 182 insertions(+), 67 deletions(-)
>
next prev parent reply other threads:[~2013-06-05 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 9:55 [RFC PATCH 0/3] Nvram-to-pstore: compression support for oops data Aruna Balakrishnaiah
2013-04-26 9:55 ` Aruna Balakrishnaiah
2013-04-26 9:55 ` [PATCH 1/3] Retreive header size from pstore Aruna Balakrishnaiah
2013-04-26 9:55 ` Aruna Balakrishnaiah
2013-04-26 9:56 ` [PATCH 2/3] powerpc/pseries: Re-organise the oops compression code Aruna Balakrishnaiah
2013-04-26 9:56 ` Aruna Balakrishnaiah
2013-04-26 9:56 ` [PATCH 3/3] powerpc/pseries: Support compression of oops text via pstore Aruna Balakrishnaiah
2013-04-26 9:56 ` Aruna Balakrishnaiah
2013-06-01 4:54 ` Benjamin Herrenschmidt
2013-06-01 4:54 ` Benjamin Herrenschmidt
2013-06-04 9:07 ` Aruna Balakrishnaiah
2013-06-04 9:07 ` Aruna Balakrishnaiah
2013-06-05 19:00 ` Aruna Balakrishnaiah [this message]
2013-06-05 19:00 ` [RFC PATCH 0/3] Nvram-to-pstore: compression support for oops data Aruna Balakrishnaiah
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=51AF8AEA.4030702@linux.vnet.ibm.com \
--to=aruna@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=cbouatmailru@gmail.com \
--cc=ccross@android.com \
--cc=jkenisto@linux.vnet.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.