mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>
To: linux-kernel@vger.kernel.org
Cc: Tony Luck <tony.luck@intel.com>,
	Kees Cook <keescook@chromium.org>,
	Anton Vorontsov <anton@enomsg.org>,
	Mark Salyzyn <salyzyn@android.com>,
	Colin Cross <ccross@android.com>,
	Seiji Aguchi <seiji.aguchi.tr@hitachi.com>
Subject: [PATCH 0/5] pstore: ramoops: support multiple pmsg instances
Date: Thu, 05 Nov 2015 11:36:44 +0900	[thread overview]
Message-ID: <20151105023644.3367.94795.stgit@arietta> (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,...

---

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

             reply	other threads:[~2015-11-05  2:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05  2:36 Hiraku Toyooka [this message]
2015-11-05  2:36 ` [PATCH 1/5] ramoops: use persistent_ram_free() instead of kfree() for freeing prz Hiraku Toyooka
2015-11-05  2:36 ` [PATCH 2/5] ramoops: introduce generic init/free functions for prz Hiraku Toyooka
2015-11-05  2:36 ` [PATCH 3/5] pstore: support multiple pmsg instances Hiraku Toyooka
2015-11-05  2:36 ` [PATCH 4/5] ramoops: " Hiraku Toyooka
2015-11-05  2:36 ` [PATCH 5/5] selftests/pstore: add testcases for " Hiraku Toyooka

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=20151105023644.3367.94795.stgit@arietta \
    --to=hiraku.toyooka.gu@hitachi.com \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=salyzyn@android.com \
    --cc=seiji.aguchi.tr@hitachi.com \
    --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

all inboxes | Powered by JetHome®