public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Stephane Eranian <eranian@google.com>,
	linux-kernel@vger.kernel.org, mingo@elte.hu,
	peterz@infradead.org, dsahern@gmail.com, ak@linux.intel.com,
	jolsa@redhat.com, hughd@google.com, keescook@chromium.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH] perf: disable mmap2 support
Date: Thu, 10 Oct 2013 06:56:35 +0200	[thread overview]
Message-ID: <20131010045635.GC23267@gmail.com> (raw)
In-Reply-To: <20131009193322.GA3794@infradead.org>


* Arnaldo Carvalho de Melo <acme@redhat.com> wrote:

> Em Wed, Oct 09, 2013 at 06:17:43PM +0200, Stephane Eranian escreveu:

> > This patch disables the mmap2 record format support for now. The 
> > support needs a bit more work to cover VM_CLONE cases.
> > 
> > The patch leaves attr->mmap2 defined, but returns an error if it is 
> > set. That ensures no PERF_RECORD_MMAP2 record can be generated. Yet it 
> > minimizes the reverts in the perf tool.
> 
> Would be interesting to have a simple new tool that would detect all the 
> mmaps that are shared in a given perf.data file, using the 
> PERF_RECORD_MMAP2 information, and that tool should come together with 
> the reworked kernel ABI, showing how it is used.

Indeed. Let's make that a requirement for the next round of mmap2 patches. 

Issues like this is really why I hate not getting a fully functional 
usecase together with a new ABI - it's _so_ easy to come up with something 
subtly (or not so subtly) incomplete.

> A 'perf test' entry, based on the test programs you guys are using to 
> test this functionality would be even better, showing that all cases 
> you've been striving to cover are in fact covered by the new ABI.

That too, in addition to an actual tool that people can use.

Thanks,

	Ingo

      reply	other threads:[~2013-10-10  4:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 16:17 [PATCH] perf: disable mmap2 support Stephane Eranian
2013-10-09 16:21 ` David Ahern
2013-10-09 16:24   ` Stephane Eranian
2013-10-09 16:39     ` Stephane Eranian
2013-10-09 17:19       ` David Ahern
2013-10-09 17:40         ` Stephane Eranian
2013-10-09 18:03           ` David Ahern
2013-10-10 14:26             ` Arnaldo Carvalho de Melo
2013-10-11 18:40           ` David Ahern
2013-10-15 12:25             ` Stephane Eranian
2013-10-15 13:12               ` Ingo Molnar
2013-10-15 13:27                 ` Stephane Eranian
2013-10-15 13:34                   ` Ingo Molnar
2013-10-15 14:32                     ` Stephane Eranian
2013-10-15 16:04                       ` Ingo Molnar
2013-10-09 19:33 ` Arnaldo Carvalho de Melo
2013-10-10  4:56   ` Ingo Molnar [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=20131010045635.GC23267@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=hughd@google.com \
    --cc=jolsa@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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