[PATCH v2 0/3] Nvram-to-pstore: compression support for oops data

[Aruna Balakrishnaiah]

Changes from v1:
		- Add header size argument in the pstore write callback
		instead of a separate API to return header size.

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 adds an additional argument for header size in pstore_write callback.

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):
      Pass header size in the pstore write callback
      powerpc/pseries: Re-organise the oops compression code
      powerpc/pseries: Support compression of oops text via pstore


 arch/powerpc/platforms/pseries/nvram.c |  239 +++++++++++++++++++++++---------
 drivers/acpi/apei/erst.c               |    4 -
 drivers/firmware/efi/efi-pstore.c      |    2 
 fs/pstore/platform.c                   |   10 +
 fs/pstore/ram.c                        |    3 
 include/linux/pstore.h                 |    8 +
 6 files changed, 187 insertions(+), 79 deletions(-)

-- 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/