From: David Ahern <dsahern@gmail.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-perf-users@vger.kernel.org, ak <ak@linux.intel.com>
Subject: Re: Perf record premature termination
Date: Tue, 12 Feb 2013 10:16:21 -0700 [thread overview]
Message-ID: <511A78E5.8000909@gmail.com> (raw)
In-Reply-To: <1360688851.17632.195.camel@schen9-DESK>
On 2/12/13 10:07 AM, Tim Chen wrote:
> On Mon, 2013-02-11 at 15:30 -0700, David Ahern wrote:
>> On 2/11/13 3:15 PM, Tim Chen wrote:
>>> On Mon, 2013-02-11 at 12:34 -0700, David Ahern wrote:
>>>> On 2/11/13 11:50 AM, Tim Chen wrote:
>>>>> David,
>>>>>
>>>>> When I am doing a profiling of kernel compile with 32 threads on a 4
>>>>> socket westmere machine, I found that perf record terminated right away
>>>>> for the version of perf in 3.7 kernel source tree.
>>>>> There's no profile data recroded and the compile is running in
>>>>> background.
>>>>>
>>>>> $ make -j32 &
>>>>> then
>>>>> $ sudo /test/perf record -a -g -f sleep 5
>>>>> sleep: Terminated
>>
>> This is the more appropriate fix. Make mmap consistent with comm. Revert
>> the other one.
>
> Thanks. Works for me.
>
> Tim
>
BTW, this does not seem to be a problem with 3.8 - at least I could not
reproduce it. So it seems limited to 3.7 kernels only.
David
prev parent reply other threads:[~2013-02-12 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 18:50 Perf record premature termination Tim Chen
2013-02-11 19:05 ` David Ahern
2013-02-11 19:34 ` David Ahern
2013-02-11 22:15 ` Tim Chen
2013-02-11 22:30 ` David Ahern
2013-02-12 17:07 ` Tim Chen
2013-02-12 17:16 ` David Ahern [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=511A78E5.8000909@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tim.c.chen@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).