From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755186Ab0CWQ2p (ORCPT <rfc822;w@1wt.eu>);
	Tue, 23 Mar 2010 12:28:45 -0400
Received: from mailout1.zih.tu-dresden.de ([141.30.67.72]:48175 "EHLO
	mailout1.zih.tu-dresden.de" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1754512Ab0CWQ2n convert rfc822-to-8bit
	(ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 23 Mar 2010 12:28:43 -0400
Subject: Re: [PATCH] trace power_frequency events on the correct cpu  (for
 Intel x86 CPUs)
From: Robert =?ISO-8859-1?Q?Sch=F6ne?= <robert.schoene@tu-dresden.de>
To: Thomas Renninger <trenn@suse.de>
Cc: Arjan van de Ven <arjan@linux.intel.com>, Dave Jones <davej@redhat.com>,
       Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
       linux-kernel <linux-kernel@vger.kernel.org>,
       cpufreq <cpufreq@vger.kernel.org>, x86@kernel.org
In-Reply-To: <4BA7773A.5080206@linux.intel.com>
References: <1268399863.3407.15.camel@localhost>
	 <201003182143.22929.trenn@suse.de> <1268985679.3395.47.camel@localhost>
	 <201003202237.57477.trenn@suse.de>  <4BA6BD0A.6030303@linux.intel.com>
	 <1269241492.3485.16.camel@localhost>  <4BA7773A.5080206@linux.intel.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 23 Mar 2010 17:28:36 +0100
Message-ID: <1269361716.3475.1.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.1 
Content-Transfer-Encoding: 8BIT
X-TUD-Virus-Scanned: mailout1.zih.tu-dresden.de
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Am Montag, den 22.03.2010, 06:57 -0700 schrieb Arjan van de Ven:
> On 3/22/2010 0:04, Robert Schöne wrote:
> > Am Sonntag, den 21.03.2010, 17:42 -0700 schrieb Arjan van de Ven:
> >> On 3/20/2010 14:37, Thomas Renninger wrote:
> >>
> >>> It also seem to be (hopefully) a minor feature for timechart, so this should
> >>> not hurt that much (yet).
> >>
> >> It's actually a major feature for timechart, and one of the key things I and a bunch of others
> >> inside Intel use timechart for.
> >>
> > It's a major feature for us too.
> > I suppose, the cpufreq_notify_transition calls are correct (meaning
> > being called for all related cpus) for every driver. So there's still
> > the option to include it in the POST_CHANGE section of this function.
> > Could this be okay for the both of you?
> 
> post change would work... that gets frequency afaik..
Are you ok with this too, Thomas?