From: Jet Chen <jet.chen@intel.com>
To: lkp@lists.01.org
Subject: Re: [clockevents] WARNING: CPU: 1 PID: 0 at kernel/time/clockevents.c:281 clockevents_program_event()
Date: Mon, 30 Jun 2014 15:06:28 +0800 [thread overview]
Message-ID: <53B10C74.4060409@intel.com> (raw)
In-Reply-To: <CAKohpomfxodayivDUriZKKgvQ7NnWGAYXc=2tAjMe9x2F8JfkA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
On 06/30/2014 12:40 PM, Viresh Kumar wrote:
> On 29 June 2014 20:28, Fengguang Wu <fengguang.wu@intel.com> wrote:
>> Greetings,
>>
>> 0day kernel testing robot got the below dmesg and the first bad commit is
>>
>> git://bee.sh.intel.com/git/tchen37/linux.git test
>> commit 2f89103f5b85386245b434e8e9f66d25df929e65
>> Author: Viresh Kumar <viresh.kumar@linaro.org>
>> AuthorDate: Tue Jun 10 13:52:25 2014 +0530
>> Commit: Viresh Kumar <viresh.kumar@linaro.org>
>> CommitDate: Tue Jun 24 10:54:12 2014 +0530
>>
>> clockevents: x86: add support for ONESHOT_STOPPED mode
>>
>> Clockevent devices can be stopped from core (hrtimers/tick) when they aren't
>> used anymore. This will mostly happen on a idle or tickless cpu. This is done to
>> avoid getting spurious interrupts when core doesn't want to handle them anymore.
>>
>> For stopping clockevent devices, core requests drivers to switch to a special
>> optional mode: CLOCK_EVT_MODE_ONESHOT_STOPPED. At this time platforms can also
>> save some power by disabling these devices.
>>
>> This patch adds support for handling CLOCK_EVT_MODE_ONESHOT_STOPPED mode for x86
>> drivers.
>>
>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Hmm, I have made some changes and pushed stuff again, please see if it
> still breaks:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git
> tick/oneshot-stopped
Changes fixes the issue.
Tested-by: Jet Chen <jet.chen@intel.com>
>
> Thanks.
>
prev parent reply other threads:[~2014-06-30 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 14:58 [clockevents] WARNING: CPU: 1 PID: 0 at kernel/time/clockevents.c:281 clockevents_program_event() Fengguang Wu
2014-06-30 4:40 ` Viresh Kumar
2014-06-30 7:06 ` Jet Chen [this message]
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=53B10C74.4060409@intel.com \
--to=jet.chen@intel.com \
--cc=lkp@lists.01.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.