From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, jolsa@redhat.com,
Mansour Alharthi <malharthi9@gatech.edu>
Subject: Re: [PATCH v0 1/2] perf: Copy parent's address filter offsets on clone
Date: Fri, 22 Feb 2019 11:54:42 -0300 [thread overview]
Message-ID: <20190222145442.GA26132@kernel.org> (raw)
In-Reply-To: <87d0nkc77p.fsf@ashishki-desk.ger.corp.intel.com>
Em Fri, Feb 22, 2019 at 02:56:26PM +0200, Alexander Shishkin escreveu:
> Arnaldo Carvalho de Melo <acme@redhat.com> writes:
>
> > Em Fri, Feb 15, 2019 at 01:56:54PM +0200, Alexander Shishkin escreveu:
> >> When a child event is allocated in the inherit_event() path, the VMA
> >> based filter offsets are not copied from the parent, even though the
> >> address space mapping of the new task remains the same, which leads
> >> to no trace for the new task until exec.
> >
> > Peter, I'm processing this one, ok? Ack?
>
> Any news on this one?
Will process it now, was waiting for some ack from Peter.
- Arnaldo
next prev parent reply other threads:[~2019-02-22 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 11:56 [PATCH v0 0/2] perf: Address range filtering fixes Alexander Shishkin
2019-02-15 11:56 ` [PATCH v0 1/2] perf: Copy parent's address filter offsets on clone Alexander Shishkin
2019-02-15 18:10 ` Arnaldo Carvalho de Melo
2019-02-22 12:56 ` Alexander Shishkin
2019-02-22 14:54 ` Arnaldo Carvalho de Melo [this message]
2019-02-28 7:57 ` [tip:perf/core] " tip-bot for Alexander Shishkin
2019-02-15 11:56 ` [PATCH v0 2/2] perf, pt, coresight: Fix address filters for vmas with non-zero offset Alexander Shishkin
2019-02-15 14:54 ` Arnaldo Carvalho de Melo
2019-02-15 17:38 ` Mathieu Poirier
2019-02-28 7:58 ` [tip:perf/core] " tip-bot for Alexander Shishkin
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=20190222145442.GA26132@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malharthi9@gatech.edu \
--cc=mingo@redhat.com \
--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