Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752122AbaBSD2L (ORCPT ); Tue, 18 Feb 2014 22:28:11 -0500 Received: from e33.co.us.ibm.com ([32.97.110.151]:42296 "EHLO e33.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751833AbaBSD1m (ORCPT ); Tue, 18 Feb 2014 22:27:42 -0500 Message-ID: <530423CB.5060105@linux.vnet.ibm.com> Date: Wed, 19 Feb 2014 08:53:55 +0530 From: Preeti U Murthy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: Thomas Gleixner CC: Preeti Murthy , Linus Torvalds , LKML , Andrew Morton , Ingo Molnar , "H. Peter Anvin" Subject: Re: [GIT Pull] timer fixes for 3.14 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14021903-0928-0000-0000-00000692A5AB Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/19/2014 12:10 AM, Thomas Gleixner wrote: > On Tue, 18 Feb 2014, Preeti Murthy wrote: > >> Hi Thomas, >> >> With regard to the patch: "tick: Clear broadcast pending bit when >> switching to oneshot" >> isn't BROADCAST_EXIT called atleast after initializing the high >> resolution timers while >> handling the broadcast IPI and before re-entering idle? This should >> clear the cpu bit >> in the pending mask right? >> >> idle() >> |__BROADCAST_ENTER >> |__halt() >> |__broadcast_ipi >> |__init_highres()->clear oneshot mask >> |__return from interrupt->BROADCAST_EXIT (clear pending mask) > > Unfortunately not: > > if (cpumask_test_and_clear_cpu(cpu, tick_broadcast_oneshot_mask)) { > clear pending mask; > } > >> |__re-enter idle > > Go figure :) Ah right! Thanks :) Regards Preeti U Murthy > > Thanks, > > tglx > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/