[lkml]   [2019]   [Jan]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC v3 0/2] pstore/rom: new support logger for block devices
Why should we need pstore_rom?
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).
2. Do not any equipment have battery, which means that it lost all data
on general ram if power failure. Pstore has little to do for these

[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well on allwinner(sunxi) platform.
On patch 2:
A sample for pstore_rom, using general ram rather than block device.

[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and 'romz_register'

[PATCH v3]
On patch 1:
Fix build as module error for undefined 'vfs_read' and 'vfs_write'
Both of 'vfs_read' and 'vfs_write' haven't be exproted yet, so we use 'kernel_read'
and 'kernel_write' instead.

liaoweixiong (2):
pstore/rom: new support logger for block devices
pstore/rom: add sample for pstore_rom

fs/pstore/Kconfig | 16 +
fs/pstore/Makefile | 5 +
fs/pstore/rombuf.c | 46 +++
fs/pstore/romzone.c | 957 +++++++++++++++++++++++++++++++++++++++++++++
include/linux/pstore_rom.h | 61 +++
5 files changed, 1085 insertions(+)
create mode 100644 fs/pstore/rombuf.c
create mode 100644 fs/pstore/romzone.c
create mode 100644 include/linux/pstore_rom.h


 \ /
  Last update: 2019-01-02 08:19    [W:0.057 / U:8.544 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site