All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Joachim <svenjoac@gmx.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, rjw@sisk.pl,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/urgent] tick: Fix oneshot broadcast setup really
Date: Thu, 19 Apr 2012 12:37:29 +0200	[thread overview]
Message-ID: <87lils3t3q.fsf@turtle.gmx.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1204191028510.2542@ionos> (Thomas Gleixner's message of "Thu, 19 Apr 2012 10:29:46 +0200 (CEST)")

Am 19.04.2012 um 10:29 schrieb Thomas Gleixner:

> On Wed, 18 Apr 2012, Suresh Siddha wrote:
>> On Wed, 2012-04-18 at 17:31 +0200, Thomas Gleixner wrote:
>> From: Suresh Siddha <suresh.b.siddha@intel.com>
>> Subject: tick: Fix the spurious broadcast timer ticks
>> 
>> During resume, tick_resume_broadcast() programs the broadcast timer
>> in oneshot mode unconditionally. On the platforms where broadcast timer
>> is not really required, this will generate spurious broadcast timer ticks
>> upon resume. For example, on the always running apic timer platforms with
>> HPET, I see spurious hpet tick once every ~5minutes (which is the 32-bit
>> hpet counter wraparound time).
>> 
>> Similar to boot time, during resume make the oneshot mode setting of
>> the broadcast clock event device conditional on the state of active broadcast
>> users. 
>> 
>> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
>
> Sven, Santosh, can you confirm that this works for you on top of the
> other two patches?

Works for me, thanks.

>> ---
>>  kernel/time/tick-broadcast.c |    3 ++-
>>  1 files changed, 2 insertions(+), 1 deletions(-)
>> 
>> diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
>> index bf57abd..766cd82 100644
>> --- a/kernel/time/tick-broadcast.c
>> +++ b/kernel/time/tick-broadcast.c
>> @@ -346,7 +346,8 @@ int tick_resume_broadcast(void)
>>  						     tick_get_broadcast_mask());
>>  			break;
>>  		case TICKDEV_MODE_ONESHOT:
>> -			broadcast = tick_resume_broadcast_oneshot(bc);
>> +			if (!cpumask_empty(tick_get_broadcast_mask()))
>> +				broadcast = tick_resume_broadcast_oneshot(bc);
>>  			break;
>>  		}
>>  	}


  parent reply	other threads:[~2012-04-19 10:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  1:49 Linux 3.4-rc3 Linus Torvalds
2012-04-17 15:24 ` kernel panic after suspend/resume (was: Linux 3.4-rc3) Sven Joachim
2012-04-17 16:00   ` Linus Torvalds
2012-04-17 18:12     ` kernel panic after suspend/resume Sven Joachim
2012-04-17 19:50       ` Linus Torvalds
2012-04-17 22:13         ` Thomas Gleixner
2012-04-18  5:27           ` Sven Joachim
2012-04-17 21:21     ` kernel panic after suspend/resume (was: Linux 3.4-rc3) Rafael J. Wysocki
2012-04-18  8:22       ` kernel panic after suspend/resume Sven Joachim
2012-04-18  9:36         ` Rafael J. Wysocki
2012-04-18 10:08         ` Thomas Gleixner
2012-04-18 11:03           ` Sven Joachim
2012-04-18 12:07           ` [tip:timers/urgent] tick: Fix oneshot broadcast setup really tip-bot for Thomas Gleixner
2012-04-18 13:19             ` Shilimkar, Santosh
2012-04-18 14:18               ` Santosh Shilimkar
2012-04-18 15:31                 ` Thomas Gleixner
2012-04-18 15:51                   ` Santosh Shilimkar
2012-04-19  2:27                   ` Suresh Siddha
2012-04-19  8:29                     ` Thomas Gleixner
2012-04-19 10:14                       ` Santosh Shilimkar
2012-04-19 10:37                       ` Sven Joachim [this message]
2012-04-19 19:38                     ` [tip:timers/urgent] tick: Fix the spurious broadcast timer ticks after resume tip-bot for Suresh Siddha
2012-04-19 19:37                   ` [tip:timers/urgent] tick: Ensure that the broadcast device is initialized tip-bot for Thomas Gleixner

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=87lils3t3q.fsf@turtle.gmx.de \
    --to=svenjoac@gmx.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rjw@sisk.pl \
    --cc=santosh.shilimkar@ti.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.