| From: |
| liaoweixiong <liaoweixiong-AT-allwinnertech.com> |
| To: |
| Kees Cook <keescook-AT-chromium.org>, Anton Vorontsov <anton-AT-enomsg.org>, Colin Cross <ccross-AT-android.com>, Tony Luck <tony.luck-AT-intel.com> |
| Subject: |
| [RFC 0/2] pstore/rom: new support logger for block devices |
| Date: |
| Tue, 1 Jan 2019 17:27:23 +0800 |
| Message-ID: |
| <1546334845-24255-1-git-send-email-liaoweixiong@allwinnertech.com> |
| Cc: |
| linux-kernel-AT-vger.kernel.org, liaoweixiong <liaoweixiong-AT-allwinnertech.com> |
| Archive-link: |
| Article |
pstore_rom is similar to pstore_ram, but dump log to block devices
rather than persistent ram.
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
equipments.
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.
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 | 965 +++++++++++++++++++++++++++++++++++++++++++++
include/linux/pstore_rom.h | 68 ++++
5 files changed, 1100 insertions(+)
create mode 100644 fs/pstore/rombuf.c
create mode 100644 fs/pstore/romzone.c
create mode 100644 include/linux/pstore_rom.h
--
1.9.1