All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:41:25 +0800	[thread overview]
Message-ID: <52843855.5060509@linaro.org> (raw)
In-Reply-To: <CANHzE=2EOJmjFqLUDSfxTvgQhrUogOxH8Qux9hBFTGf8HiWWEw@mail.gmail.com>

CC to kernel mailing list.

What's you expected result for twd?


On 11/14/2013 08:36 AM, Shaojie Sun wrote:
> Hi all
>      When I enble NO_HZ_FULL and NO_HZ_FULL_ALL option in K3V2 board.
> I find that the twd interrupt will be trigged in a large time pre
> second.
>      In our landing team branch, we used lsk branch.
> 
>      Do you find this bugs on your board? And how to resolve it?
> 
> 
>>> cat /proc/interrupts
> 
>              CPU0     CPU1
>  29:        293        395       GIC  twd
> 


-- 
Thanks
    Alex

       reply	other threads:[~2013-11-14  2:41 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 ` Alex Shi [this message]
2013-11-14  7:46   ` a bug on NO_HZ_FULL_ALL 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
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=52843855.5060509@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.