From: Thomas Gleixner <tglx@linutronix.de>
To: Rei Yamamoto <yamamoto.rei@jp.fujitsu.com>
Cc: geert+renesas@glider.be, linux-kernel@vger.kernel.org,
yamamoto.rei@jp.fujitsu.com
Subject: Re: [PATCH] hrtimer: Remove a warning message in hrtimer_interrupt()
Date: Fri, 25 Mar 2022 20:48:18 +0100 [thread overview]
Message-ID: <87h77lhkzh.ffs@tglx> (raw)
In-Reply-To: <20220224092848.3755-1-yamamoto.rei@jp.fujitsu.com>
On Thu, Feb 24 2022 at 18:28, Rei Yamamoto wrote:
> It seems the warning message in hrtimer_interrupt() has
> no an intention.
> The required action for the warning message in hrtimer_interrupt()
> is not clear.
The required action is to figure out why the hrtimer interrupt is
looping for a long time.
> Remove this message not to confuse user.
No. This message is interesting because as a consequence of an overly
long hrtimer interrupt the hrtimer interrupt will be deferred so tasks
can make progress. That means for the time of deferral there will be no
hrtimers fire, which is confusing if the message is removed because you
cannot figure out the reason.
Thanks,
tglx
next prev parent reply other threads:[~2022-03-25 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 2:39 [RFC] hrtimer: About the warning message in hrtimer_interrupt() Rei Yamamoto
2022-02-24 9:28 ` [PATCH] hrtimer: Remove a " Rei Yamamoto
2022-03-25 19:48 ` Thomas Gleixner [this message]
2022-06-24 7:00 ` [PATCH] hrtimer: CPU and entry_time is added to " Rei Yamamoto
2022-06-24 7:09 ` Rei Yamamoto
2022-09-09 5:22 ` Rei Yamamoto
2022-11-07 0:20 ` Rei Yamamoto
2022-12-01 21:30 ` Thomas Gleixner
2022-12-02 9:55 ` Rei Yamamoto
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=87h77lhkzh.ffs@tglx \
--to=tglx@linutronix.de \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=yamamoto.rei@jp.fujitsu.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