From patchwork Thu Mar 23 17:42:02 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Daniel Lezcano X-Patchwork-Id: 95915 Delivered-To: patch@linaro.org Received: by 10.140.89.233 with SMTP id v96csp852444qgd; Thu, 23 Mar 2017 10:43:24 -0700 (PDT) X-Received: by 10.84.241.69 with SMTP id u5mr5230765plm.107.1490291004866; Thu, 23 Mar 2017 10:43:24 -0700 (PDT) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p6si4563779pfl.58.2017.03.23.10.43.24; Thu, 23 Mar 2017 10:43:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965408AbdCWRnY (ORCPT + 17 others); Thu, 23 Mar 2017 13:43:24 -0400 Received: from mail-wr0-f181.google.com ([209.85.128.181]:33645 "EHLO mail-wr0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755091AbdCWRmc (ORCPT ); Thu, 23 Mar 2017 13:42:32 -0400 Received: by mail-wr0-f181.google.com with SMTP id y90so34835121wrb.0 for ; Thu, 23 Mar 2017 10:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=8+5Ktagry9szWGI2UjtwdiOBS0bEnAHur0RjUqwDTeo=; b=NvDv2LP9YpoG+S7QoriW08Z7jiWNKB8vwzlv5OalK3uWlqYdUqWKBNniDkMi0KKX+d FolXFoj0/qyJi2GMAt5R3Bxf9Pnh8FAS3FIAKTGzkaWPluuZ4G6GPvh+FjPSiFUfGmOx HEmDrFyBUgCJm5XnWBTiIVYiawSEvVmxNpb0A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=8+5Ktagry9szWGI2UjtwdiOBS0bEnAHur0RjUqwDTeo=; b=NGOkj0JHiXORt3Q1s/6vf9YrQJmQLW1+1HaPXmD7OxVwqwYiQPCRELCWQzUOueOmZ/ QNwKMHiZGS/uRqoF5uqx/5EoL2Fpcf8GlLxZjnHvVhk/f0TIOaKDzNriNOwD5jpHYWSN rh7qJqLBctN4gRHTA8+fVx1qSiwPYqVUFGrUP39/wBFND6HEc9n4tFFPO5W6YnHAltti DA+A7s/MLepAYCZpBZZO8t5qL9KfHntzcIyaeFM229DI1Ym4Hr9TidULJ/jXUGgB9ix3 /doTqslvIOXd9Rv5V4yzi0lNd4MeKMAbZyLGmuxYyYv6uCtvZ64XZT8LrqXGvfGkWFWK zQpg== X-Gm-Message-State: AFeK/H2QnUwc2pcqT57iu3w6LqvxtG8mv89+keiGHAoxwig2hLmhpSO/ttZYDrkhRTsQlT+1 X-Received: by 10.223.170.70 with SMTP id q6mr4164349wrd.162.1490290950108; Thu, 23 Mar 2017 10:42:30 -0700 (PDT) Received: from localhost.localdomain (lft31-1-88-121-166-205.fbx.proxad.net. [88.121.166.205]) by smtp.gmail.com with ESMTPSA id o22sm6690566wro.13.2017.03.23.10.42.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 23 Mar 2017 10:42:29 -0700 (PDT) From: Daniel Lezcano To: tglx@linutronix.de Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, nicolas.pitre@linaro.org, rafael@kernel.org, vincent.guittot@linaro.org Subject: [PATCH V8 2/3] irq: Track the interrupt timings Date: Thu, 23 Mar 2017 18:42:02 +0100 Message-Id: <1490290924-12958-2-git-send-email-daniel.lezcano@linaro.org> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1490290924-12958-1-git-send-email-daniel.lezcano@linaro.org> References: <1490290924-12958-1-git-send-email-daniel.lezcano@linaro.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The interrupt framework gives a lot of information about each interrupt. It does not keep track of when those interrupts occur though. This patch provides a mean to record the timestamp for each interrupt occurrences in a per-CPU circular buffer to help with the prediction of the next occurrence using a statistical model. Each CPU can store IRQ_TIMINGS_SIZE events , the current value of IRQ_TIMINGS_SIZE is 32. A static key is introduced so when the irq prediction is switched off at runtime, we can reduce the overhead near to zero. The irq timings is supposed to be potentially used by different sub-systems and for this reason the static key is a ref counter, so when the last use releases the irq timings that will result on the effective deactivation of the irq measurement. It results in most of the code in internals.h for inline reason and a very few in the new file timings.c. The latter will contain more in the next patch which will provide the statistical model for the next event prediction. Note this code is by default *not* compiled in the kernel. Signed-off-by: Daniel Lezcano Acked-by: Nicolas Pitre --- V8: - Replaced percpu field in the irqdesc by a percpu array containing the timings and the associated irq. The function irq_timings_get_next() is no longer needed, so it is removed - Removed all unused code resulting from the conversion irqdesc->percpu timings storage V7: - Mentionned in the irq_timings_get_next() function description, the function must be called inside a rcu read locked section V6: - Renamed handle_irq_timings to record_irq_time - Stored the event time instead of the interval time - Removed the 'timestamp' field from the timings structure - Moved _handle_irq_timings content inside record_irq_time V5: - Changed comment about 'deterministic' as the comment is confusing - Added license comment in the header - Replaced irq_timings_get/put by irq_timings_enable/disable - Moved IRQS_TIMINGS check in the handle_timings inline function - Dropped 'if !prev' as it is pointless - Stored time interval in nsec basis with u64 instead of u32 - Removed redundant store - Removed the math V4: - Added a static key - Added more comments for irq_timings_get_next() - Unified some function names to be prefixed by 'irq_timings_...' - Fixed a rebase error V3: - Replaced ktime_get() by local_clock() - Shared irq are not handled - Simplified code by adding the timing in the irqdesc struct - Added a function to browse the irq timings V2: - Fixed kerneldoc comment - Removed data field from the struct irq timing - Changed the lock section comment - Removed semi-colon style with empty stub - Replaced macro by static inline - Fixed static functions declaration RFC: - initial posting --- include/linux/interrupt.h | 5 ++++ kernel/irq/Kconfig | 3 +++ kernel/irq/Makefile | 1 + kernel/irq/handle.c | 2 ++ kernel/irq/internals.h | 67 +++++++++++++++++++++++++++++++++++++++++++++++ kernel/irq/manage.c | 3 +++ kernel/irq/timings.c | 30 +++++++++++++++++++++ 7 files changed, 111 insertions(+) create mode 100644 kernel/irq/timings.c -- 1.9.1 diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h index bc3b675..c050333 100644 --- a/include/linux/interrupt.h +++ b/include/linux/interrupt.h @@ -704,6 +704,11 @@ static inline void init_irq_proc(void) } #endif +#ifdef CONFIG_IRQ_TIMINGS +void irq_timings_enable(void); +void irq_timings_disable(void); +#endif + struct seq_file; int show_interrupts(struct seq_file *p, void *v); int arch_show_interrupts(struct seq_file *p, int prec); diff --git a/kernel/irq/Kconfig b/kernel/irq/Kconfig index 3bbfd6a..38e551d 100644 --- a/kernel/irq/Kconfig +++ b/kernel/irq/Kconfig @@ -81,6 +81,9 @@ config GENERIC_MSI_IRQ_DOMAIN config HANDLE_DOMAIN_IRQ bool +config IRQ_TIMINGS + bool + config IRQ_DOMAIN_DEBUG bool "Expose hardware/virtual IRQ mapping via debugfs" depends on IRQ_DOMAIN && DEBUG_FS diff --git a/kernel/irq/Makefile b/kernel/irq/Makefile index 1d3ee31..efb5f14 100644 --- a/kernel/irq/Makefile +++ b/kernel/irq/Makefile @@ -10,3 +10,4 @@ obj-$(CONFIG_PM_SLEEP) += pm.o obj-$(CONFIG_GENERIC_MSI_IRQ) += msi.o obj-$(CONFIG_GENERIC_IRQ_IPI) += ipi.o obj-$(CONFIG_SMP) += affinity.o +obj-$(CONFIG_IRQ_TIMINGS) += timings.o diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c index d3f2490..eb4d3e8 100644 --- a/kernel/irq/handle.c +++ b/kernel/irq/handle.c @@ -138,6 +138,8 @@ irqreturn_t __handle_irq_event_percpu(struct irq_desc *desc, unsigned int *flags unsigned int irq = desc->irq_data.irq; struct irqaction *action; + record_irq_time(desc); + for_each_action_of_desc(desc, action) { irqreturn_t res; diff --git a/kernel/irq/internals.h b/kernel/irq/internals.h index bc226e7..abaadaa 100644 --- a/kernel/irq/internals.h +++ b/kernel/irq/internals.h @@ -8,6 +8,7 @@ #include #include #include +#include #ifdef CONFIG_SPARSE_IRQ # define IRQ_BITMAP_BITS (NR_IRQS + 8196) @@ -57,6 +58,7 @@ enum { IRQS_WAITING = 0x00000080, IRQS_PENDING = 0x00000200, IRQS_SUSPENDED = 0x00000800, + IRQS_TIMINGS = 0x00001000, }; #include "debug.h" @@ -226,3 +228,68 @@ static inline int irq_desc_is_chained(struct irq_desc *desc) static inline void irq_pm_remove_action(struct irq_desc *desc, struct irqaction *action) { } #endif + +#ifdef CONFIG_IRQ_TIMINGS + +#define IRQ_TIMINGS_SHIFT 5 +#define IRQ_TIMINGS_SIZE (1 << IRQ_TIMINGS_SHIFT) +#define IRQ_TIMINGS_MASK (IRQ_TIMINGS_SIZE - 1) + +struct irq_timing { + u32 irq; + u64 ts; +}; + +struct irq_timings { + struct irq_timing values[IRQ_TIMINGS_SIZE]; /* our circular buffer */ + unsigned int count; /* Number of interruptions since last inspection */ +}; + +DECLARE_PER_CPU(struct irq_timings, irq_timings); + +static inline void remove_timings(struct irq_desc *desc) +{ + desc->istate &= ~IRQS_TIMINGS; +} + +static inline void setup_timings(struct irq_desc *desc, struct irqaction *act) +{ + /* + * We don't need the measurement because the idle code already + * knows the next expiry event. + */ + if (act->flags & __IRQF_TIMER) + return; + + desc->istate |= IRQS_TIMINGS; +} + +extern struct static_key_false irq_timing_enabled; + +/* + * The function record_irq_time is only called in one place in the + * interrupts handler. We want this function always inline so the code + * inside is embedded in the function and the static key branching + * code can act at the higher level. Without the explicit + * __always_inline we can end up with a function call and a small + * overhead in the hotpath for nothing. + */ +static __always_inline void record_irq_time(struct irq_desc *desc) +{ + if (static_key_enabled(&irq_timing_enabled)) { + if (desc->istate & IRQS_TIMINGS) { + struct irq_timings *timings = this_cpu_ptr(&irq_timings); + unsigned int index = timings->count & IRQ_TIMINGS_MASK; + + timings->values[index].ts = local_clock(); + timings->values[index].irq = irq_desc_get_irq(desc); + timings->count++; + } + } +} +#else +static inline void remove_timings(struct irq_desc *desc) {} +static inline void setup_timings(struct irq_desc *desc, + struct irqaction *act) {}; +static inline void record_irq_time(struct irq_desc *desc) {} +#endif /* CONFIG_IRQ_TIMINGS */ diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c index c0a23e2..da799d3 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c @@ -1370,6 +1370,8 @@ static void irq_release_resources(struct irq_desc *desc) raw_spin_unlock_irqrestore(&desc->lock, flags); + setup_timings(desc, new); + /* * Strictly no need to wake it up, but hung_task complains * when no hard interrupt wakes the thread up. @@ -1498,6 +1500,7 @@ static struct irqaction *__free_irq(unsigned int irq, void *dev_id) irq_settings_clr_disable_unlazy(desc); irq_shutdown(desc); irq_release_resources(desc); + remove_timings(desc); } #ifdef CONFIG_SMP diff --git a/kernel/irq/timings.c b/kernel/irq/timings.c new file mode 100644 index 0000000..21ceca8 --- /dev/null +++ b/kernel/irq/timings.c @@ -0,0 +1,30 @@ +/* + * linux/kernel/irq/timings.c + * + * Copyright (C) 2016, Linaro Ltd - Daniel Lezcano + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + */ +#include +#include +#include +#include + +#include "internals.h" + +DEFINE_STATIC_KEY_FALSE(irq_timing_enabled); + +DEFINE_PER_CPU(struct irq_timings, irq_timings); + +void irq_timings_enable(void) +{ + static_branch_inc(&irq_timing_enabled); +} + +void irq_timings_disable(void) +{ + static_branch_dec(&irq_timing_enabled); +} From patchwork Thu Mar 23 17:42:03 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Daniel Lezcano X-Patchwork-Id: 95914 Delivered-To: patch@linaro.org Received: by 10.140.89.233 with SMTP id v96csp852171qgd; Thu, 23 Mar 2017 10:42:39 -0700 (PDT) X-Received: by 10.84.238.207 with SMTP id l15mr5197126pln.90.1490290959460; Thu, 23 Mar 2017 10:42:39 -0700 (PDT) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x8si4542478pfk.349.2017.03.23.10.42.39; Thu, 23 Mar 2017 10:42:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756579AbdCWRmh (ORCPT + 17 others); Thu, 23 Mar 2017 13:42:37 -0400 Received: from mail-wr0-f177.google.com ([209.85.128.177]:33659 "EHLO mail-wr0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965071AbdCWRme (ORCPT ); Thu, 23 Mar 2017 13:42:34 -0400 Received: by mail-wr0-f177.google.com with SMTP id y90so34835686wrb.0 for ; Thu, 23 Mar 2017 10:42:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=+7/n0LfxVK3zaaFLSVt921DRarPVav/8mjXlz4CCBzg=; b=HJ1M2DFvBuq8nHCTCWrpsWLNN0WjVA9pFcr1IdqGuUDqn7eqruAm9tXlJY51OFodI9 EzPOBglw6xuQOhgxJ+6f0OjmKcIHnOXw6Ql5ZOqgvShywVV7frk6hNjrfVX81ETRa1sL RufIeNSmbR3oLL6R5FleCnU4qK4PDnAgPWWyY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=+7/n0LfxVK3zaaFLSVt921DRarPVav/8mjXlz4CCBzg=; b=HUi72H0pxy17iOG/6NuXFLxSwOJtp/Pqo6CSgoAs89qYASaMpMMK4mI4JSM4AxcDjV JbY/2wt4u5XjWQRWDAW21yJcb3SM1kUS/ocVrjY+h2IKKu3tkqXA+Dq3LduSujrlnn96 MFVBZ9dVc1WZ7KpnXI9ai6kY9sdJ/ZuDbdX09NZhyM+vceajMgAzV+fXEDb+Q0wlkTRg jVuUm/QwCkfpOX4iJLUee18/JzY0B7D4Kpo2BPmlPrOZeMXckZ5KtBG0RxEz+IuB47hS F0VuQQ4WjssoeJxLSbOkb8/9x4Vvxe8v+Oh0l1+eN+n0YW+Pv4xZ4jBwl4h33ZFfD6FY IvrQ== X-Gm-Message-State: AFeK/H0BQRt/wagfMLRjOT/0L3E5YLeseq+mT17dLwWv6pk/lkXe8IRthUeBiMTnRMBca36f X-Received: by 10.223.183.6 with SMTP id l6mr1706593wre.192.1490290951873; Thu, 23 Mar 2017 10:42:31 -0700 (PDT) Received: from localhost.localdomain (lft31-1-88-121-166-205.fbx.proxad.net. [88.121.166.205]) by smtp.gmail.com with ESMTPSA id o22sm6690566wro.13.2017.03.23.10.42.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 23 Mar 2017 10:42:31 -0700 (PDT) From: Daniel Lezcano To: tglx@linutronix.de Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, nicolas.pitre@linaro.org, rafael@kernel.org, vincent.guittot@linaro.org Subject: [PATCH V8 3/3] irq: Compute the periodic interval for interrupts Date: Thu, 23 Mar 2017 18:42:03 +0100 Message-Id: <1490290924-12958-3-git-send-email-daniel.lezcano@linaro.org> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1490290924-12958-1-git-send-email-daniel.lezcano@linaro.org> References: <1490290924-12958-1-git-send-email-daniel.lezcano@linaro.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org An interrupt behaves with a burst of activity with periodic interval of time followed by one or two peaks of longer interval. As the time intervals are periodic, statistically speaking they follow a normal distribution and each interrupts can be tracked individually. This patch does statistics on all interrupts, except the timers which are deterministic by essence. The goal is to extract the periodicity for each interrupt, with the last timestamp and sum them, so we have the next event. Taking the earliest prediction gives the expected wakeup on the system (assuming a timer won't expire before). As stated in the previous patch, this code is not enabled in the kernel by default. Signed-off-by: Daniel Lezcano --- include/linux/interrupt.h | 1 + kernel/irq/internals.h | 19 +++ kernel/irq/timings.c | 344 ++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 364 insertions(+) -- 1.9.1 diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h index c050333..62bb0c9 100644 --- a/include/linux/interrupt.h +++ b/include/linux/interrupt.h @@ -707,6 +707,7 @@ static inline void init_irq_proc(void) #ifdef CONFIG_IRQ_TIMINGS void irq_timings_enable(void); void irq_timings_disable(void); +u64 irq_timings_next_event(u64 now); #endif struct seq_file; diff --git a/kernel/irq/internals.h b/kernel/irq/internals.h index abaadaa..677c1a2 100644 --- a/kernel/irq/internals.h +++ b/kernel/irq/internals.h @@ -247,13 +247,21 @@ struct irq_timings { DECLARE_PER_CPU(struct irq_timings, irq_timings); +extern void irq_timings_free(int irq); +extern int irq_timings_alloc(int irq); + static inline void remove_timings(struct irq_desc *desc) { desc->istate &= ~IRQS_TIMINGS; + + irq_timings_free(irq_desc_get_irq(desc)); } static inline void setup_timings(struct irq_desc *desc, struct irqaction *act) { + int irq = irq_desc_get_irq(desc); + int ret; + /* * We don't need the measurement because the idle code already * knows the next expiry event. @@ -261,6 +269,17 @@ static inline void setup_timings(struct irq_desc *desc, struct irqaction *act) if (act->flags & __IRQF_TIMER) return; + /* + * In case the timing allocation fails, we just want to warn, + * not fail, so letting the system boot anyway. + */ + ret = irq_timings_alloc(irq); + if (ret) { + pr_warn("Failed to allocate irq timing stats for irq%d (%d)", + irq, ret); + return; + } + desc->istate |= IRQS_TIMINGS; } diff --git a/kernel/irq/timings.c b/kernel/irq/timings.c index 21ceca8..a3879cb 100644 --- a/kernel/irq/timings.c +++ b/kernel/irq/timings.c @@ -9,9 +9,14 @@ * */ #include +#include #include #include +#include #include +#include + +#include #include "internals.h" @@ -19,6 +24,18 @@ DEFINE_PER_CPU(struct irq_timings, irq_timings); +struct irq_stat { + u64 ne; /* next event */ + u64 lts; /* last timestamp */ + u64 variance; /* variance */ + u32 avg; /* mean value */ + u32 count; /* number of samples */ + int anomalies; /* number of consecutives anomalies */ + int valid; /* behaviour of the interrupt */ +}; + +static DEFINE_IDR(irq_stats); + void irq_timings_enable(void) { static_branch_inc(&irq_timing_enabled); @@ -28,3 +45,330 @@ void irq_timings_disable(void) { static_branch_dec(&irq_timing_enabled); } + +/** + * irqs_update - update the irq timing statistics with a new timestamp + * + * @irqs: an irq_stat struct pointer + * @ts: the new timestamp + * + * ** This function must be called with the local irq disabled ** + * + * The statistics are computed online, in other words, the code is + * designed to compute the statistics on a stream of values rather + * than doing multiple passes on the values to compute the average, + * then the variance. The integer division introduces a loss of + * precision but with an acceptable error margin regarding the results + * we would have with the double floating precision: we are dealing + * with nanosec, so big numbers, consequently the mantisse is + * negligeable, especially when converting the time in usec + * afterwards. + * + * The computation happens at idle time. When the CPU is not idle, the + * interrupts' timestamps are stored in the circular buffer, when the + * CPU goes idle and this routine is called, all the buffer's values + * are injected in the statistical model continuying to extend the + * statistics from the previous busy-idle cycle. + * + * The observations showed a device will trigger a burst of periodic + * interrupts followed by one or two peaks of longer time, for + * instance when a SD card device flushes its cache, then the periodic + * intervals occur again. A one second inactivity period resets the + * stats, that gives us the certitude the statistical values won't + * exceed 1x10^9, thus the computation won't overflow. + * + * Basically, the purpose of the algorithm is to watch the periodic + * interrupts and eliminate the peaks. + * + * An interrupt is considered periodically stable if the interval of + * its occurences follow the normal distribution, thus the values + * comply with: + * + * avg - 3 x stddev < value < avg + 3 x stddev + * + * Which can be simplified to: + * + * -3 x stddev < value - avg < 3 x stddev + * + * abs(value - avg) < 3 x stddev + * + * In order to save a costly square root computation, we use the + * variance. For the record, stddev = sqrt(variance). The equation + * above becomes: + * + * abs(value - avg) < 3 x sqrt(variance) + * + * And finally we square it: + * + * (value - avg) ^ 2 < (3 x sqrt(variance)) ^ 2 + * + * (value - avg) x (value - avg) < 9 x variance + * + * Statistically speaking, any values out of this interval is + * considered as an anomaly and is discarded. However, a normal + * distribution appears when the number of samples is 30 (it is the + * rule of thumb in statistics, cf. "30 samples" on Internet). When + * there are three consecutive anomalies, the statistics are resetted. + * + */ +static void irqs_update(struct irq_stat *irqs, u64 ts) +{ + u64 old_ts = irqs->lts; + u64 variance = 0; + u64 interval; + s64 diff; + + /* + * The timestamps are absolute time values, we need to compute + * the timing interval between two interrupts. + */ + irqs->lts = ts; + + /* + * The interval type is u64 in order to deal with the same + * type in our computation, that prevent mindfuck issues with + * overflow, sign and do_div. + */ + interval = ts - old_ts; + + /* + * The interrupt triggered more than one second apart, that + * ends the sequence as predictible for our purpose. In this + * case, assume we have the beginning of a sequence and the + * timestamp is the first value. As it is impossible to + * predict anything at this point, return. + * + * Note the first timestamp of the sequence will always fall + * in this test because the old_ts is zero. That is what we + * want as we need another timestamp to compute an interval. + */ + if (interval >= NSEC_PER_SEC) { + memset(irqs, 0, sizeof(*irqs)); + irqs->lts = ts; + return; + } + + /* + * Pre-compute the delta with the average as the result is + * used several times in this function. + */ + diff = interval - irqs->avg; + + /* + * Increment the number of samples. + */ + irqs->count++; + + /* + * Online variance divided by the number of elements if there + * is more than one sample. + */ + if (likely(irqs->count > 1)) + variance = div_u64(irqs->variance, irqs->count - 1); + + /* + * The rule of thumb in statistics for the normal distribution + * is having at least 30 samples in order to have the model to + * apply. Values outside the interval are considered as an + * anomaly. + */ + if ((irqs->count >= 30) && ((diff * diff) > (9 * variance))) { + /* + * After three consecutive anomalies, we reset the + * stats as it is no longer stable enough. + */ + if (irqs->anomalies++ >= 3) { + memset(irqs, 0, sizeof(*irqs)); + irqs->lts = ts; + return; + } + } else { + /* + * The anomalies must be consecutives, so at this + * point, we reset the anomalies counter. + */ + irqs->anomalies = 0; + } + + /* + * The interrupt is considered stable enough to try to predict + * the next event on it. + */ + irqs->valid = 1; + + /* + * Online average algorithm: + * + * new_average = average + ((value - average) / count) + * + * The variance computation depends on the new average + * to be computed here first. + * + */ + irqs->avg = irqs->avg + div_s64(diff, irqs->count); + + /* + * Online variance algorithm: + * + * new_variance = variance + (value - average) x (value - new_average) + * + * Warning: irqs->avg is updated with the line above, hence + * 'interval - irqs->avg' is no longer equal to 'diff' + */ + irqs->variance = irqs->variance + (diff * (interval - irqs->avg)); + + /* + * Update the next event + */ + irqs->ne = ts + irqs->avg; +} + +/** + * irq_timings_next_event - Return when the next event is supposed to arrive + * + * *** This function must be called with the local irq disabled *** + * + * During the last busy cycle, the number of interrupts is incremented + * and stored in the irq_timings structure. This information is + * necessary to: + * + * - know if the index in the table wrapped up: + * + * If more than the array size interrupts happened during the + * last busy/idle cycle, the index wrapped up and we have to + * begin with the next element in the array which is the last one + * in the sequence, otherwise it is a the index 0. + * + * - have an indication of the interrupts activity on this CPU + * (eg. irq/sec) + * + * The values are 'consumed' after inserting in the statistical model, + * thus the count is reinitialized. + * + * The array of values **must** be browsed in the time direction, the + * timestamp must increase between an element and the next one. + * + * Returns a nanosec time based estimation of the earliest interrupt, + * U64_MAX otherwise. + */ +u64 irq_timings_next_event(u64 now) +{ + struct irq_timings *irqts = this_cpu_ptr(&irq_timings); + struct irq_timing *irqt; + struct irq_stat *irqs; + struct irq_stat __percpu *s; + u64 ne = U64_MAX; + int index, count, i, irq = 0; + + /* + * Number of elements in the circular buffer. If it happens it + * was flushed before, then the number of elements could be + * smaller than IRQ_TIMINGS_SIZE, so the count is used, + * otherwise the array size is used as we wrapped. The index + * begins from zero when we did not wrap. That could be done + * in a nicer way with the proper circular array structure + * type but with the cost of extra computation in the + * interrupt handler hot path. We choose efficiency. + */ + if (irqts->count >= IRQ_TIMINGS_SIZE) { + count = IRQ_TIMINGS_SIZE; + index = irqts->count & IRQ_TIMINGS_MASK; + } else { + count = irqts->count; + index = 0; + } + + /* + * Inject measured irq/timestamp to the statistical model. + */ + for (i = 0; i < count; i++) { + + irqt = &irqts->values[(index + i) & IRQ_TIMINGS_MASK]; + + s = idr_find(&irq_stats, irqt->irq); + + irqs = this_cpu_ptr(s); + + irqs_update(irqs, irqt->ts); + } + + /* + * Reset the counter, we consumed all the data from our + * circular buffer. + */ + irqts->count = 0; + + /* + * Look in the list of interrupts' statistics, the earliest + * next event. + */ + idr_for_each_entry(&irq_stats, s, i) { + + irqs = this_cpu_ptr(s); + + if (!irqs->valid) + continue; + + if (irqs->ne <= now) { + irq = i; + ne = now; + + /* + * This interrupt mustn't use in the future + * until new events occur and update the + * statistics. + */ + irqs->valid = 0; + break; + } + + if (irqs->ne < ne) { + irq = i; + ne = irqs->ne; + } + } + + return ne; +} + +void irq_timings_free(int irq) +{ + struct irq_stat __percpu *s; + + s = idr_find(&irq_stats, irq); + if (s) { + free_percpu(s); + idr_remove(&irq_stats, irq); + } +} + +int irq_timings_alloc(int irq) +{ + int id; + struct irq_stat __percpu *s; + + /* + * Some platforms can have the same private interrupt per cpu, + * so this function may be be called several times with the + * same interrupt number. Just bail out in case the per cpu + * stat structure is already allocated. + */ + s = idr_find(&irq_stats, irq); + if (s) + return 0; + + s = alloc_percpu(*s); + if (!s) + return -ENOMEM; + + idr_preload(GFP_KERNEL); + id = idr_alloc(&irq_stats, s, irq, irq + 1, GFP_NOWAIT); + idr_preload_end(); + + if (id < 0) { + free_percpu(s); + return id; + } + + return 0; +}