17 May, 2012
1 commit
-
This is now straightforward: just introduce a module parameter and pass
the needed value to persistent_ram_new().Signed-off-by: Anton Vorontsov
Acked-by: Marco Stornelli
Acked-by: Kees Cook
Signed-off-by: Greg Kroah-Hartman
16 May, 2012
2 commits
-
Since ramoops was converted to pstore, it has nothing to do with character
devices nowadays. Instead, today it is just a RAM backend for pstore.The patch just moves things around. There are a few changes were needed
because of the move:1. Kconfig and Makefiles fixups, of course.
2. In pstore/ram.c we have to play a bit with MODULE_PARAM_PREFIX, this
is needed to keep user experience the same as with ramoops driver
(i.e. so that ramoops.foo kernel command line arguments would still
work).Signed-off-by: Anton Vorontsov
Acked-by: Marco Stornelli
Acked-by: Kees Cook
Signed-off-by: Greg Kroah-Hartman -
Instead of using /dev/mem directly and forcing userspace to know (or
extract) where the platform has defined persistent memory, how many slots
it has, the sizes, etc, use the common pstore infrastructure to handle
Oops gathering and extraction. This presents a much easier to use
filesystem-based view to the memory region. This also means that any
other tools that are written to understand pstore will automatically be
able to process ramoops too.Signed-off-by: Kees Cook
Cc: Tony Luck
Cc: Marco Stornelli
Cc: Arnd Bergmann
Cc: Randy Dunlap
Signed-off-by: Andrew Morton
Signed-off-by: Greg Kroah-Hartman
14 Aug, 2011
1 commit
-
Add a documentation file describing the usage of Ramoops
Signed-off-by: Sergiu Iordache
Signed-off-by: Randy Dunlap
Signed-off-by: Linus Torvalds
