public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Stephane Eranian <eranian@google.com>,
	linux-kernel@vger.kernel.org, ak@linux.intel.com,
	kan.liang@intel.com, mingo@elte.hu, jolsa@redhat.com,
	acme@kernel.org
Subject: Re: [PATCH] perf/core: restore mmap record type correctly
Date: Thu, 7 Mar 2019 20:09:39 +0100	[thread overview]
Message-ID: <20190307190939.GB2482@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20190307190330.GA2443@redhat.com>

On Thu, Mar 07, 2019 at 04:03:30PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Mar 07, 2019 at 10:52:33AM -0800, Stephane Eranian escreveu:
> > On mmap(), perf_events generates a RECORD_MMAP record and then checks
> > which events are interested in this record. There are currently 2 versions
> > of mmap records: RECORD_MMAP and RECORD_MMAP2. MMAP2 is larger. The event
> > configuration controls which version the user level tool accepts. If the
> > event->attr.mmap2=1 field then MMAP2 record is returned. The
> > perf_event_mmap_output() takes care of this. It checks attr->mmap2 and corrects
> > the record fields before putting it in the sampling buffer of the event.
> > At the end the function restores the modified MMAP record fields.
> > 
> > The problem is that the function restores the size but not the
> > type. Thus, if a subsequent event only accepts MMAP type, then it would
> > instead receive an MMAP2 record with a size of MMAP record.
> > 
> > This patch fixes the problem by restoring the record type on exit.
> 
> Right, simple enough, bug fixed, Peter, I'm taking this one, ok?

Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>

  reply	other threads:[~2019-03-07 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 18:52 [PATCH] perf/core: restore mmap record type correctly Stephane Eranian
2019-03-07 19:03 ` Arnaldo Carvalho de Melo
2019-03-07 19:09   ` Peter Zijlstra [this message]
2019-03-07 19:26     ` Arnaldo Carvalho de Melo
2019-03-07 19:28       ` Stephane Eranian
2019-03-22 21:58 ` [tip:perf/urgent] perf/core: Restore " tip-bot for Stephane Eranian

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=20190307190939.GB2482@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@intel.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