From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: <fweisbec@gmail.com>
Cc: Xie XiuQi <xiexiuqi@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Question]: questions about 'Use sysidle detection to let the timekeeper sleep'
Date: Wed, 3 Nov 2021 15:51:21 +0800 [thread overview]
Message-ID: <197f0d3a-dd7c-b90f-4a9d-8a21e289fd6b@huawei.com> (raw)
In-Reply-To: <93236de5-f76e-3915-bbdf-9d060435937a@huawei.com>
Sorry, I forgot to Cc the maillist again. Cc it in this mail.
On 2021/11/3 10:59, Xiongfeng Wang wrote:
> Hi Frederic,
>
> Sorry to disturb you. It's just that I came across the same problem as you
> mentioned in the below link.
> https://lwn.net/Articles/577424/
>
> This is the problem in my situation. All the CPUs on my machine are in the same
> power domain. When nohz_full is enabled, if one of the CPUs keep receiving tick
> interrupts, all the CPUs can not be put into powerdown state, even thought all
> other CPUs are idle.
>
> I found your first version patchset in the below link.
> https://lore.kernel.org/lkml/1387320692-28460-1-git-send-email-fweisbec@gmail.com/
> But I couldn't found other verions. Even 'full-system-idle' is reverted in the
> mailline in the following commit.
> commit fe5ac724d81a3c7803e60c2232718f212f3f38d4
> rcu: Remove nohz_full full-system-idle state machine
>
> I am not sure if we have any other alternative solutions, or do we have rebased
> the patchset to mainline kernel. The first version patchset I found is based on
> v3.13.
>
> Thanks,
> Xiongfeng
>
parent reply other threads:[~2021-11-03 7:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <93236de5-f76e-3915-bbdf-9d060435937a@huawei.com>]
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=197f0d3a-dd7c-b90f-4a9d-8a21e289fd6b@huawei.com \
--to=wangxiongfeng2@huawei.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiexiuqi@huawei.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
all inboxes | Powered by JetHome®