public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <bitbucket@online.de>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: perf: perf sched lat segfault - bisected
Date: Tue, 08 Oct 2013 12:41:10 +0200	[thread overview]
Message-ID: <1381228870.15686.15.camel@marge.simpson.net> (raw)
In-Reply-To: <CABPqkBQD9TE7RbP-auXO060aU1QNU=RUw2QZvoF39CCqpzdC4w@mail.gmail.com>

On Tue, 2013-10-08 at 12:25 +0200, Stephane Eranian wrote: 
> Mike,
> 
> Ok, I missed the sched record, let me track this down.
> Note that there was a second commit to fix this one
> by Arnaldo. Do you also have it in your kernel?
> 
> 51131c4 perf: Fix up MMAP2 buffer space reservation

Not with that commit id, but..

commit d008d5258e9c1a1b7ee6547b8d444323aef331b3
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Tue Sep 10 10:24:05 2013 -0300

    perf: Fix up MMAP2 buffer space reservation

-Mike


  parent reply	other threads:[~2013-10-08 10:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  8:41 perf: perf sched lat segfault - bisected Mike Galbraith
2013-10-08  9:23 ` Stephane Eranian
2013-10-08 10:14   ` Mike Galbraith
2013-10-08 10:20     ` Mike Galbraith
2013-10-08 10:25       ` Stephane Eranian
2013-10-08 10:36         ` Stephane Eranian
2013-10-08 10:50           ` Mike Galbraith
2013-10-08 10:51             ` Stephane Eranian
2013-10-08 10:56               ` Mike Galbraith
2013-10-08 10:57                 ` Stephane Eranian
2013-10-08 10:41         ` Mike Galbraith [this message]
2013-10-08 12:17 ` Arnaldo Carvalho de Melo
2013-10-08 12:27   ` Mike Galbraith
2013-10-08 12:35     ` Mike Galbraith
2013-10-08 13:20       ` David Ahern
2013-10-08 13:44         ` Mike Galbraith

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=1381228870.15686.15.camel@marge.simpson.net \
    --to=bitbucket@online.de \
    --cc=acme@redhat.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    /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