linux-toradex.git/Documentation/ramoops.txt, branch v4.7

pstore-ram: Allow optional mapping with pgprot_noncached

2014-12-11T21:38:31+00:00

On some ARMs the memory can be mapped pgprot_noncached() and still
be working for atomic operations. As pointed out by Colin Cross
, in some cases you do want to use
pgprot_noncached() if the SoC supports it to see a debug printk
just before a write hanging the system.

On ARMs, the atomic operations on strongly ordered memory are
implementation defined. So let's provide an optional kernel parameter
for configuring pgprot_noncached(), and use pgprot_writecombine() by
default.

Cc: Arnd Bergmann 
Cc: Rob Herring 
Cc: Randy Dunlap 
Cc: Anton Vorontsov 
Cc: Colin Cross 
Cc: Olof Johansson 
Cc: Russell King 
Cc: stable@vger.kernel.org
Acked-by: Kees Cook 
Signed-off-by: Tony Lindgren 
Signed-off-by: Tony Luck

pstore/ftrace: Convert to its own enable/disable debugfs knob

2012-09-07T05:16:58+00:00

With this patch we no longer reuse function tracer infrastructure, now
we register our own tracer back-end via a debugfs knob.

It's a bit more code, but that is the only downside. On the bright side we
have:

- Ability to make persistent_ram module removable (when needed, we can
  move ftrace_ops struct into a module). Note that persistent_ram is still
  not removable for other reasons, but with this patch it's just one
  thing less to worry about;

- Pstore part is more isolated from the generic function tracer. We tried
  it already by registering our own tracer in available_tracers, but that
  way we're loosing ability to see the traces while we record them to
  pstore. This solution is somewhere in the middle: we only register
  "internal ftracer" back-end, but not the "front-end";

- When there is only pstore tracing enabled, the kernel will only write
  to the pstore buffer, omitting function tracer buffer (which, of course,
  still can be enabled via 'echo function > current_tracer').

Suggested-by: Steven Rostedt 
Signed-off-by: Anton Vorontsov

pstore/ram: Add ftrace messages handling

2012-07-17T17:14:17+00:00

The ftrace log size is configurable via ramoops.ftrace_size
module option, and the log itself is available via
/ftrace-ramoops file.

Signed-off-by: Anton Vorontsov 
Signed-off-by: Greg Kroah-Hartman

pstore/ram: Add some more documentation and examples

2012-06-13T23:59:28+00:00

Suggested-by: Shuah Khan 
Signed-off-by: Anton Vorontsov 
Acked-by: Kees Cook 
Acked-by: Colin Cross 
Signed-off-by: Greg Kroah-Hartman

pstore/ram: Add ECC support

2012-05-17T15:51:59+00:00

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

ramoops: Move to fs/pstore/ram.c

2012-05-16T15:06:37+00:00

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

ramoops: use pstore interface

2012-05-16T15:06:33+00:00

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

Documentation: add Ramoops usage description

2011-08-14T01:34:03+00:00

Add a documentation file describing the usage of Ramoops

Signed-off-by: Sergiu Iordache 
Signed-off-by: Randy Dunlap 
Signed-off-by: Linus Torvalds