From: liaoweixiong <liaoweixiong@allwinnertech.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [RFC v7 0/5] pstore/block: new support logger for block devices
Date: Thu, 24 Jan 2019 20:16:30 +0800 [thread overview]
Message-ID: <5f243418-c6bd-061e-1161-1c0139ad84bf@allwinnertech.com> (raw)
In-Reply-To: <20190123182638.GD2792@darkstar.musicnaut.iki.fi>
On 2019-01-24 02:26, Aaro Koskinen wrote:
> Hi,
>
> On Wed, Jan 23, 2019 at 08:05:11PM +0800, liaoweixiong wrote:
>> Why should we need pstore_block?
>> 1. Most embedded intelligent equipment have no persistent ram, which
>> increases costs. We perfer to cheaper solutions, like block devices.
>> In fast, there is already a sample for block device logger in driver
>> MTD (drivers/mtd/mtdoops.c).
>
> I think you should add a patch for some actual block device using this
> new framework to show that it can work. What HW you think would be
> using things?
>
I will try to add a patch. Actually, I have implemented it on allwinner
platform, but unfortunately these codes are unsuitable to submit to
upper stream.
In addition, there is already a sample for pstore/blk on patch 3 of
version 7. It names
blkoops. Blkoops is suitable for most block device as what it need is
just a path of a partition. We can use it to test most of features but
panic.
> A.
>
--
liaoweixiong
next prev parent reply other threads:[~2019-01-24 12:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 12:05 [RFC v7 0/5] pstore/block: new support logger for block devices liaoweixiong
2019-01-23 12:05 ` [RFC v7 1/5] pstore/blk: " liaoweixiong
2019-01-23 12:05 ` [RFC v7 2/5] dt-bindings: pstore-block: new support for blkoops liaoweixiong
2019-01-30 16:07 ` Rob Herring
2019-02-13 13:52 ` liaoweixiong
2019-02-13 20:30 ` Rob Herring
2019-02-15 1:06 ` liaoweixiong
2019-02-18 15:37 ` Rob Herring
2019-01-23 12:05 ` [RFC v7 3/5] pstore/blk: add blkoops for pstore_blk liaoweixiong
2019-01-23 12:05 ` [RFC v7 4/5] pstore/blk: support pmsg for pstore block liaoweixiong
2019-01-23 12:05 ` [RFC v7 5/5] Documentation: pstore/blk: create document for pstore_blk liaoweixiong
2019-01-23 18:26 ` [RFC v7 0/5] pstore/block: new support logger for block devices Aaro Koskinen
2019-01-24 12:16 ` liaoweixiong [this message]
2019-02-12 20:54 ` Kees Cook
2019-02-13 0:40 ` liaoweixiong
2019-02-13 20:35 ` Rob Herring
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=5f243418-c6bd-061e-1161-1c0139ad84bf@allwinnertech.com \
--to=liaoweixiong@allwinnertech.com \
--cc=aaro.koskinen@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=anton@enomsg.org \
--cc=arnd@arndb.de \
--cc=ccross@android.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@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