Eric Lee / smarc-ti-linux-kernel

07 Sep, 2012

1 commit

  • 65f8c95e4   pstore/ftrace: Convert to its own enable/disable debugfs knob ... Browse Code »

    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

    Anton Vorontsov
     

18 Jul, 2012

1 commit

14 Jun, 2012

1 commit

17 May, 2012

1 commit

  • 39eb7e979   pstore/ram: Add ECC support ... Browse Code »

    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

    Anton Vorontsov
     

16 May, 2012

2 commits

  • 1894a253d   ramoops: Move to fs/pstore/ram.c ... Browse Code »

    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

    Anton Vorontsov
     
  • 9ba80d99c   ramoops: use pstore interface ... Browse Code »

    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

    Kees Cook
     

14 Aug, 2011

1 commit