From: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.kw@hitachi.com>
To: Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org,
Nobuhiro Iwamatsu <nobuhiro.iwamatsu.kw@hitachi.com>
Subject: [PATCH v2 0/5] pstore: ramoops: support multiple pmsg instances
Date: Mon, 25 Jul 2016 12:56:54 +0900 [thread overview]
Message-ID: <1469419019-4820-1-git-send-email-nobuhiro.iwamatsu.kw@hitachi.com> (raw)
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,...
I did check the operation of this feature on CycloneV (socfpga) Helio board.
v2:
Rebase to v4.7.
Fix compile error by ramoops_free_przs function.
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 | 215 ++++++++++++++++-----
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(+), 73 deletions(-)
--
2.8.1
next reply other threads:[~2016-07-25 4:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 3:56 Nobuhiro Iwamatsu [this message]
2016-07-25 3:56 ` [PATCH v2 1/5] ramoops: use persistent_ram_free() instead of kfree() for freeing prz Nobuhiro Iwamatsu
2016-07-28 19:35 ` Kees Cook
2016-07-29 5:58 ` 岩松信洋 / IWAMATSU，NOBUHIRO
2016-08-03 19:04 ` Kees Cook
2016-07-25 3:56 ` [PATCH v2 2/5] ramoops: introduce generic init/free functions for prz Nobuhiro Iwamatsu
2016-09-08 21:22 ` Kees Cook
2016-10-05 4:06 ` 岩松信洋 / IWAMATSU，NOBUHIRO
2016-07-25 3:56 ` [PATCH v2 3/5] pstore: support multiple pmsg instances Nobuhiro Iwamatsu
2016-09-08 21:33 ` Kees Cook
2016-10-05 4:09 ` 岩松信洋 / IWAMATSU，NOBUHIRO
2016-07-25 3:56 ` [PATCH v2 4/5] ramoops: " Nobuhiro Iwamatsu
2016-09-08 21:53 ` Kees Cook
2016-10-05 4:13 ` 岩松信洋 / IWAMATSU，NOBUHIRO
2016-07-25 3:56 ` [PATCH v2 5/5] selftests/pstore: add testcases for " Nobuhiro Iwamatsu
2016-09-08 21:55 ` Kees Cook
2016-10-05 4:14 ` 岩松信洋 / IWAMATSU，NOBUHIRO
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=1469419019-4820-1-git-send-email-nobuhiro.iwamatsu.kw@hitachi.com \
--to=nobuhiro.iwamatsu.kw@hitachi.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).