mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: David Ahern <dsahern@gmail.com>
Cc: mingo@redhat.com, hpa@zytor.com, paulus@samba.org,
	linux-kernel@vger.kernel.org, acme@redhat.com,
	fweisbec@gmail.com, peterz@infradead.org, tglx@linutronix.de,
	linux-tip-commits@vger.kernel.org,
	Stephane Eranian <eranian@google.com>
Subject: Re: [tip:perf/core] perf tools: Allow multiple threads or processes in record, stat, top
Date: Sat, 3 Mar 2012 08:42:02 +0100	[thread overview]
Message-ID: <20120303074202.GB16816@elte.hu> (raw)
In-Reply-To: <4F50DEA0.2020607@gmail.com>


* David Ahern <dsahern@gmail.com> wrote:

> That first cup of coffee is so important.
> 
> On 3/2/12 3:56 AM, Ingo Molnar wrote:
> >phoenix:~>  perf record -a sleep 1
> >[ perf record: Woken up 1 times to write data ]
> >[ perf record: Captured and wrote 0.023 MB perf.data (~988 samples) ]
> >phoenix:~>  perf report --stdio
> >Warning:
> >The perf.data file has no samples!
> ># ========
> ># captured on: Fri Mar  2 12:01:41 2012
> ># hostname : phoenix
> ># os release : 3.3.0-rc5+
> ># perf version : 3.3.rc5.1698.g68a63a.dirty
> ># arch : x86_64
> ># nrcpus online : 16
> ># nrcpus avail : 16
> ># cpudesc : Quad-Core AMD Opteron(tm) Processor 8356
> ># cpuid : AuthenticAMD,16,2,3
> 
> Would you mind adding this patch:
>   https://lkml.org/lkml/2012/2/29/217
> and see if it fixes your problem?

That one appears to have done the trick - I committed it 
yesterday, shortly after I did the testing - unknowing that it 
would fix this bug as well :-)

Thanks,

	Ingo

      reply	other threads:[~2012-03-03  7:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 16:32 [PATCH] " David Ahern
2012-02-09  1:19 ` Namhyung Kim
2012-02-09  2:52   ` David Ahern
2012-02-09  5:36     ` Namhyung Kim
2012-02-09  6:04       ` David Ahern
2012-02-09  7:37     ` Ingo Molnar
2012-02-09 14:34       ` Arnaldo Carvalho de Melo
2012-02-09 14:44         ` Arnaldo Carvalho de Melo
2012-02-10  5:42           ` Namhyung Kim
2012-02-10 14:28             ` Arnaldo Carvalho de Melo
2012-02-12 10:45               ` [PATCH] perf tools: Fix build dependency of perf python extension Namhyung Kim
2012-02-17  9:44                 ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-02-10 19:24 ` [PATCH] perf tools: Allow multiple threads or processes in record, stat, top Arnaldo Carvalho de Melo
2012-02-10 19:32   ` David Ahern
2012-02-10 19:34     ` Arnaldo Carvalho de Melo
2012-02-10 19:46       ` David Ahern
2012-02-10 19:58         ` Arnaldo Carvalho de Melo
2012-02-17  9:46 ` [tip:perf/core] " tip-bot for David Ahern
2012-03-02 10:56   ` Ingo Molnar
2012-03-02 14:21     ` David Ahern
2012-03-02 14:52     ` David Ahern
2012-03-03  7:42       ` Ingo Molnar [this message]

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=20120303074202.GB16816@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®