linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Saenz Julienne <nsaenzju@redhat.com>
To: He Zhe <zhe.he@windriver.com>, Frederic Weisbecker <frederic@kernel.org>
Cc: anna-maria@linutronix.de, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, Nicolas Saenz Julienne <nsaenzju@redhat.com>
Subject: Re: [PATCH v2] timers: Recalculate next timer interrupt only when necessary
Date: Fri, 09 Jul 2021 16:06:05 +0200	[thread overview]
Message-ID: <f520c8b87f56fcda0158853c5127f0488918503e.camel@redhat.com> (raw)
In-Reply-To: <11e85cd8-40ac-09fe-e1fe-0eafa351072c@windriver.com>

Hi Frederic, Zhe,

I've stumbled upon an issue on my x86_64 nohz_full setups which looks a lot
like Zhe's.

I've got a potential fix, I'll post it as a reply to this mail.

Regards,
Nicolas


  reply	other threads:[~2021-07-09 14:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 15:16 [PATCH v2] timers: Recalculate next timer interrupt only when necessary Frederic Weisbecker
2020-07-24 10:59 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2021-07-08  6:43 ` [PATCH v2] " He Zhe
2021-07-08 11:35   ` Frederic Weisbecker
2021-07-08 15:36   ` Frederic Weisbecker
2021-07-09  5:37     ` He Zhe
2021-07-09  8:43       ` Frederic Weisbecker
2021-07-09  9:25         ` He Zhe
2021-07-09 14:06           ` Nicolas Saenz Julienne [this message]
2021-07-09 14:13             ` [PATCH] timers: Fix get_next_timer_interrupt() with no timers pending Nicolas Saenz Julienne
2021-07-10  0:52               ` Frederic Weisbecker
2021-07-12 10:19                 ` Nicolas Saenz Julienne
2021-07-16 16:38                 ` Nicolas Saenz Julienne
2021-07-19 13:54                   ` Frederic Weisbecker
2021-07-10  9:05               ` Frederic Weisbecker
2021-07-12  6:04                 ` He Zhe

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=f520c8b87f56fcda0158853c5127f0488918503e.camel@redhat.com \
    --to=nsaenzju@redhat.com \
    --cc=anna-maria@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=zhe.he@windriver.com \
    /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).