All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org, acme@kernel.org
Subject: Re: perf list SEGV still present in mainline?
Date: Tue, 5 Jan 2016 16:43:04 -0200	[thread overview]
Message-ID: <20160105184304.GA2503@redhat.com> (raw)
In-Reply-To: <20151222144022.GG32623@arm.com>

Em Tue, Dec 22, 2015 at 02:40:22PM +0000, Will Deacon escreveu:
> Hi Arnaldo,
> 
> I'm seeing a SEGV running mainline perf list on my x86 and arm machines,
> thanks to a missing array entry for PERF_COUNT_SW_BPF_OUTPUT in
> util/parse-events.c.
> 
> This seems to have been fixed in -next by ("perf list: Add support for
> PERF_COUNT_SW_BPF_OUT"), but for some reason its not made it into
> mainline nearly a month later!
> 
> Do you plan to send this upstream as a fix for 4.4?

This one is sitting in perf/urgent waiting for Ingo to push it upstream,
should go in his next pull req to Linus.

- Arnaldo

      reply	other threads:[~2016-01-05 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 14:40 perf list SEGV still present in mainline? Will Deacon
2016-01-05 18:43 ` Arnaldo Carvalho de Melo [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=20160105184304.GA2503@redhat.com \
    --to=acme@redhat.com \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.