From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Haris Okanovic <haris.okanovic@ni.com>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, julia.cartwright@ni.com,
gratian.crisan@ni.com, anna-maria@linutronix.de
Subject: Re: [PATCH v3 2/2] timers: Don't search for expired timers while TIMER_SOFTIRQ is scheduled
Date: Thu, 1 Mar 2018 20:06:39 +0100 [thread overview]
Message-ID: <20180301190639.fttlaq272p67qzm4@linutronix.de> (raw)
In-Reply-To: <7079102c-f53b-e8ab-c54d-1c40ff21d921@ni.com>
On 2018-03-01 12:37:49 [-0600], Haris Okanovic wrote:
> On 03/01/2018 10:47 AM, Sebastian Andrzej Siewior wrote:
> > On 2018-03-01 09:49:59 [-0600], Haris Okanovic wrote:
> > > *bump* Has anyone looked into this?
> >
> > I'm lost.
> > It entered the kernel in v4.9.9-rt6 and left in v4.9.30-rt20 once we
> > figured out that there is something wrong with it.
>
> It was added back into 4.9 at some point after v4.9.30-rt20. I see an older
> version in v4.9.68-rt60, for example, hence my original email. It was
let me check that tomorrow.
> dropped sometime thereafter, presumably because it no longer cleanly
> applies. I don't see it in v4.14.20-rt17, for example.
>
> > Is there a newer patch pending on your side?
>
> Not yet. The latest version on patchwork is OK, just needs to be rebased
> post-4.9. I'll post a new version when I get a chance to build and retest
> it.
okay.
Sebastian
next prev parent reply other threads:[~2018-03-01 19:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 21:44 [RFC v2] timers: Don't wake ktimersoftd on every tick Haris Okanovic
2016-12-23 17:28 ` Sebastian Andrzej Siewior
2016-12-28 18:06 ` Haris Okanovic
2017-02-03 16:51 ` Sebastian Andrzej Siewior
2017-02-03 18:21 ` [PATCH] " Haris Okanovic
2017-02-10 17:02 ` Sebastian Andrzej Siewior
2017-05-26 17:16 ` [PATCH] Revert "timers: Don't wake ktimersoftd on every tick" Anna-Maria Gleixner
2017-05-26 19:27 ` Haris Okanovic
2017-05-26 19:49 ` Thomas Gleixner
2017-05-26 20:25 ` Haris Okanovic
2017-05-26 20:50 ` Thomas Gleixner
2017-06-02 14:37 ` Haris Okanovic
2017-06-04 14:17 ` Thomas Gleixner
2017-07-17 21:58 ` Haris Okanovic
2017-07-17 22:04 ` [PATCH v2] timers: Don't wake ktimersoftd on every tick Haris Okanovic
2017-07-18 21:33 ` Thomas Gleixner
2017-08-03 21:04 ` Haris Okanovic
2017-08-03 21:06 ` [PATCH v3 1/2] " Haris Okanovic
2017-08-03 21:06 ` [PATCH v3 2/2] timers: Don't search for expired timers while TIMER_SOFTIRQ is scheduled Haris Okanovic
2018-01-05 19:37 ` Haris Okanovic
2018-03-01 15:49 ` Haris Okanovic
2018-03-01 15:54 ` Thomas Gleixner
2018-03-01 16:35 ` Haris Okanovic
2018-03-01 16:47 ` Sebastian Andrzej Siewior
2018-03-01 18:37 ` Haris Okanovic
2018-03-01 19:06 ` Sebastian Andrzej Siewior [this message]
2018-03-02 14:52 ` Sebastian Andrzej Siewior
2018-03-02 16:29 ` Haris Okanovic
2018-03-02 16:39 ` Sebastian Andrzej Siewior
2018-03-02 17:19 ` Haris Okanovic
2018-03-06 23:39 ` [PATCH v4 1/2] timers: Don't wake ktimersoftd on every tick Haris Okanovic
2018-03-06 23:39 ` [PATCH v4 2/2] timers: Don't search for expired timers while TIMER_SOFTIRQ is scheduled Haris Okanovic
[not found] ` <1523332961.4827.1.camel@gmx.de>
2018-04-12 15:00 ` [PATCH v4 1/2] timers: Don't wake ktimersoftd on every tick Haris Okanovic
2018-06-19 12:43 ` Daniel Bristot de Oliveira
2018-06-20 14:24 ` Haris Okanovic
2018-06-28 16:36 ` Haris Okanovic
2018-06-28 16:40 ` [PATCH v5 " Haris Okanovic
2018-06-28 16:40 ` [PATCH v5 2/2] timers: Don't search for expired timers while TIMER_SOFTIRQ is scheduled Haris Okanovic
2018-07-13 12:01 ` [PATCH v5 1/2] timers: Don't wake ktimersoftd on every tick Anna-Maria Gleixner
2018-07-13 14:37 ` Haris Okanovic
2017-05-27 7:47 ` [PATCH] Revert "timers: Don't wake ktimersoftd on every tick" Sebastian Andrzej Siewior
2017-02-03 18:27 ` [RFC v2] timers: Don't wake ktimersoftd on every tick Haris Okanovic
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=20180301190639.fttlaq272p67qzm4@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=gratian.crisan@ni.com \
--cc=haris.okanovic@ni.com \
--cc=julia.cartwright@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).