From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755442Ab1F3Iik (ORCPT ); Thu, 30 Jun 2011 04:38:40 -0400 Received: from mga14.intel.com ([143.182.124.37]:32109 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754110Ab1F3Ii2 (ORCPT ); Thu, 30 Jun 2011 04:38:28 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.65,449,1304319600"; d="scan'208";a="20779895" Subject: Re: power increase issue on light load From: "Alex,Shi" To: Nikhil Rao Cc: Peter Zijlstra , "mingo@elte.hu" , "Chen, Tim C" , "Li, Shaohua" , "linux-kernel@vger.kernel.org" , "Brown, Len" In-Reply-To: References: <1308797024.23204.95.camel@debian> <1308819748.1022.69.camel@twins> <1308876099.23204.124.camel@debian> <1309219329.14604.11.camel@debian> <1309273180.6701.213.camel@twins> <1309317764.14604.92.camel@debian> <1309330546.14604.97.camel@debian> Content-Type: text/plain; charset="UTF-8" Date: Thu, 30 Jun 2011 16:38:19 +0800 Message-ID: <1309423099.14604.480.camel@debian> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2011-06-30 at 08:26 +0800, Nikhil Rao wrote: > On Tue, Jun 28, 2011 at 11:55 PM, Alex,Shi wrote: > >> > - Would it be possible to get a "perf sched" trace on these two kernels? > > > > I tried the 'perf sched record' and then 'perf sched trace' as usage > > show. but in fact, the 'perf sched' doesn't support 'trace' command now. > > I believe this was renamed to "perf script" in > 133dc4c39c57eeef2577ca5b4ed24765b7a78ce2. > > > since the 'perf sched record' is using 'perf record -e sched:xxx' to do > > record. I used 'perf record' directly. The follow info collected in 300' > > on my NHM-EP for benchmark bltk-office. > > > > [alexs@lkp-ne01 ~]$ grep -e Events.*sched > > linux-2.6/perf-report-3.0.0-rc5 > > # Events: 11K sched:sched_wakeup > > # Events: 1K sched:sched_wakeup_new > > # Events: 24K sched:sched_switch > > # Events: 3K sched:sched_migrate_task > > # Events: 851 sched:sched_process_free > > # Events: 1K sched:sched_process_exit > > # Events: 1K sched:sched_process_wait > > # Events: 1K sched:sched_process_fork > > # Events: 12K sched:sched_stat_wait > > # Events: 9K sched:sched_stat_sleep > > # Events: 452 sched:sched_stat_iowait > > # Events: 16K sched:sched_stat_runtime > > [alexs@lkp-ne01 ~]$ > > [alexs@lkp-ne01 ~]$ > > [alexs@lkp-ne01 ~]$ grep -e > > Events.*sched /mnt/linux-2.6.39/perf-report-2.6.39 > > # Events: 5K sched:sched_wakeup > > # Events: 615 sched:sched_wakeup_new > > # Events: 11K sched:sched_switch > > # Events: 2K sched:sched_migrate_task > > # Events: 541 sched:sched_process_free > > # Events: 692 sched:sched_process_exit > > # Events: 1K sched:sched_process_wait > > # Events: 615 sched:sched_process_fork > > # Events: 6K sched:sched_stat_wait > > # Events: 4K sched:sched_stat_sleep > > # Events: 178 sched:sched_stat_iowait > > # Events: 9K sched:sched_stat_runtime > > > > > > Thanks for the data but these raw counts are not very useful. Can you > please send either the binary file or the ascii trace output for the > two kernels? Also -- a 300s trace might be too much; about 30s should > be sufficient. The trace output file is much big, and guess no others has interesting on it. I will give separately. :) > > -Thanks, > Nikhil