7 May
2012
7 May
'12
5:40 p.m.
On 05/07/2012 10:33 AM, Anton Vorontsov wrote:
- ram_console feature seemed quite interesting, so I started looking more closely into it. Based on previous lkml discussions, it appears that the main obstacle is that we should use pstore. So, as a warm-up I started porting ramoops (which uses pstore in -next tree) driver to use persistent_ram. That would be a good reason to move persistent_ram out of staging/.
From the discussions on the list, it it seemed we might want to use persistent_ram as a back end for pstore, instead of having ramoops use it directly. This allows drivers to target one interface (pstore) and have it multiplex the data back to the proper storage for the device.
thanks -john