public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: [GIT PULL V11] irq: next irq tracking
Date: Tue, 20 Jun 2017 23:26:57 +0200	[thread overview]
Message-ID: <20170620212657.GB1812@mai> (raw)

Hi Thomas,

this pull request contains the next irq prediction as posted for V11
[1] which takes into account all the commments. It is based on top of
irq/core.

As previously discussed the code is not enabled by default, hence compiled out.

The first patch adds the IRQF_TIMER flag to the timers which are percpu in
order to discard any timing measurement when the interrupt is coming from a
timer. All the timers changes have been discarded from V10.

The second patch adds a circular buffer and the small routine to store the
local time when an interrupt occurs. The t-uple <irq,timestamp> are encoded
together into a single 64bits as suggested by Nicolas Pitre.

The third patch provides the mathematic to compute the regular intervals. The
rational is in changelog and the math is commented in details in the code.

Thanks.

  -- Daniel


The following changes since commit b50fb7c99217922ea36d6e38bae34d84c0587cad:

  Merge branch 'linus' into irq/core (2017-06-20 22:08:32 +0200)

are available in the git repository at:

  http://git.linaro.org/people/daniel.lezcano/linux.git next-irq/4.13-v11

for you to fetch changes up to eacb5f29a1ec71ee3e43e2729b8a1b5ec51320d5:

  irq: Compute the periodic interval for interrupts (2017-06-20 23:14:18 +0200)

----------------------------------------------------------------
Daniel Lezcano (3):
      irq: Allow to pass the IRQF_TIMER flag with percpu irq request
      irq: Track the interrupt timings
      irq: Compute the periodic interval for interrupts

 include/linux/interrupt.h |  17 +++++++-
 kernel/irq/Kconfig        |   3 ++
 kernel/irq/Makefile       |   1 +
 kernel/irq/handle.c       |   2 +
 kernel/irq/internals.h    | 103 +++++++++++++++++++++++++++++++++++++++++++++
 kernel/irq/manage.c       |  18 +++++---
 kernel/irq/timings.c      | 366 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 7 files changed, 504 insertions(+), 6 deletions(-)
 create mode 100644 kernel/irq/timings.c


-- 

 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

             reply	other threads:[~2017-06-20 21:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 21:26 Daniel Lezcano [this message]
2017-06-20 21:28 ` [PATCH 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request Daniel Lezcano
2017-06-20 21:28   ` [PATCH 2/3] irq: Track the interrupt timings Daniel Lezcano
2017-06-22 14:47     ` Thomas Gleixner
2017-06-22 14:55       ` Daniel Lezcano
2017-06-20 21:28   ` [PATCH 3/3] irq: Compute the periodic interval for interrupts Daniel Lezcano
2017-06-22 15:25     ` Thomas Gleixner
2017-06-22 16:35       ` Daniel Lezcano
2017-06-22  9:31   ` [PATCH 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request Mark Rutland
2017-06-22 10:36     ` Daniel Lezcano
2017-06-20 22:04 ` [GIT PULL V11] irq: next irq tracking Thomas Gleixner
2017-06-21 10:57   ` Daniel Lezcano
2017-07-06 12:29   ` [PATCH V11] irq: Allow to pass the IRQF_TIMER flag with percpu irq request Daniel Lezcano
2017-07-06 21:21     ` [tip:irq/urgent] genirq: " tip-bot for Daniel Lezcano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170620212657.GB1812@mai \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox