All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linux <zhaoyan.liao@linux.alibaba.com>
Cc: mingo@redhat.com, hpa@zytor.com, dwmw@amazon.co.uk,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	songmuchun@bytedance.com, likunkun@bytedance.com,
	guancheng.rjk@alibaba-inc.com, duanxiongchun@bytedance.com,
	wenan.mao@linux.alibaba.com
Subject: Re: [PATCH] use 64bit timer for hpet
Date: Mon, 12 Jul 2021 09:25:38 +0200	[thread overview]
Message-ID: <875yxgngct.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <2CC6F5DA-B186-4A06-92B4-B763386F0D0A@linux.alibaba.com>

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-12  7:32 UTC|newest]

Thread overview: 9+ 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-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 [this message]
2021-07-13  1:43           ` Linux

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=875yxgngct.ffs@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=duanxiongchun@bytedance.com \
    --cc=dwmw@amazon.co.uk \
    --cc=guancheng.rjk@alibaba-inc.com \
    --cc=hpa@zytor.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=likunkun@bytedance.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=songmuchun@bytedance.com \
    --cc=wenan.mao@linux.alibaba.com \
    --cc=zhaoyan.liao@linux.alibaba.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 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.