2019-05-29 17:17:56 +03:00
// SPDX-License-Identifier: GPL-2.0-only
2012-07-10 04:10:41 +04: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-18 01:26:15 +04: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>
2020-05-08 18:42:12 +03:00
# include <linux/slab.h>
2012-07-10 04:10:41 +04:00
# include <asm/barrier.h>
# include "internal.h"
2016-10-20 10:34:05 +03: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-18 01:26:15 +04:00
static void notrace pstore_ftrace_call ( unsigned long ip ,
2012-11-15 06:48:15 +04:00
unsigned long parent_ip ,
struct ftrace_ops * op ,
2020-10-29 00:42:17 +03:00
struct ftrace_regs * fregs )
2012-07-10 04:10:41 +04:00
{
2020-11-06 05:32:39 +03:00
int bit ;
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-18 01:26:15 +04:00
unsigned long flags ;
2012-07-10 04:10:41 +04:00
struct pstore_ftrace_record rec = { } ;
2017-03-05 11:27:54 +03:00
struct pstore_record record = {
. type = PSTORE_TYPE_FTRACE ,
. buf = ( char * ) & rec ,
. size = sizeof ( rec ) ,
. psi = psinfo ,
} ;
2012-07-10 04:10:41 +04:00
if ( unlikely ( oops_in_progress ) )
return ;
2020-11-06 05:32:46 +03:00
bit = ftrace_test_recursion_trylock ( ip , parent_ip ) ;
2020-11-06 05:32:39 +03:00
if ( bit < 0 )
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-18 01:26:15 +04:00
local_irq_save ( flags ) ;
2012-07-10 04:10:41 +04:00
rec . ip = ip ;
rec . parent_ip = parent_ip ;
2016-10-20 10:34:05 +03:00
pstore_ftrace_write_timestamp ( & rec , pstore_ftrace_stamp + + ) ;
2012-07-10 04:10:41 +04:00
pstore_ftrace_encode_cpu ( & rec , raw_smp_processor_id ( ) ) ;
2017-03-06 09:41:10 +03: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-18 01:26:15 +04:00
local_irq_restore ( flags ) ;
2020-11-06 05:32:39 +03:00
ftrace_test_recursion_unlock ( bit ) ;
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-18 01:26:15 +04:00
}
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 23:31:21 +03: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-18 01:26:15 +04:00
ret = register_ftrace_function ( & pstore_ftrace_ops ) ;
2016-11-15 23:31:21 +03: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-18 01:26:15 +04:00
ret = unregister_ftrace_function ( & pstore_ftrace_ops ) ;
2016-11-15 23:31:21 +03: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-18 01:26:15 +04: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 10:39:03 +03: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-18 01:26:15 +04:00
void pstore_register_ftrace ( void )
{
2017-03-06 09:41:10 +03: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-18 01:26:15 +04:00
return ;
2015-10-20 10:39:03 +03:00
pstore_ftrace_dir = debugfs_create_dir ( " pstore " , NULL ) ;
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-18 01:26:15 +04:00
2019-06-12 18:20:33 +03:00
debugfs_create_file ( " record_ftrace " , 0600 , pstore_ftrace_dir , NULL ,
& pstore_knob_fops ) ;
2015-10-20 10:39:03 +03:00
}
void pstore_unregister_ftrace ( void )
{
mutex_lock ( & pstore_ftrace_lock ) ;
if ( pstore_ftrace_enabled ) {
unregister_ftrace_function ( & pstore_ftrace_ops ) ;
2017-10-07 17:02:21 +03:00
pstore_ftrace_enabled = false ;
2015-10-20 10:39:03 +03:00
}
mutex_unlock ( & pstore_ftrace_lock ) ;
debugfs_remove_recursive ( pstore_ftrace_dir ) ;
2012-07-10 04:10:41 +04:00
}
2020-05-08 18:42:12 +03:00
ssize_t pstore_ftrace_combine_log ( char * * dest_log , size_t * dest_log_size ,
const char * src_log , size_t src_log_size )
{
size_t dest_size , src_size , total , dest_off , src_off ;
size_t dest_idx = 0 , src_idx = 0 , merged_idx = 0 ;
void * merged_buf ;
struct pstore_ftrace_record * drec , * srec , * mrec ;
size_t record_size = sizeof ( struct pstore_ftrace_record ) ;
dest_off = * dest_log_size % record_size ;
dest_size = * dest_log_size - dest_off ;
src_off = src_log_size % record_size ;
src_size = src_log_size - src_off ;
total = dest_size + src_size ;
merged_buf = kmalloc ( total , GFP_KERNEL ) ;
if ( ! merged_buf )
return - ENOMEM ;
drec = ( struct pstore_ftrace_record * ) ( * dest_log + dest_off ) ;
srec = ( struct pstore_ftrace_record * ) ( src_log + src_off ) ;
mrec = ( struct pstore_ftrace_record * ) ( merged_buf ) ;
while ( dest_size > 0 & & src_size > 0 ) {
if ( pstore_ftrace_read_timestamp ( & drec [ dest_idx ] ) <
pstore_ftrace_read_timestamp ( & srec [ src_idx ] ) ) {
mrec [ merged_idx + + ] = drec [ dest_idx + + ] ;
dest_size - = record_size ;
} else {
mrec [ merged_idx + + ] = srec [ src_idx + + ] ;
src_size - = record_size ;
}
}
while ( dest_size > 0 ) {
mrec [ merged_idx + + ] = drec [ dest_idx + + ] ;
dest_size - = record_size ;
}
while ( src_size > 0 ) {
mrec [ merged_idx + + ] = srec [ src_idx + + ] ;
src_size - = record_size ;
}
kfree ( * dest_log ) ;
* dest_log = merged_buf ;
* dest_log_size = total ;
return 0 ;
}
EXPORT_SYMBOL_GPL ( pstore_ftrace_combine_log ) ;