From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: [GIT PULL] IRQ changes for v5.2
Date: Mon, 6 May 2019 10:36:23 +0200 [thread overview]
Message-ID: <20190506083623.GA127408@gmail.com> (raw)
Linus,
Please pull the latest irq-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-core-for-linus
# HEAD: 471ba0e686cb13752bc1ff3216c54b69a2d250ea irq_work: Do not raise an IPI when queueing work on the local CPU
The changes in this cycle were:
- Remove the irq timings/variance statistics code that tried to predict
when the next interrupt would occur, which didn't work out as hoped
and will is replaced by another mechanism.
- This new mechanism is the 'array suffix computation' estimate, which
is superior to the previous one as it can detect not just a single
periodic pattern, but independent periodic patterns along a log-2
scale of bucketing and exponential moving average. The comments are
longer than the code - and it works better at predicting various
complex interrupt patterns from real-world devices than the previous
estimate.
- avoid IRQ-work self-IPIs on the local CPU
- fix work-list corruption in irq_set_affinity_notifier()
Thanks,
Ingo
------------------>
Daniel Lezcano (2):
genirq/timings: Remove variance computation code
genirq/timings: Add array suffix computation code
Gustavo A. R. Silva (1):
genirq/devres: Use struct_size() in devm_kzalloc()
Nicholas Piggin (1):
irq_work: Do not raise an IPI when queueing work on the local CPU
Prasad Sodagudi (1):
genirq: Prevent use-after-free and work list corruption
kernel/irq/devres.c | 3 +-
kernel/irq/manage.c | 4 +-
kernel/irq/timings.c | 522 +++++++++++++++++++++++++++++++++++----------------
kernel/irq_work.c | 75 ++++----
4 files changed, 409 insertions(+), 195 deletions(-)
next reply other threads:[~2019-05-06 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 8:36 Ingo Molnar [this message]
2019-05-06 23:40 ` [GIT PULL] IRQ changes for v5.2 pr-tracker-bot
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=20190506083623.GA127408@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.