public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <dsahern@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: perf_guest default bug
Date: Sat, 3 Mar 2012 12:19:12 -0300	[thread overview]
Message-ID: <20120303151912.GD16301@infradead.org> (raw)
In-Reply-To: <20120303140405.GB16301@infradead.org>

Em Sat, Mar 03, 2012 at 11:04:05AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Mar 02, 2012 at 12:00:01PM -0700, David Ahern escreveu:
> > Similar to my last email, this patch is not in urgent trees or
> > Linus' yet the problem exists in Linus' tree:
> > https://lkml.org/lkml/2012/2/17/82
> > 
> > $ /tmp/pbuild/perf record -a  -- sleep 1
> > [ perf record: Woken up 1 times to write data ]
> > [ perf record: Captured and wrote 0.319 MB perf.data (~13935 samples) ]
> > Segmentation fault
> > 
> > Root cause is the perf_guest setting.
> > 
> > $ /tmp/pbuild/perf --version
> > perf version 3.3.rc5.60.g203738
> 
> This one was tricky, IIRC, weren't follow up patches needed to plug some
> extra problems?

Yeah, just trying cherry picking it and trying it on an RHEL6.2 kernel
and it didn't work because older kernels don't have
attr.exclude_{guest,host}, so I had to also cherrypick:

[acme@sandy linux]$ git cherry-pick
0c9781280fb672ca09c997df3f14ba506bbdb977
Finished one cherry-pick.
[perf/urgent b5f81a4] perf tools: Handle kernels that don't support attr.exclude_{guest,host}

- Arnaldo

  reply	other threads:[~2012-03-03 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 19:00 perf_guest default bug David Ahern
2012-03-03 14:04 ` Arnaldo Carvalho de Melo
2012-03-03 15:19   ` Arnaldo Carvalho de Melo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-03 15:29 David Ahern

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=20120303151912.GD16301@infradead.org \
    --to=acme@ghostprotocols.net \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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