From: alex.shi@linaro.org (Alex Shi)
To: linux-arm-kernel@lists.infradead.org
Subject: 答复: a bug on NO_HZ_FULL_ALL
Date: Tue, 19 Nov 2013 11:15:12 +0800 [thread overview]
Message-ID: <528AD7C0.40702@linaro.org> (raw)
In-Reply-To: <548C3FF8E9B1F945A9FEE3533A16C6CD4E9C319D@szxema507-mbs.china.huawei.com>
On 11/19/2013 11:10 AM, Sunshaojie wrote:
> Hi Alex
>
> I tested it on kernel V3.10 and on 32bits ARM system.
> Where did you see this option opened only for 64bits?
>
kernel/time/Kconfig:
config NO_HZ_FULL
bool "Full dynticks system (tickless)"
# NO_HZ_COMMON dependency
depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
# We need at least one periodic CPU for timekeeping
depends on SMP
# RCU_USER_QS dependency
depends on HAVE_CONTEXT_TRACKING
# VIRT_CPU_ACCOUNTING_GEN dependency
depends on 64BIT <=======
select NO_HZ_COMMON
select RCU_USER_QS
select RCU_NOCB_CPU
select VIRT_CPU_ACCOUNTING_GEN
select IRQ_WORK
>
> -----????-----
> ???: Alex Shi [mailto:alex.shi at linaro.org]
> ????: 2013?11?19? 11:03
> ???: Shaojie Sun; viresh kumar
> ??: Vincent Guittot; Fathi Boudra; Guodong Xu; Amit Kucheria; Chris Redpath; Linaro Kernel; LAK; Fr?d?ric Weisbecker; Kevin Hilman; Sunshaojie
> ??: Re: a bug on NO_HZ_FULL_ALL
>
> On 11/14/2013 05:54 PM, Shaojie Sun wrote:
>> No, I think it is a bug.
>>
>> Because I tested the option with NO_HZ_FULL and without
>> NO_HZ_FULL_ALL. It had only little interruptes on CPU0 twd.
>> With same code, I added NO_HZ_FULL_ALL option. It had too many
>> interruptes on CPU0 twd.
>>
>> So the sumbitter just didn't test twd interrupts, when he expanded
>> NO_HZ_FULL option to all cpu.
>>
>> On Thu, Nov 14, 2013 at 4:09 PM, viresh kumar <viresh.kumar@linaro.org> wrote:
>>> On Thursday 14 November 2013 01:35 PM, Vincent Guittot wrote:
>>>> AFAICT, It's a none issue. In full nohz, a timer fires periodically
>>>> (around 4sec period on ARM IIRC) on one cpu (cpu0).
>>>
>>> Timer should always be running on CPU0, its out of nohz-full domain.
>>> Its cpu 1, where it will fire after long delays..
>>>
>>>
>>> https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/AdaptiveTic
>>> kless
>
>
> Shaojie,
> which kernel version has this bug?
> I just find only the v3.13 kernel has opened the NO_HZ_FULL for 32 bit kernel. and my testing base it.
>
> but for lsk, it is 3.10 kernel, so unless you are using 64bit kernel to do testing, is it right?
>
> --
> Thanks
> Alex
>
--
Thanks
Alex
next prev parent reply other threads:[~2013-11-19 3:15 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
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 [this message]
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=528AD7C0.40702@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 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.