From: alex.shi@linaro.org (Alex Shi)
To: linux-arm-kernel@lists.infradead.org
Subject: a bug on NO_HZ_FULL_ALL
Date: Thu, 14 Nov 2013 21:08:29 +0800 [thread overview]
Message-ID: <5284CB4D.3050902@linaro.org> (raw)
In-Reply-To: <20131114120845.GA16735@n2100.arm.linux.org.uk>
On 11/14/2013 08:08 PM, Russell King - ARM Linux wrote:
> On Thu, Nov 14, 2013 at 12:53:15PM +0100, Frederic Weisbecker wrote:
>> BTW, support for ARM's full dynticks is uncomplete without
>> "[PATCH] ARM: Support arch_irq_work_raise() via self IPIs"
>>
>> ...which I'm not sure is applied upstream, or even any ARM tree yet.
>
> It's in mainline as of last night, along with a fix to the above patch.
>
I saw this in linus tree and in tip/master. According to content, it
seems no effort on this issue. The following testing base on latest code.
btw, the full_all do cause more interrupts.
#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
# CONFIG_NO_HZ_IDLE is not set
CONFIG_NO_HZ_FULL=y
# CONFIG_NO_HZ_FULL_ALL is not set
CONFIG_NO_HZ_FULL_SYSIDLE=y
CONFIG_NO_HZ_FULL_SYSIDLE_SMALL=2
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
alexs at alex-panda:~$ head -2 /proc/interrupts; sleep 10 ; head -2
/proc/interrupts
CPU0 CPU1
29: 12567 9783 GIC 29 twd
CPU0 CPU1
29: 12814 9942 GIC 29 twd
Then enabled CONFIG_NO_HZ_FULL_ALL. more than 200/second interrupt
increased.
alexs at alex-panda:~$ head -2 /proc/interrupts; sleep 10 ; head -2
/proc/interrupts
CPU0 CPU1
29: 34969 6384 GIC 29 twd
CPU0 CPU1
29: 37172 6646 GIC 29 twd
--
Thanks
Alex
next prev parent reply other threads:[~2013-11-14 13:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANHzE=2EOJmjFqLUDSfxTvgQhrUogOxH8Qux9hBFTGf8HiWWEw@mail.gmail.com>
2013-11-14 2:41 ` a bug on NO_HZ_FULL_ALL Alex Shi
2013-11-14 7:46 ` Alex Shi
2013-11-14 8:05 ` Vincent Guittot
2013-11-14 8:09 ` viresh kumar
2013-11-14 9:54 ` Shaojie Sun
2013-11-14 11:50 ` Frederic Weisbecker
[not found] ` <548C3FF8E9B1F945A9FEE3533A16C6CD4E9BF1DA@szxema507-mbs.china.huawei.com>
2013-11-14 12:59 ` 答复: " Frederic Weisbecker
2013-11-14 11:53 ` Frederic Weisbecker
2013-11-14 12:08 ` Russell King - ARM Linux
2013-11-14 12:37 ` Frederic Weisbecker
2013-11-14 13:08 ` Alex Shi [this message]
2013-11-14 13:15 ` Frederic Weisbecker
2013-11-19 3:03 ` Alex Shi
[not found] ` <548C3FF8E9B1F945A9FEE3533A16C6CD4E9C319D@szxema507-mbs.china.huawei.com>
2013-11-19 3:15 ` 答复: " Alex Shi
2013-11-14 11:42 ` Frederic Weisbecker
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=5284CB4D.3050902@linaro.org \
--to=alex.shi@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).