Some new features for the preempt/irqsoff tracers
Subsystems (3)
v8 cover Some new features for the preempt/irqsoff tracers
Hello all,
I have retained the fourth patch, although it was suggested that is becoming obsolete soon. I have retained it only because I do not know the status of the code that will make it obsolete. It's the last patch of the series and if there indeed is some code that will remove the latency issues from the printk code, then of course it makes sense to drop it. The first three patches will work without it.
Changes in v8:
- [PATCH 1/4]:
* Moved a forward declaration in order to make code a bit more robust.
* Converted a macro NOP to a static function so that the type is checked.
- [PATCH 2/4]:
* No change.
- [PATCH 3/4]:
* No change
- [PACTH 4/4]:
* Added a comment to explain an optimization in console_tracing_disabled().
This series is meant to address two issues with the latency tracing.
The first three patches provide a method to trace latencies that always occurs very close to each other and to differentiate between them, in spite of the fact that the latency tracers work in overwrite mode.
[PATCH 1/4] This implement fs notification for tracing_max_latency. It makes it possible for userspace to detect when a new latency has been detected.
[PATCH 2/4] This extends the preemptirq_delay_test module so that it can be used to generate a burst of closely occurring latencies.
[PATCH 3/4] This adds a user space program to the tools directory that utilizes the fs notification feature and a randomized algorithm to print out any of the latencies in a burst with approximately equal probability.
The last patch is not directly connected but earlier it didn't apply cleanly on its own. However, now it does, so in principle it could be applied separately from the others.
[PATCH 4/4] This adds the option console-latency to the trace options. This makes it possible to enable tracing of console latencies.
best regards,
Viktor
Viktor Rosendahl (BMW) (4):
ftrace: Implement fs notification for tracing_max_latency
preemptirq_delay_test: Add the burst feature and a sysfs trigger Add the latency-collector to tools
ftrace: Add an option for tracing console latencies
include/linux/irqflags.h | 22 + kernel/printk/printk.c | 6 +- kernel/trace/Kconfig | 6 +- kernel/trace/preemptirq_delay_test.c | 144 ++- kernel/trace/trace.c | 75 +- kernel/trace/trace.h | 19 + kernel/trace/trace_hwlat.c | 4 +- kernel/trace/trace_irqsoff.c | 18 + tools/Makefile | 14 +- tools/trace/Makefile | 20 + tools/trace/latency-collector.c | 1212 ++++++++++++++++++++++++++ 11 files changed, 1507 insertions(+), 33 deletions(-) create mode 100644 tools/trace/Makefile create mode 100644 tools/trace/latency-collector.c
Signature · 1 line
2.17.1
PATCH v8 1/4 ftrace: Implement fs notification for tracing_max_latency
This patch implements the feature that the tracing_max_latency file, e.g. /sys/kernel/debug/tracing/tracing_max_latency will receive notifications through the fsnotify framework when a new latency is available.
One particularly interesting use of this facility is when enabling threshold tracing, through /sys/kernel/debug/tracing/tracing_thresh, together with the preempt/irqsoff tracers. This makes it possible to implement a user space program that can, with equal probability, obtain traces of latencies that occur immediately after each other in spite of the fact that the preempt/irqsoff tracers operate in overwrite mode.
This facility works with the hwlat, preempt/irqsoff, and wakeup tracers.
The tracers may call the latency_fsnotify() from places such as __schedule() or do_idle(); this makes it impossible to call queue_work() directly without risking a deadlock. The same would happen with a softirq, kernel thread or tasklet. For this reason we use the irq_work mechanism to call queue_work().
This patch creates a new workqueue. The reason for doing this is that I wanted to use the WQ_UNBOUND and WQ_HIGHPRI flags. My thinking was that WQ_UNBOUND might help with the latency in some important cases.
If we use:
queue_work(system_highpri_wq, &tr->fsnotify_work);
then the work will (almost) always execute on the same CPU but if we are unlucky that CPU could be too busy while there could be another CPU in the system that would be able to process the work soon enough.
queue_work_on() could be used to queue the work on another CPU but it seems difficult to select the right CPU.
--- kernel/trace/trace.c | 75 +++++++++++++++++++++++++++++++++++++- kernel/trace/trace.h | 18 +++++++++ kernel/trace/trace_hwlat.c | 4 +- 3 files changed, 94 insertions(+), 3 deletions(-)
kernel/trace/trace.c +73 -2
@@ -44,6 +44,9 @@#include <linux/trace.h> #include <linux/sched/clock.h> #include <linux/sched/rt.h> +#include <linux/fsnotify.h> +#include <linux/irq_work.h> +#include <linux/workqueue.h> #include "trace.h" #include "trace_output.h"
@@ -1479,6 +1482,74 @@ static ssize_t trace_seq_to_buffer(struct trace_seq *s, void *buf, size_t cnt) }unsigned long __read_mostly tracing_thresh; +static const struct file_operations tracing_max_lat_fops; + +#if (defined(CONFIG_TRACER_MAX_TRACE ) || defined(CONFIG_HWLAT_TRACER )) && \ + defined(CONFIG_FSNOTIFY ) + +static struct workqueue_struct *fsnotify_wq; + +static void latency_fsnotify_workfn (struct work_struct *work) +{ + struct trace_array *tr = container_of(work, struct trace_array, + fsnotify_work); +fsnotify (tr->d_max_latency->d_inode,FS_MODIFY , + tr->d_max_latency->d_inode,FSNOTIFY_EVENT_INODE ,NULL ,0 ); +} + +static void latency_fsnotify_workfn_irq (struct irq_work *iwork) +{ + struct trace_array *tr = container_of(iwork, struct trace_array, + fsnotify_irqwork); +queue_work (fsnotify_wq, &tr->fsnotify_work); +} + +static void trace_create_maxlat_file (struct trace_array *tr, +struct dentry *d_tracer) +{ +INIT_WORK (&tr->fsnotify_work, latency_fsnotify_workfn); +init_irq_work (&tr->fsnotify_irqwork, latency_fsnotify_workfn_irq); + tr->d_max_latency =trace_create_file ("tracing_max_latency" ,0644 , + d_tracer, &tr->max_latency, + &tracing_max_lat_fops); +} + +__init static int latency_fsnotify_init (void ) +{ + fsnotify_wq =alloc_workqueue ("tr_max_lat_wq" , +WQ_UNBOUND |WQ_HIGHPRI ,0 ); +if (!fsnotify_wq) { +pr_err ("Unable to allocate tr_max_lat_wq\n" ); +return -ENOMEM ; + } +return 0 ; +} + +late_initcall_sync (latency_fsnotify_init); + +void latency_fsnotify (struct trace_array *tr) +{ +if (!fsnotify_wq) +return ; +/* +* We cannot call queue_work(&tr->fsnotify_work) from here because it's +* possible that we are called from __schedule() or do_idle(), which +* could cause a deadlock. +*/ +irq_work_queue (&tr->fsnotify_irqwork); +} + +/* +* (defined(CONFIG_TRACER_MAX_TRACE) || defined(CONFIG_HWLAT_TRACER)) && \ +* defined(CONFIG_FSNOTIFY) +*/ +#else + +#define trace_create_maxlat_file (tr, d_tracer) \ + trace_create_file("tracing_max_latency", 0644, d_tracer, \ + &tr->max_latency, &tracing_max_lat_fops) + +#endif #ifdef CONFIG_TRACER_MAX_TRACE /*
@@ -1518,6 +1589,7 @@ __update_max_tr(struct trace_array *tr, struct task_struct *tsk, int cpu)/* record this tasks comm */ tracing_record_cmdline (tsk); +latency_fsnotify (tr); }/**
@@ -8550,8 +8622,7 @@ init_tracer_tracefs(struct trace_array *tr, struct dentry *d_tracer)create_trace_options_dir (tr);#if defined(CONFIG_TRACER_MAX_TRACE ) || defined(CONFIG_HWLAT_TRACER ) -trace_create_file ("tracing_max_latency" ,0644 , d_tracer, - &tr->max_latency, &tracing_max_lat_fops); +trace_create_maxlat_file (tr, d_tracer);#endif if (ftrace_create_function_files (tr, d_tracer))
kernel/trace/trace.h +18 -0
@@ -16,6 +16,8 @@#include <linux/trace_events.h> #include <linux/compiler.h> #include <linux/glob.h> +#include <linux/irq_work.h> +#include <linux/workqueue.h> #ifdef CONFIG_FTRACE_SYSCALLS #include <asm/unistd.h> /* For NR_SYSCALLS */
@@ -264,6 +266,11 @@ struct trace_array {#endif #if defined(CONFIG_TRACER_MAX_TRACE ) || defined(CONFIG_HWLAT_TRACER )unsigned long max_latency; +#ifdef CONFIG_FSNOTIFY +struct dentry *d_max_latency; +struct work_struct fsnotify_work; +struct irq_work fsnotify_irqwork; +#endif #endif struct trace_pid_list __rcu *filtered_pids;/*
@@ -784,6 +791,17 @@ void update_max_tr_single(struct trace_array *tr, struct task_struct *tsk, int cpu);#endif /* CONFIG_TRACER_MAX_TRACE */ +#if (defined(CONFIG_TRACER_MAX_TRACE ) || defined(CONFIG_HWLAT_TRACER )) && \ + defined(CONFIG_FSNOTIFY ) + +void latency_fsnotify (struct trace_array *tr); + +#else + +static void latency_fsnotify (struct trace_array *tr) { } + +#endif +#ifdef CONFIG_STACKTRACE void __trace_stack (struct trace_array *tr,unsigned long flags,int skip,int pc);
kernel/trace/trace_hwlat.c +3 -1
@@ -254,8 +254,10 @@ static int get_sample(void)trace_hwlat_sample (&s);/* Keep a running maximum ever recorded hardware latency */ -if (sample > tr->max_latency) +if (sample > tr->max_latency) { tr->max_latency = sample; +latency_fsnotify (tr); + } } out:
Signature · 1 line
2.17.1
PATCH v8 2/4 preemptirq_delay_test: Add the burst feature and a sysfs trigger
In reply to Viktor Rosendahl (BMW)This burst feature enables the user to generate a burst of preempt/irqsoff latencies. This makes it possible to test whether we are able to detect latencies that systematically occur very close to each other.
The maximum burst size is 10. We also create 10 identical test functions, so that we get 10 different backtraces; this is useful when we want to test whether we can detect all the latencies in a burst. Otherwise, there would be no easy way of differentiating between which latency in a burst was captured by the tracer.
In addition, there is a sysfs trigger, so that it's not necessary to reload the module to repeat the test. The trigger will appear as /sys/kernel/preemptirq_delay_test/trigger in sysfs.
--- kernel/trace/Kconfig | 6 +- kernel/trace/preemptirq_delay_test.c | 144 +++++++++++++++++++++++---- 2 files changed, 128 insertions(+), 22 deletions(-)
kernel/trace/Kconfig +3 -3
@@ -752,9 +752,9 @@ config PREEMPTIRQ_DELAY_TEST configurable delay. The module busy waits for the duration of the critical section. - For example, the following invocation forces a one-time irq-disabled - critical section for 500us: - modprobe preemptirq_delay_test test_mode=irq delay=500000 + For example, the following invocation generates a burst of three + irq-disabled critical sections for 500us: + modprobe preemptirq_delay_test test_mode=irq delay=500 burst_size=3 If unsure, say N
kernel/trace/preemptirq_delay_test.c +125 -19
180 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH v8 3/4 Add the latency-collector to tools
In reply to Viktor Rosendahl (BMW)This is a tool that is intended to work around the fact that the preemptoff, irqsoff, and preemptirqsoff tracers only work in overwrite mode. The idea is to act randomly in such a way that we do not systematically lose any latencies, so that if enough testing is done, all latencies will be captured. If the same burst of latencies is repeated, then sooner or later we will have captured all the latencies.
It also works with the wakeup_dl, wakeup_rt, wakeup, and hwlat tracers. However, in that case it is probably not useful to use the random sleep functionality.
The reason why it may be desirable to catch all latencies with a long test campaign is that for some organizations, it's necessary to test the kernel in the field and not practical for developers to work iteratively with field testers. Because of cost and project schedules it is not possible to start a new test campaign every time a latency problem has been fixed.
It uses inotify to detect changes to /sys/kernel/debug/tracing/trace. When a latency is detected, it will either sleep or print immediately, depending on a function that act as an unfair coin toss.
If immediate print is chosen, it means that we open /sys/kernel/debug/tracing/trace and thereby cause a blackout period that will hide any subsequent latencies.
If sleep is chosen, it means that we wait before opening /sys/kernel/debug/tracing/trace, by default for 1000 ms, to see if there is another latency during this period. If there is, then we will lose the previous latency. The coin will be tossed again with a different probability, and we will either print the new latency, or possibly a subsequent one.
The probability for the unfair coin toss is chosen so that there is equal probability to obtain any of the latencies in a burst. However, this assumes that we make an assumption of how many latencies there can be. By default the program assumes that there are no more than 2 latencies in a burst, the probability of immediate printout will be:
1/2 and 1
Thus, the probability of getting each of the two latencies will be 1/2.
If we ever find that there is more than one latency in a series, meaning that we reach the probability of 1, then the table will be expanded to:
1/3, 1/2, and 1
Thus, we assume that there are no more than three latencies and each with a probability of 1/3 of being captured. If the probability of 1 is reached in the new table, that is we see more than two closely occurring latencies, then the table will again be extended, and so on.
On my systems, it seems like this scheme works fairly well, as long as the latencies we trace are long enough, 300 us seems to be enough. This userspace program receive the inotify event at the end of a latency, and it has time until the end of the next latency to react, that is to open /sys/kernel/debug/tracing/trace. Thus, if we trace latencies that are >300 us, then we have at least 300 us to react.
The minimum latency will of course not be 300 us on all systems, it will depend on the hardware, kernel version, workload and configuration.
Example output:
root@myhost:~# echo 100 > /sys/kernel/debug/tracing/tracing_thresh root@myhost:~# echo preemptirqsoff > /sys/kernel/debug/tracing/current_tracer root@myhost:~# latency-collector -rvv -a 11 & [1] 4915 root@myhost:~# Running with policy rr and priority 99. Using 3 print threads. /sys/kernel/debug/tracing/trace will be printed with random delay Start size of the probability table: 11 Print a message when prob. table table changes size: true Print a warning when an event has been lost: true Sleep time is: 1000 ms Initializing probability table to 11 Thread 4916 runs with policy rr and priority 99 Thread 4917 runs with policy rr and priority 99 Thread 4918 runs with policy rr and priority 99 Thread 4919 runs with policy rr and priority 99
root@myhost:~# modprobe preemptirq_delay_test delay=105 test_mode=alternate burst_size=10 2850.638308 Latency 1 printout skipped due to random delay 2850.638383 Latency 2 printout skipped due to random delay 2850.638497 Latency 3 immediate print
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
BEGIN <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
alternat-4922 6d... 0us!: execute_preemptirqtest <-preemptirqtest_2 alternat-4922 6d... 106us : execute_preemptirqtest <-preemptirqtest_2 alternat-4922 6d... 106us : tracer_hardirqs_on <-preemptirqtest_2 alternat-4922 6d... 108us : <stack trace>
=> preemptirqtest_2
=> preemptirq_delay_run
=> kthread
=> ret_from_fork
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
END <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
In the example above, we randomly, happened to get the third latency in a burst burst of 10. If the experiment is repeated enough times, we will get all 10.
Sometimes, there will be lost latencies, so that we get:
3054.078294 Latency 44 printout skipped due to inotify loop ..or:
3211.957685 Latency 112 printout skipped due to print loop
In my experience, these are not frequent enough to be a problem.
Also, we do not really lose any latency in these cases, it's more like we get another latency than what was intended by the design.
--- tools/Makefile | 14 +- tools/trace/Makefile | 20 + tools/trace/latency-collector.c | 1212 +++++++++++++++++++++++++++++++ 3 files changed, 1240 insertions(+), 6 deletions(-) create mode 100644 tools/trace/Makefile create mode 100644 tools/trace/latency-collector.c
tools/Makefile +8 -6
@@ -30,6 +30,7 @@ help: @echo ' selftests - various kernel selftests' @echo ' spi - spi tools' @echo ' tmon - thermal monitoring and tuning tool' + @echo ' trace - misc tracing tools' @echo ' turbostat - Intel CPU idle stats and freq reporting tool' @echo ' usb - USB testing tools' @echo ' virtio - vhost test module'
@@ -63,7 +64,7 @@ acpi: FORCE cpupower: FORCE $(call descend,power/$@) -cgroup firewire hv guest spi usb virtio vm bpf iio gpio objtool leds wmi pci firmware debugging: FORCE +cgroup firewire hv guest spi usb virtio vm bpf iio gpio objtool leds wmi pci firmware debugging trace: FORCE $(call descend,$@) liblockdep: FORCE
@@ -99,7 +100,7 @@ all: acpi cgroup cpupower gpio hv firewire liblockdep \ perf selftests spi turbostat usb \ virtio vm bpf x86_energy_perf_policy \ tmon freefall iio objtool kvm_stat wmi \ - pci debugging + pci debugging trace acpi_install: $(call descend,power/$(@:_install=),install)
@@ -107,7 +108,7 @@ acpi_install: cpupower_install: $(call descend,power/$(@:_install=),install) -cgroup_install firewire_install gpio_install hv_install iio_install perf_install spi_install usb_install virtio_install vm_install bpf_install objtool_install wmi_install pci_install debugging_install: +cgroup_install firewire_install gpio_install hv_install iio_install perf_install spi_install usb_install virtio_install vm_install bpf_install objtool_install wmi_install pci_install debugging_install trace_install: $(call descend,$(@:_install=),install) liblockdep_install:
@@ -133,7 +134,8 @@ install: acpi_install cgroup_install cpupower_install gpio_install \ perf_install selftests_install turbostat_install usb_install \ virtio_install vm_install bpf_install x86_energy_perf_policy_install \ tmon_install freefall_install objtool_install kvm_stat_install \ - wmi_install pci_install debugging_install intel-speed-select_install + wmi_install pci_install debugging_install intel-speed-select_install \ + trace_install acpi_clean: $(call descend,power/acpi,clean)
@@ -141,7 +143,7 @@ acpi_clean: cpupower_clean: $(call descend,power/cpupower,clean) -cgroup_clean hv_clean firewire_clean spi_clean usb_clean virtio_clean vm_clean wmi_clean bpf_clean iio_clean gpio_clean objtool_clean leds_clean pci_clean firmware_clean debugging_clean: +cgroup_clean hv_clean firewire_clean spi_clean usb_clean virtio_clean vm_clean wmi_clean bpf_clean iio_clean gpio_clean objtool_clean leds_clean pci_clean firmware_clean debugging_clean trace_clean: $(call descend,$(@:_clean=),clean) liblockdep_clean:
@@ -180,6 +182,6 @@ clean: acpi_clean cgroup_clean cpupower_clean hv_clean firewire_clean \ vm_clean bpf_clean iio_clean x86_energy_perf_policy_clean tmon_clean \ freefall_clean build_clean libbpf_clean libsubcmd_clean liblockdep_clean \ gpio_clean objtool_clean leds_clean wmi_clean pci_clean firmware_clean debugging_clean \ - intel-speed-select_clean + intel-speed-select_clean trace_clean .PHONY: FORCE
tools/trace/Makefile new file +20 -0
@@ -0,0 +1,20 @@ +# SPDX-License-Identifier: GPL-2.0 +# Makefile for vm tools +# +TARGETS = latency-collector +CFLAGS = -Wall -Wextra -g -O2 +LDFLAGS = -lpthread + +all: $(TARGETS) + +%: %.c + $(CC) $(CFLAGS) -o $@ $< $(LDFLAGS) + +clean: + $(RM) latency-collector + +sbindir ?= /usr/sbin + +install: all + install -d $(DESTDIR)$(sbindir) + install -m 755 -p $(TARGETS) $(DESTDIR)$(sbindir)
tools/trace/latency-collector.c new file +1212 -0
1,212 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH v8 4/4 ftrace: Add an option for tracing console latencies
In reply to Viktor Rosendahl (BMW)This new trace option "console-latency" will enable the latency tracers to trace the console latencies. Previously this has always been implicitely disabled. I guess this is because they are considered to be well known and unavoidable.
However, for some organizations it may nevertheless be desirable to trace them. Basically, we want to be able to tell that there are latencies in the system under test because someone has incorrectly enabled the serial console.
--- include/linux/irqflags.h | 22 ++++++++++++++++++++++ kernel/printk/printk.c | 6 ++++-- kernel/trace/trace.h | 1 + kernel/trace/trace_irqsoff.c | 18 ++++++++++++++++++ 4 files changed, 45 insertions(+), 2 deletions(-)
include/linux/irqflags.h +22 -0
@@ -13,6 +13,7 @@#define _LINUX_TRACE_IRQFLAGS_H#include <linux/typecheck.h> +#include <linux/types.h> #include <asm/irqflags.h> /* Currently trace_softirqs_on/off is used only by lockdep */
@@ -68,9 +69,30 @@ do { \defined (CONFIG_PREEMPT_TRACER) extern void stop_critical_timings(void);extern void start_critical_timings (void ); +extern bool console_tracing_disabled (void ); + +# define console_stop_critical_timings (flag) \ + do { \ + typecheck(bool, flag); \ + flag = console_tracing_disabled(); \ + if (flag) \ + stop_critical_timings(); \ + } while (0) + +# define console_start_critical_timings (flag) \ + do { \ + typecheck(bool, flag); \ + if (flag) \ + start_critical_timings(); \ + } while (0) +#else # define stop_critical_timings () do { } while (0)# define start_critical_timings () do { } while (0) +# define console_stop_critical_timings (flag) \ + do { typecheck(bool, flag); } while (0) +# define console_start_critical_timings (flag) \ + do { typecheck(bool, flag); } while (0)#endif /*
kernel/printk/printk.c +4 -2
@@ -2369,6 +2369,7 @@ void console_unlock(void)static char ext_text[CONSOLE_EXT_LOG_MAX ];static char text[LOG_LINE_MAX +PREFIX_MAX ];unsigned long flags; +bool cflag;bool do_cond_resched, retry;if (console_suspended) {
@@ -2469,9 +2470,10 @@ void console_unlock(void)*/ console_lock_spinning_enable (); -stop_critical_timings ();/* don't trace print latency */ +/* don't trace print latency if it's disabled */ +console_stop_critical_timings (cflag);call_console_drivers (ext_text, ext_len, text, len); -start_critical_timings (); +console_start_critical_timings (cflag);if (console_lock_spinning_disable_and_check ()) {printk_safe_exit_irqrestore (flags);
kernel/trace/trace.h +1 -0
@@ -1261,6 +1261,7 @@ extern int trace_get_user(struct trace_parser *parser, const char __user *ubuf,C (PRINTK_MSGONLY ,"printk-msg-only" ), \C (CONTEXT_INFO ,"context-info" ),/* Print pid/cpu/time */ \C (LATENCY_FMT ,"latency-format" ), \ +C (CONSOLE_LATENCY ,"console-latency" ), \C (RECORD_CMD ,"record-cmd" ), \C (RECORD_TGID ,"record-tgid" ), \ C(OVERWRITE, "overwrite"), \
kernel/trace/trace_irqsoff.c +18 -0
@@ -456,6 +456,24 @@ void stop_critical_timings(void)EXPORT_SYMBOL_GPL (stop_critical_timings);NOKPROBE_SYMBOL (stop_critical_timings); +bool console_tracing_disabled (void ) +{ +struct trace_array *tr = irqsoff_trace; +int pc =preempt_count (); + +/* +* If tracing is disabled, then the question of whether to trace console +* latencies is moot. By always returning false here we save the caller +* the calls to start/stop_critical_timings(). These calls would not do +* anything anyway. +*/ +if (!preempt_trace (pc) && !irq_trace ()) +return false; + +return !(tr->trace_flags &TRACE_ITER_CONSOLE_LATENCY ); +} +EXPORT_SYMBOL_GPL (console_tracing_disabled); +#ifdef CONFIG_FUNCTION_TRACER static bool function_enabled;
Signature · 1 line
2.17.1
Re: [PATCH v8 4/4] ftrace: Add an option for tracing console latencies
Quoted 107 lines · Viktor Rosendahl (BMW)
This new trace option "console-latency" will enable the latency tracers to trace the console latencies. Previously this has always been implicitely disabled. I guess this is because they are considered to be well known and unavoidable.
However, for some organizations it may nevertheless be desirable to trace them. Basically, we want to be able to tell that there are latencies in the system under test because someone has incorrectly enabled the serial console.
Signed-off-by Viktor Rosendahl (BMW) <[email protected]>--- include/linux/irqflags.h | 22 ++++++++++++++++++++++ kernel/printk/printk.c | 6 ++++-- kernel/trace/trace.h | 1 + kernel/trace/trace_irqsoff.c | 18 ++++++++++++++++++ 4 files changed, 45 insertions(+), 2 deletions(-)include/linux/irqflags.h +22
-0@@ -13,6 +13,7 @@#define _LINUX_TRACE_IRQFLAGS_H#include <linux/typecheck.h> +#include <linux/types.h> #include <asm/irqflags.h> /* Currently trace_softirqs_on/off is used only by lockdep */ @@ -68,9 +69,30 @@ do { \defined (CONFIG_PREEMPT_TRACER) extern void stop_critical_timings(void);extern void start_critical_timings (void ); +extern bool console_tracing_disabled (void ); + +# define console_stop_critical_timings (flag) \ + do { \ + typecheck(bool, flag); \ + flag = console_tracing_disabled(); \ + if (flag) \ + stop_critical_timings(); \ + } while (0) + +# define console_start_critical_timings (flag) \ + do { \ + typecheck(bool, flag); \ + if (flag) \ + start_critical_timings(); \ + } while (0) +#else # define stop_critical_timings () do { } while (0)# define start_critical_timings () do { } while (0) +# define console_stop_critical_timings (flag) \ + do { typecheck(bool, flag); } while (0) +# define console_start_critical_timings (flag) \ + do { typecheck(bool, flag); } while (0)#endif /* kernel/printk/printk.c +4
-2@@ -2369,6 +2369,7 @@ void console_unlock(void)static char ext_text[CONSOLE_EXT_LOG_MAX ];static char text[LOG_LINE_MAX +PREFIX_MAX ];unsigned long flags; +bool cflag;bool do_cond_resched, retry;if (console_suspended) {@@ -2469,9 +2470,10 @@ void console_unlock(void)*/ console_lock_spinning_enable (); -stop_critical_timings ();/* don't trace print latency */ +/* don't trace print latency if it's disabled */ +console_stop_critical_timings (cflag);call_console_drivers (ext_text, ext_len, text, len); -start_critical_timings (); +console_start_critical_timings (cflag);if (console_lock_spinning_disable_and_check ()) {printk_safe_exit_irqrestore (flags);kernel/trace/trace.h +1
-0@@ -1261,6 +1261,7 @@ extern int trace_get_user(struct trace_parser *parser, const char __user *ubuf,C (PRINTK_MSGONLY ,"printk-msg-only" ), \C (CONTEXT_INFO ,"context-info" ),/* Print pid/cpu/time */ \C (LATENCY_FMT ,"latency-format" ), \ +C (CONSOLE_LATENCY ,"console-latency" ), \C (RECORD_CMD ,"record-cmd" ), \C (RECORD_TGID ,"record-tgid" ), \ C(OVERWRITE, "overwrite"), \kernel/trace/trace_irqsoff.c +1
-0@@ -456,6 +456,24 @@ void stop_critical_timings(void)EXPORT_SYMBOL_GPL (stop_critical_timings);NOKPROBE_SYMBOL (stop_critical_timings); +bool console_tracing_disabled (void )
kernel/trace/trace_irqsoff.c void stop_critical_timings(void) · line 469
Quoted 10 lines
kernel/trace/trace_irqsoff.c +10
-0+{ +struct trace_array *tr = irqsoff_trace; +int pc =preempt_count (); + +/* +* If tracing is disabled, then the question of whether to trace console +* latencies is moot. By always returning false here we save the caller +* the calls to start/stop_critical_timings(). These calls would not do +* anything anyway. +*/
I thought you were going to drop this patch, or at least I had suggested so but did not hear a reply from you: https://lkml.org/lkml/2019/10/3/464
Thanks for adding the comments though.
Steve, what do you think about this patch? I am worried the extra flag may go obsolete at some point if the console latencies are fixed and we have yet another knob.
thanks,
- Joel
Quoted 13 lines
kernel/trace/trace_irqsoff.c +7
-0+if (!preempt_trace (pc) && !irq_trace ()) +return false; + +return !(tr->trace_flags &TRACE_ITER_CONSOLE_LATENCY ); +} +EXPORT_SYMBOL_GPL (console_tracing_disabled); +#ifdef CONFIG_FUNCTION_TRACER static bool function_enabled;Signature · 1 line
2.17.1
Re: [PATCH v8 4/4] ftrace: Add an option for tracing console latencies
Den ons 9 okt. 2019 kl 16:11 skrev Joel Fernandes <[email protected]>:
Quoted 108 lines · Viktor Rosendahl (BMW)
Quoted 106 lines
This new trace option "console-latency" will enable the latency tracers to trace the console latencies. Previously this has always been implicitely disabled. I guess this is because they are considered to be well known and unavoidable.
However, for some organizations it may nevertheless be desirable to trace them. Basically, we want to be able to tell that there are latencies in the system under test because someone has incorrectly enabled the serial console.
Signed-off-by Viktor Rosendahl (BMW) <[email protected]>--- include/linux/irqflags.h | 22 ++++++++++++++++++++++ kernel/printk/printk.c | 6 ++++-- kernel/trace/trace.h | 1 + kernel/trace/trace_irqsoff.c | 18 ++++++++++++++++++ 4 files changed, 45 insertions(+), 2 deletions(-)include/linux/irqflags.h +22
-0@@ -13,6 +13,7 @@#define _LINUX_TRACE_IRQFLAGS_H#include <linux/typecheck.h> +#include <linux/types.h> #include <asm/irqflags.h> /* Currently trace_softirqs_on/off is used only by lockdep */ @@ -68,9 +69,30 @@ do { \defined (CONFIG_PREEMPT_TRACER) extern void stop_critical_timings(void);extern void start_critical_timings (void ); +extern bool console_tracing_disabled (void ); + +# define console_stop_critical_timings (flag) \ + do { \ + typecheck(bool, flag); \ + flag = console_tracing_disabled(); \ + if (flag) \ + stop_critical_timings(); \ + } while (0) + +# define console_start_critical_timings (flag) \ + do { \ + typecheck(bool, flag); \ + if (flag) \ + start_critical_timings(); \ + } while (0) +#else # define stop_critical_timings () do { } while (0)# define start_critical_timings () do { } while (0) +# define console_stop_critical_timings (flag) \ + do { typecheck(bool, flag); } while (0) +# define console_start_critical_timings (flag) \ + do { typecheck(bool, flag); } while (0)#endif /* kernel/printk/printk.c +4
-2@@ -2369,6 +2369,7 @@ void console_unlock(void)static char ext_text[CONSOLE_EXT_LOG_MAX ];static char text[LOG_LINE_MAX +PREFIX_MAX ];unsigned long flags; +bool cflag;bool do_cond_resched, retry;if (console_suspended) {@@ -2469,9 +2470,10 @@ void console_unlock(void)*/ console_lock_spinning_enable (); -stop_critical_timings ();/* don't trace print latency */ +/* don't trace print latency if it's disabled */ +console_stop_critical_timings (cflag);call_console_drivers (ext_text, ext_len, text, len); -start_critical_timings (); +console_start_critical_timings (cflag);if (console_lock_spinning_disable_and_check ()) {printk_safe_exit_irqrestore (flags);kernel/trace/trace.h +1
-0@@ -1261,6 +1261,7 @@ extern int trace_get_user(struct trace_parser *parser, const char __user *ubuf,C (PRINTK_MSGONLY ,"printk-msg-only" ), \C (CONTEXT_INFO ,"context-info" ),/* Print pid/cpu/time */ \C (LATENCY_FMT ,"latency-format" ), \ +C (CONSOLE_LATENCY ,"console-latency" ), \C (RECORD_CMD ,"record-cmd" ), \C (RECORD_TGID ,"record-tgid" ), \ C(OVERWRITE, "overwrite"), \kernel/trace/trace_irqsoff.c +0
-0@@ -456,6 +456,24 @@ void stop_critical_timings(void)EXPORT_SYMBOL_GPL (stop_critical_timings);NOKPROBE_SYMBOL (stop_critical_timings);
Quoted 15 lines
kernel/trace/trace_irqsoff.c void stop_critical_timings(void) · line 469
Quoted 11 lines
kernel/trace/trace_irqsoff.c +11
-0+bool console_tracing_disabled (void ) +{ +struct trace_array *tr = irqsoff_trace; +int pc =preempt_count (); + +/* +* If tracing is disabled, then the question of whether to trace console +* latencies is moot. By always returning false here we save the caller +* the calls to start/stop_critical_timings(). These calls would not do +* anything anyway. +*/ I thought you were going to drop this patch, or at least I had suggested so but did not hear a reply from you: https://lkml.org/lkml/2019/10/3/464
Apologies, I should have replied there but I have been a bit busy the last few days with other topics, and I felt a bit indecisive about that point, so I just sloppily addressed the issue in the cover letter of this new series:
"I have retained the fourth patch, although it was suggested that is becoming obsolete soon. I have retained it only because I do not know the status of the code that will make it obsolete. It's the last patch of the series and if there indeed is some code that will remove the latency issues from the printk code, then of course it makes sense to drop it. The first three patches will work without it."
I thought that, since it's the last in the series, it would be possible for maintainers to just take the first three if the last one is not wanted.
For me it solves a rather important problem though, so if the code that will make it obsolete isn't available for some time, then perhaps it should be considered as a temporary solution.
Of course, if there is a commitment to never remove any knobs from /sys/kernel/debug/tracing/trace_options, then I can easily understand that it's not wanted as a temporary fix.
best regards,
Viktor
Quoted 23 lines
Thanks for adding the comments though.
Steve, what do you think about this patch? I am worried the extra flag may go obsolete at some point if the console latencies are fixed and we have yet another knob.
thanks,
- Joel
Quoted 13 lines
kernel/trace/trace_irqsoff.c +7
-1+if (!preempt_trace (pc) && !irq_trace ()) +return false; + +return !(tr->trace_flags &TRACE_ITER_CONSOLE_LATENCY ); +} +EXPORT_SYMBOL_GPL (console_tracing_disabled); +#ifdef CONFIG_FUNCTION_TRACER static bool function_enabled; --2.17.1
Steven Rostedt
maintainerRe: [PATCH v8 4/4] ftrace: Add an option for tracing console latencies
Quoted 16 lines · On Wed, 9 Oct 2019 16:51:07 +0200 Viktor Rosendahl…
Apologies, I should have replied there but I have been a bit busy the last few days with other topics, and I felt a bit indecisive about that point, so I just sloppily addressed the issue in the cover letter of this new series:
"I have retained the fourth patch, although it was suggested that is becoming obsolete soon. I have retained it only because I do not know the status of the code that will make it obsolete. It's the last patch of the series and if there indeed is some code that will remove the latency issues from the printk code, then of course it makes sense to drop it. The first three patches will work without it."
I thought that, since it's the last in the series, it would be possible for maintainers to just take the first three if the last one is not wanted.
Quoted 7 lines
For me it solves a rather important problem though, so if the code that will make it obsolete isn't available for some time, then perhaps it should be considered as a temporary solution.
Of course, if there is a commitment to never remove any knobs from
/sys/kernel/debug/tracing/trace_options, then I can easily understand that it's not wanted as a temporary fix.
There isn't quite a commitment to not remove knobs, but if a tool starts relying on a knob, then, the answer is yes there is :-p
As this will hopefully become something we don't worry about in the future, I would rather have this be a kernel command line option. This way, it wont be something that tools can really check for.
If you add a trace_console_latency option to the kernel command line, we can enable it that way. And then when it becomes obsolete, we can simply remove it, without breaking any tools.
Would that work for you?
-- Steve
Re: [PATCH v8 4/4] ftrace: Add an option for tracing console latencies
Den ons 9 okt. 2019 kl 20:08 skrev Steven Rostedt <[email protected]>:
Quoted 35 lines
Quoted 16 lines · On Wed, 9 Oct 2019 16:51:07 +0200 Viktor Rosendahl…
Apologies, I should have replied there but I have been a bit busy the last few days with other topics, and I felt a bit indecisive about that point, so I just sloppily addressed the issue in the cover letter of this new series:
"I have retained the fourth patch, although it was suggested that is becoming obsolete soon. I have retained it only because I do not know the status of the code that will make it obsolete. It's the last patch of the series and if there indeed is some code that will remove the latency issues from the printk code, then of course it makes sense to drop it. The first three patches will work without it."
I thought that, since it's the last in the series, it would be possible for maintainers to just take the first three if the last one is not wanted.
Quoted 7 lines
For me it solves a rather important problem though, so if the code that will make it obsolete isn't available for some time, then perhaps it should be considered as a temporary solution.
Of course, if there is a commitment to never remove any knobs from
/sys/kernel/debug/tracing/trace_options, then I can easily understand that it's not wanted as a temporary fix.There isn't quite a commitment to not remove knobs, but if a tool starts relying on a knob, then, the answer is yes there is :-p
As this will hopefully become something we don't worry about in the future, I would rather have this be a kernel command line option. This way, it wont be something that tools can really check for.
Quoted 6 lines
If you add a
trace_console_latencyoption to the kernel command line, we can enable it that way. And then when it becomes obsolete, we can simply remove it, without breaking any tools.Would that work for you?
Sounds good to me. I will try to adjust the patch accordingly within a few days.
best regards,
Viktor
Quoted 1 line
-- Steve
Steven Rostedt
maintainerRe: [PATCH v8 4/4] ftrace: Add an option for tracing console latencies
Quoted 1 line · On Thu, 10 Oct 2019 09:57:31 +0200 Viktor Rosendahl…
Sounds good to me. I will try to adjust the patch accordingly within a few days.
OK,
Also, I may hold off on patch 3. I want to make sure that adding a new directory to tools is OK, and see if there's not other things we can add there.
-- Steve