2012-07-10 00:10:41 +00:00
|
|
|
#ifndef __PSTORE_INTERNAL_H__
|
|
|
|
|
#define __PSTORE_INTERNAL_H__
|
|
|
|
|
|
2012-07-17 18:37:07 +00:00
|
|
|
#include <linux/types.h>
|
|
|
|
|
#include <linux/time.h>
|
2012-07-10 00:10:41 +00:00
|
|
|
#include <linux/pstore.h>
|
|
|
|
|
|
|
|
|
|
#if NR_CPUS <= 2 && defined(CONFIG_ARM_THUMB)
|
|
|
|
|
#define PSTORE_CPU_IN_IP 0x1
|
|
|
|
|
#elif NR_CPUS <= 4 && defined(CONFIG_ARM)
|
|
|
|
|
#define PSTORE_CPU_IN_IP 0x3
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
struct pstore_ftrace_record {
|
|
|
|
|
unsigned long ip;
|
|
|
|
|
unsigned long parent_ip;
|
|
|
|
|
#ifndef PSTORE_CPU_IN_IP
|
|
|
|
|
unsigned int cpu;
|
|
|
|
|
#endif
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static inline void
|
|
|
|
|
pstore_ftrace_encode_cpu(struct pstore_ftrace_record *rec, unsigned int cpu)
|
|
|
|
|
{
|
|
|
|
|
#ifndef PSTORE_CPU_IN_IP
|
|
|
|
|
rec->cpu = cpu;
|
|
|
|
|
#else
|
|
|
|
|
rec->ip |= cpu;
|
|
|
|
|
#endif
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static inline unsigned int
|
|
|
|
|
pstore_ftrace_decode_cpu(struct pstore_ftrace_record *rec)
|
|
|
|
|
{
|
|
|
|
|
#ifndef PSTORE_CPU_IN_IP
|
|
|
|
|
return rec->cpu;
|
|
|
|
|
#else
|
|
|
|
|
return rec->ip & PSTORE_CPU_IN_IP;
|
|
|
|
|
#endif
|
|
|
|
|
}
|
|
|
|
|
|
pstore/ftrace: Convert to its own enable/disable debugfs knob
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 <rostedt@goodmis.org>
Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>
2012-07-17 21:26:15 +00:00
|
|
|
#ifdef CONFIG_PSTORE_FTRACE
|
|
|
|
|
extern void pstore_register_ftrace(void);
|
|
|
|
|
#else
|
|
|
|
|
static inline void pstore_register_ftrace(void) {}
|
|
|
|
|
#endif
|
|
|
|
|
|
2012-07-10 00:10:41 +00:00
|
|
|
extern struct pstore_info *psinfo;
|
|
|
|
|
|
2011-03-18 22:33:43 +00:00
|
|
|
extern void pstore_set_kmsg_bytes(int);
|
2011-08-11 22:14:39 +00:00
|
|
|
extern void pstore_get_records(int);
|
2010-12-28 22:25:21 +00:00
|
|
|
extern int pstore_mkfile(enum pstore_type_id, char *psname, u64 id,
|
efi_pstore: Add a sequence counter to a variable name
[Issue]
Currently, a variable name, which identifies each entry, consists of type, id and ctime.
But if multiple events happens in a short time, a second/third event may fail to log because
efi_pstore can't distinguish each event with current variable name.
[Solution]
A reasonable way to identify all events precisely is introducing a sequence counter to
the variable name.
The sequence counter has already supported in a pstore layer with "oopscount".
So, this patch adds it to a variable name.
Also, it is passed to read/erase callbacks of platform drivers in accordance with
the modification of the variable name.
<before applying this patch>
a variable name of first event: dump-type0-1-12345678
a variable name of second event: dump-type0-1-12345678
type:0
id:1
ctime:12345678
If multiple events happen in a short time, efi_pstore can't distinguish them because
variable names are same among them.
<after applying this patch>
it can be distinguishable by adding a sequence counter as follows.
a variable name of first event: dump-type0-1-1-12345678
a variable name of Second event: dump-type0-1-2-12345678
type:0
id:1
sequence counter: 1(first event), 2(second event)
ctime:12345678
In case of a write callback executed in pstore_console_write(), "0" is added to
an argument of the write callback because it just logs all kernel messages and
doesn't need to care about multiple events.
Signed-off-by: Seiji Aguchi <seiji.aguchi@hds.com>
Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Mike Waychison <mikew@google.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
2012-11-27 00:07:44 +00:00
|
|
|
int count, char *data, size_t size,
|
2011-07-21 20:57:52 +00:00
|
|
|
struct timespec time, struct pstore_info *psi);
|
2010-12-28 22:25:21 +00:00
|
|
|
extern int pstore_is_mounted(void);
|
2012-07-10 00:10:41 +00:00
|
|
|
|
|
|
|
|
#endif
|
