Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760782AbZDCHRl (ORCPT ); Fri, 3 Apr 2009 03:17:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753411AbZDCHRc (ORCPT ); Fri, 3 Apr 2009 03:17:32 -0400 Received: from mga11.intel.com ([192.55.52.93]:9784 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751334AbZDCHRb convert rfc822-to-8bit (ORCPT ); Fri, 3 Apr 2009 03:17:31 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.39,318,1235980800"; d="scan'208";a="678421367" From: "Metzger, Markus T" To: Ingo Molnar CC: "tglx@linutronix.de" , "hpa@zytor.com" , "markus.t.metzger@gmail.com" , "roland@redhat.com" , "eranian@googlemail.com" , "oleg@redhat.com" , "Villacis, Juan" , "ak@linux.jf.intel.com" , "linux-kernel@vger.kernel.org" Date: Fri, 3 Apr 2009 08:17:22 +0100 Subject: RE: [patch 01/18] x86, bts: fix race when bts tracer is removed Thread-Topic: [patch 01/18] x86, bts: fix race when bts tracer is removed Thread-Index: AcmzwzWaOsx60ovwSfmp6ywNDZWSaQAYHckgAAHNybA= Message-ID: <928CFBE8E7CB0040959E56B4EA41A77E9271809B@irsmsx504.ger.corp.intel.com> References: <20090402145455.597376000@intel.com> <20090402145702.669790000@intel.com> <20090402184514.GC843@elte.hu> <928CFBE8E7CB0040959E56B4EA41A77E9271804B@irsmsx504.ger.corp.intel.com> In-Reply-To: <928CFBE8E7CB0040959E56B4EA41A77E9271804B@irsmsx504.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1325 Lines: 38 >-----Original Message----- >From: Metzger, Markus T >Sent: Friday, April 03, 2009 8:20 AM >To: Ingo Molnar >>Also, raw use of jiffies_64 is buggy and racy. Why does this use >>jiffies to begin with - why not some finer grained time? > >What would be a good time to use? I found cpu_clock() declared in sched.h, which is based on TSC and seems to be used by the scheduler, as well. Would this be a good time to use? thanks, markus. --------------------------------------------------------------------- Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen Germany Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer Registergericht: Muenchen HRB 47456 Ust.-IdNr. VAT Registration No.: DE129385895 Citibank Frankfurt (BLZ 502 109 00) 600119052 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- 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/