diff options
| author | Kees Cook <keescook@chromium.org> | 2018-10-17 17:20:35 -0700 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2018-10-22 07:11:58 -0700 |
| commit | 1227daa43bce1318ff6fb54e6cd862b4f60245c7 (patch) | |
| tree | 013a4433679d8626d6a6fab52ae201b0e6571b3f /drivers/w1 | |
| parent | 95047b0519c17a28e09df5f38750f5354e3db4c4 (diff) | |
pstore/ram: Clarify resource reservation labels
When ramoops reserved a memory region in the kernel, it had an unhelpful
label of "persistent_memory". When reading /proc/iomem, it would be
repeated many times, did not hint that it was ramoops in particular,
and didn't clarify very much about what each was used for:
400000000-407ffffff : Persistent Memory (legacy)
400000000-400000fff : persistent_memory
400001000-400001fff : persistent_memory
...
4000ff000-4000fffff : persistent_memory
Instead, this adds meaningful labels for how the various regions are
being used:
400000000-407ffffff : Persistent Memory (legacy)
400000000-400000fff : ramoops:dump(0/252)
400001000-400001fff : ramoops:dump(1/252)
...
4000fc000-4000fcfff : ramoops:dump(252/252)
4000fd000-4000fdfff : ramoops:console
4000fe000-4000fe3ff : ramoops:ftrace(0/3)
4000fe400-4000fe7ff : ramoops:ftrace(1/3)
4000fe800-4000febff : ramoops:ftrace(2/3)
4000fec00-4000fefff : ramoops:ftrace(3/3)
4000ff000-4000fffff : ramoops:pmsg
Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Tested-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Tested-by: Guenter Roeck <groeck@chromium.org>
Diffstat (limited to 'drivers/w1')
0 files changed, 0 insertions, 0 deletions