archive mirror
 help / color / mirror / Atom feed
From: Linux <>
To: Thomas Gleixner <>
Subject: Re: [PATCH] use 64bit timer for hpet
Date: Tue, 13 Jul 2021 09:43:09 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

OK, Thank you for your patience. the last question:
> I forgot the details, but when I tried moving HPET to 64bit it did not
> work on one of my machines due to an erratum and other people reported
> similar issues on different CPUs/chipsets.
> TBH, I'm not interested at all to chase down these buggy implementations
> and have yet another pile of quirks.

Can you tell me the erranum or issue link at that time? This is very important
 to us.

Thank you very much.

> 2021年7月12日 下午3:25,Thomas Gleixner <> 写道:
> Liao,
> On Mon, Jul 12 2021 at 12:52, Linux wrote:
>>> Sorry, keeping the softirq from running for 3 minutes is simply out of
>>> spec. If the sysadmin decides to do so, then he can keep the pieces.
>> It is because the kernel thread is busy that the clocksource_watchdog 
>> thread is not scheduled, not softirq.
> Which thread?
> The clocksource watchdog runs from a timer_list timer callback in
> softirq context. Even if the softirq is switched to the softirq thread
> then still my argument of starving that for 3 minutes still stands.
> This is _not_ a kernel problem. Overcommitment is a admin problem.
> Thanks,
>        tglx

      reply	other threads:[~2021-07-13  1:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  8:13 [PATCH] use 64bit timer for hpet zhaoyan.liao
2021-07-02 15:57 ` kernel test robot
2021-07-07 10:04 ` Thomas Gleixner
2021-07-08  3:11   ` Linux
2021-07-08 11:17     ` Thomas Gleixner
2021-07-12  4:52       ` Linux
2021-07-12  7:25         ` Thomas Gleixner
2021-07-13  1:43           ` Linux [this message]

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:

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

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).