[PATCH 0/5] pstore: ramoops: support multiple pmsg instances

[Hiraku Toyooka]

The following series implements multiple pmsg. This feature allows
userspace program to control individual content aging or priority.

If a pstore backend module(e.g. ramoops) requires the multiple pmsg
instances when registering itself to pstore, multiple /dev/pmsg[ID]
are created. Writes to each /dev/pmsg[ID] are isolated each other. After
reboot, the contents are available in /sys/fs/pstore/pmsg-[backend]-[ID].

In addition, we add multiple pmsg support for ramoops. We can
specify multiple pmsg area size by its module parameter as follows.

 pmsg_size=0x1000,0x2000,...

---

Hiraku Toyooka (5):
      ramoops: use persistent_ram_free() instead of kfree() for freeing prz
      ramoops: introduce generic init/free functions for prz
      pstore: support multiple pmsg instances
      ramoops: support multiple pmsg instances
      selftests/pstore: add testcases for multiple pmsg instances


 Documentation/ramoops.txt                          |   22 ++
 fs/pstore/pmsg.c                                   |   20 ++
 fs/pstore/ram.c                                    |  213 +++++++++++++++-----
 include/linux/pstore.h                             |    1 
 include/linux/pstore_ram.h                         |    8 +
 tools/testing/selftests/pstore/common_tests        |   21 ++
 .../selftests/pstore/pstore_post_reboot_tests      |   27 +--
 tools/testing/selftests/pstore/pstore_tests        |   16 +-
 8 files changed, 257 insertions(+), 71 deletions(-)

--
Hiraku Toyooka
--
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/