2019-05-29 14:17:56 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-only
|
2012-07-10 00:10:41 +00:00
|
|
|
/*
|
|
|
|
* Copyright 2012 Google, Inc.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/compiler.h>
|
|
|
|
#include <linux/irqflags.h>
|
|
|
|
#include <linux/percpu.h>
|
|
|
|
#include <linux/smp.h>
|
|
|
|
#include <linux/atomic.h>
|
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
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/mutex.h>
|
|
|
|
#include <linux/ftrace.h>
|
|
|
|
#include <linux/fs.h>
|
|
|
|
#include <linux/debugfs.h>
|
|
|
|
#include <linux/err.h>
|
|
|
|
#include <linux/cache.h>
|
2012-07-10 00:10:41 +00:00
|
|
|
#include <asm/barrier.h>
|
|
|
|
#include "internal.h"
|
|
|
|
|
2016-10-20 07:34:05 +00:00
|
|
|
/* This doesn't need to be atomic: speed is chosen over correctness here. */
|
|
|
|
static u64 pstore_ftrace_stamp;
|
|
|
|
|
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
|
|
|
static void notrace pstore_ftrace_call(unsigned long ip,
|
2012-11-15 02:48:15 +00:00
|
|
|
unsigned long parent_ip,
|
|
|
|
struct ftrace_ops *op,
|
|
|
|
struct pt_regs *regs)
|
2012-07-10 00:10:41 +00:00
|
|
|
{
|
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
|
|
|
unsigned long flags;
|
2012-07-10 00:10:41 +00:00
|
|
|
struct pstore_ftrace_record rec = {};
|
2017-03-05 08:27:54 +00:00
|
|
|
struct pstore_record record = {
|
|
|
|
.type = PSTORE_TYPE_FTRACE,
|
|
|
|
.buf = (char *)&rec,
|
|
|
|
.size = sizeof(rec),
|
|
|
|
.psi = psinfo,
|
|
|
|
};
|
2012-07-10 00:10:41 +00:00
|
|
|
|
|
|
|
if (unlikely(oops_in_progress))
|
|
|
|
return;
|
|
|
|
|
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
|
|
|
local_irq_save(flags);
|
|
|
|
|
2012-07-10 00:10:41 +00:00
|
|
|
rec.ip = ip;
|
|
|
|
rec.parent_ip = parent_ip;
|
2016-10-20 07:34:05 +00:00
|
|
|
pstore_ftrace_write_timestamp(&rec, pstore_ftrace_stamp++);
|
2012-07-10 00:10:41 +00:00
|
|
|
pstore_ftrace_encode_cpu(&rec, raw_smp_processor_id());
|
2017-03-06 06:41:10 +00:00
|
|
|
psinfo->write(&record);
|
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
|
|
|
|
|
|
|
local_irq_restore(flags);
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct ftrace_ops pstore_ftrace_ops __read_mostly = {
|
|
|
|
.func = pstore_ftrace_call,
|
|
|
|
};
|
|
|
|
|
|
|
|
static DEFINE_MUTEX(pstore_ftrace_lock);
|
|
|
|
static bool pstore_ftrace_enabled;
|
|
|
|
|
|
|
|
static ssize_t pstore_ftrace_knob_write(struct file *f, const char __user *buf,
|
|
|
|
size_t count, loff_t *ppos)
|
|
|
|
{
|
|
|
|
u8 on;
|
|
|
|
ssize_t ret;
|
|
|
|
|
|
|
|
ret = kstrtou8_from_user(buf, count, 2, &on);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
mutex_lock(&pstore_ftrace_lock);
|
|
|
|
|
|
|
|
if (!on ^ pstore_ftrace_enabled)
|
|
|
|
goto out;
|
|
|
|
|
2016-11-15 20:31:21 +00:00
|
|
|
if (on) {
|
|
|
|
ftrace_ops_set_global_filter(&pstore_ftrace_ops);
|
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
|
|
|
ret = register_ftrace_function(&pstore_ftrace_ops);
|
2016-11-15 20:31:21 +00:00
|
|
|
} else {
|
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
|
|
|
ret = unregister_ftrace_function(&pstore_ftrace_ops);
|
2016-11-15 20:31:21 +00:00
|
|
|
}
|
|
|
|
|
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
|
|
|
if (ret) {
|
|
|
|
pr_err("%s: unable to %sregister ftrace ops: %zd\n",
|
|
|
|
__func__, on ? "" : "un", ret);
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
|
|
|
|
pstore_ftrace_enabled = on;
|
|
|
|
out:
|
|
|
|
ret = count;
|
|
|
|
err:
|
|
|
|
mutex_unlock(&pstore_ftrace_lock);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static ssize_t pstore_ftrace_knob_read(struct file *f, char __user *buf,
|
|
|
|
size_t count, loff_t *ppos)
|
|
|
|
{
|
|
|
|
char val[] = { '0' + pstore_ftrace_enabled, '\n' };
|
|
|
|
|
|
|
|
return simple_read_from_buffer(buf, count, ppos, val, sizeof(val));
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct file_operations pstore_knob_fops = {
|
|
|
|
.open = simple_open,
|
|
|
|
.read = pstore_ftrace_knob_read,
|
|
|
|
.write = pstore_ftrace_knob_write,
|
|
|
|
};
|
|
|
|
|
2015-10-20 07:39:03 +00:00
|
|
|
static struct dentry *pstore_ftrace_dir;
|
|
|
|
|
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
|
|
|
void pstore_register_ftrace(void)
|
|
|
|
{
|
|
|
|
struct dentry *file;
|
|
|
|
|
2017-03-06 06:41:10 +00:00
|
|
|
if (!psinfo->write)
|
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
|
|
|
return;
|
|
|
|
|
2015-10-20 07:39:03 +00:00
|
|
|
pstore_ftrace_dir = debugfs_create_dir("pstore", NULL);
|
|
|
|
if (!pstore_ftrace_dir) {
|
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
|
|
|
pr_err("%s: unable to create pstore directory\n", __func__);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2015-10-20 07:39:03 +00:00
|
|
|
file = debugfs_create_file("record_ftrace", 0600, pstore_ftrace_dir,
|
|
|
|
NULL, &pstore_knob_fops);
|
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
|
|
|
if (!file) {
|
|
|
|
pr_err("%s: unable to create record_ftrace file\n", __func__);
|
|
|
|
goto err_file;
|
|
|
|
}
|
|
|
|
|
|
|
|
return;
|
|
|
|
err_file:
|
2015-10-20 07:39:03 +00:00
|
|
|
debugfs_remove(pstore_ftrace_dir);
|
|
|
|
}
|
|
|
|
|
|
|
|
void pstore_unregister_ftrace(void)
|
|
|
|
{
|
|
|
|
mutex_lock(&pstore_ftrace_lock);
|
|
|
|
if (pstore_ftrace_enabled) {
|
|
|
|
unregister_ftrace_function(&pstore_ftrace_ops);
|
2017-10-07 14:02:21 +00:00
|
|
|
pstore_ftrace_enabled = false;
|
2015-10-20 07:39:03 +00:00
|
|
|
}
|
|
|
|
mutex_unlock(&pstore_ftrace_lock);
|
|
|
|
|
|
|
|
debugfs_remove_recursive(pstore_ftrace_dir);
|
2012-07-10 00:10:41 +00:00
|
|
|
}
|