From: "岩松信洋 / IWAMATSU,NOBUHIRO" <nobuhiro.iwamatsu.kw@hitachi.com>
To: "岩松信洋 / IWAMATSU,NOBUHIRO" <nobuhiro.iwamatsu.kw@hitachi.com>,
"Kees Cook" <keescook@chromium.org>
Cc: Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
"Tony Luck" <tony.luck@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"cti.systems-productivity-manager.ts@hitachi.com"
<cti.systems-productivity-manager.ts@hitachi.com>
Subject: RE: [PATCH v3 0/8] pstore: ramoops: support multiple pmsg instances
Date: Tue, 27 Dec 2016 00:48:41 +0000 [thread overview]
Message-ID: <F89ECF87BC754A49BB74E794F6A0EC2F01041248@GSjpTKYDCembx31.service.hitachi.net> (raw)
In-Reply-To: <F89ECF87BC754A49BB74E794F6A0EC2FFD246C@GSjpTKYDCembx31.service.hitachi.net>
Ping?_
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 岩松信洋 /
> IWAMATSU,NOBUHIRO
> Sent: Monday, December 05, 2016 10:47 AM
> To: Kees Cook
> Cc: Anton Vorontsov; Colin Cross; Tony Luck; LKML;
> cti.systems-productivity-manager.ts@hitachi.com
> Subject: RE: [PATCH v3 0/8] pstore: ramoops: support multiple pmsg instances
>
> Hi, Kees.
>
> > -----Original Message-----
> > From: keescook@google.com [mailto:keescook@google.com] On Behalf Of
> > Kees Cook
> > Sent: Saturday, November 12, 2016 7:24 AM
> > To: 岩松信洋 / IWAMATSU,NOBUHIRO
> > Cc: Anton Vorontsov; Colin Cross; Tony Luck; LKML;
> > cti.systems-productivity-manager.ts@hitachi.com
> > Subject: Re: [PATCH v3 0/8] pstore: ramoops: support multiple pmsg
> > instances
> >
> > On Tue, Oct 18, 2016 at 12:13 AM, Nobuhiro Iwamatsu
> > <nobuhiro.iwamatsu.kw@hitachi.com> wrote:
> > > 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.
> > >
> > > v3:
> > > Rebase to v4.8.
> > > Split patch.
> > > merged device_create().
> > > Remove Blank lines.
> > > Update documentiation of DT binding.
> > > Update parsing function of ramoops_pmsg_size, add NULL termination.
> > > Update module parameters for pmsg_size list.
> >
> > Thanks for this v3! Sorry for the delay, I should be able to review
> > this shortly.
>
> Thank you.
> I will wait for your review.
>
> >
> > -Kees
> >
>
> Best regards,
> Nobuhiro
>
> > >
> > > Hiraku Toyooka (2):
> > > pstore: support multiple pmsg instances
> > > selftests/pstore: add testcases for multiple pmsg instances
> > >
> > > Nobuhiro Iwamatsu (6):
> > > pstore: Replace four kzalloc() calls by kcalloc() in
> > ramoops_init_przs()
> > > pstore: Change parameter of ramoops_free_przs()
> > > ramoops: Add __ramoops_init_prz() as generic function
> > > pstore: Rename 'przs' to 'dprzs' in struct ramoops_context
> > > ramoops: Rename ramoops_init_prz() to ramoops_init_dprzs()
> > > ramoops: support multiple pmsg instances
> > >
> > > .../bindings/reserved-memory/ramoops.txt | 6 +-
> > > Documentation/ramoops.txt | 22 ++
> > > fs/pstore/pmsg.c | 23 +-
> > > fs/pstore/ram.c | 344
> > ++++++++++++++++-----
> > > 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 | 14 +-
> > > 9 files changed, 360 insertions(+), 106 deletions(-)
> > >
> > > --
> > > 2.9.3
> > >
> > >
> >
> >
> >
> > --
> > Kees Cook
> > Nexus Security
next prev parent reply other threads:[~2016-12-27 0:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 7:13 [PATCH v3 0/8] pstore: ramoops: support multiple pmsg instances Nobuhiro Iwamatsu
2016-10-18 7:13 ` [PATCH v3 1/8] pstore: Replace four kzalloc() calls by kcalloc() in ramoops_init_przs() Nobuhiro Iwamatsu
2016-10-18 7:13 ` [PATCH v3 2/8] pstore: Change parameter of ramoops_free_przs() Nobuhiro Iwamatsu
2016-10-18 7:13 ` [PATCH v3 3/8] ramoops: Add __ramoops_init_prz() as generic function Nobuhiro Iwamatsu
2016-10-18 7:13 ` [PATCH v3 4/8] pstore: Rename 'przs' to 'dprzs' in struct ramoops_context Nobuhiro Iwamatsu
2016-10-18 7:13 ` [PATCH v3 5/8] ramoops: Rename ramoops_init_prz() to ramoops_init_dprzs() Nobuhiro Iwamatsu
2016-10-18 7:13 ` [PATCH v3 6/8] pstore: support multiple pmsg instances Nobuhiro Iwamatsu
2016-10-18 7:13 ` [PATCH v3 7/8] ramoops: " Nobuhiro Iwamatsu
2016-10-18 7:13 ` [PATCH v3 8/8] selftests/pstore: add testcases for " Nobuhiro Iwamatsu
2016-11-11 22:24 ` [PATCH v3 0/8] pstore: ramoops: support " Kees Cook
2016-12-05 1:47 ` 岩松信洋 / IWAMATSU,NOBUHIRO
2016-12-27 0:48 ` 岩松信洋 / IWAMATSU,NOBUHIRO [this message]
2017-01-04 6:20 ` Kees Cook
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=F89ECF87BC754A49BB74E794F6A0EC2F01041248@GSjpTKYDCembx31.service.hitachi.net \
--to=nobuhiro.iwamatsu.kw@hitachi.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=cti.systems-productivity-manager.ts@hitachi.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).