From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Stephane Eranian <eranian@google.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
acme@redhat.com, mingo@elte.hu, paulus@samba.org,
cjashfor@linux.vnet.ibm.com, fweisbec@gmail.com,
gorcunov@openvz.org, tzanussi@gmail.com, mhiramat@redhat.com,
robert.richter@amd.com, fche@redhat.com,
linux-kernel@vger.kernel.org, masami.hiramatsu.pt@hitachi.com,
drepper@gmail.com, asharma@fb.com,
benjamin.redelings@nescent.org
Subject: Re: [PATCH 02/16] perf: Add ability to attach registers dump to sample
Date: Thu, 24 May 2012 12:42:22 +0200 [thread overview]
Message-ID: <1337856142.9783.104.camel@laptop> (raw)
In-Reply-To: <CABPqkBR9hewjNUJf9ByD-jHc42e_qwQiKoP68RyL7BU8Q7BGgQ@mail.gmail.com>
On Thu, 2012-05-24 at 12:06 +0200, Stephane Eranian wrote:
> > What are we doing here and why?
> >
> I think this is related to a discusion we had earlier about which
> machine state you want
> to sample.
>
> There are 3 possible machine states:
> 1- user level (even when sample is in kernel AND assuming you did
> not hit a kernel only thread)
> 2- interrupted state (@ PMU interrupt)
> 3- precise state (state captured by PEBS on Intel, for instance)
>
> Jiri is only interested in 1/. I am interested in the other two as well.
>
> Question: is there a situation where we could need more than one machine
> state per sample?
Well, IIRC you always wanted both 2 and 3 at the same time to compute
skid, thus:
> If not, then a single bitmask is enough.
Indeed, so then we get to multiple bitmasks and unless you want to be
restricted to the same bitmap for all these types this setup won't
actually work.
Also, all that was missing from the changelog.
next prev parent reply other threads:[~2012-05-24 10:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 19:31 [RFCv4 00/16] perf: Add backtrace post dwarf unwind Jiri Olsa
2012-05-23 19:32 ` [PATCH 01/16] perf: Unified API to record selective sets of arch registers Jiri Olsa
2012-05-24 9:33 ` Peter Zijlstra
2012-05-24 12:13 ` Stephane Eranian
2012-05-24 12:37 ` Jiri Olsa
2012-05-24 9:43 ` Peter Zijlstra
2012-06-07 9:46 ` Frederic Weisbecker
2012-06-07 10:29 ` Peter Zijlstra
2012-06-07 10:31 ` Frederic Weisbecker
2012-06-07 10:36 ` Stephane Eranian
2012-05-23 19:32 ` [PATCH 02/16] perf: Add ability to attach registers dump to sample Jiri Olsa
2012-05-24 9:50 ` Peter Zijlstra
2012-05-24 10:06 ` Stephane Eranian
2012-05-24 10:42 ` Peter Zijlstra [this message]
2012-05-24 11:52 ` Jiri Olsa
2012-05-25 10:01 ` Peter Zijlstra
2012-06-07 9:56 ` Frederic Weisbecker
2012-05-24 9:51 ` Peter Zijlstra
2012-05-24 9:57 ` Peter Zijlstra
2012-05-23 19:32 ` [PATCH 03/16] perf: Factor __output_copy to be usable with specific copy function Jiri Olsa
2012-05-23 19:32 ` [PATCH 04/16] perf: Add ability to attach user stack dump to sample Jiri Olsa
2012-05-24 10:44 ` Peter Zijlstra
2012-05-24 10:51 ` Peter Zijlstra
2012-05-24 12:16 ` Jiri Olsa
2012-06-07 10:07 ` Frederic Weisbecker
2012-06-07 14:07 ` Jiri Olsa
2012-05-23 19:32 ` [PATCH 05/16] perf: Add attribute to filter out user callchains Jiri Olsa
2012-05-24 10:57 ` Peter Zijlstra
2012-05-23 19:32 ` [PATCH 06/16] perf, tool: Factor DSO symtab types to generic binary types Jiri Olsa
2012-05-23 19:32 ` [PATCH 07/16] perf, tool: Add interface to read DSO image data Jiri Olsa
2012-05-23 19:32 ` [PATCH 08/16] perf, tool: Add '.note' check into search for NOTE section Jiri Olsa
2012-05-23 19:32 ` [PATCH 09/16] perf, tool: Back [vdso] DSO with real data Jiri Olsa
2012-05-23 19:32 ` [PATCH 10/16] perf, tool: Add interface to arch registers sets Jiri Olsa
2012-05-23 19:32 ` [PATCH 11/16] perf, tool: Add libunwind dependency for dwarf cfi unwinding Jiri Olsa
2012-05-23 19:32 ` [PATCH 12/16] perf, tool: Support user regs and stack in sample parsing Jiri Olsa
2012-05-23 19:32 ` [PATCH 13/16] perf, tool: Support for dwarf cfi unwinding on post processing Jiri Olsa
2012-05-23 19:32 ` [PATCH 14/16] perf, tool: Support for dwarf mode callchain on perf record Jiri Olsa
2012-05-23 19:32 ` [PATCH 15/16] perf, tool: Add dso data caching Jiri Olsa
2012-05-23 19:32 ` [PATCH 16/16] perf, tool: Add dso data caching tests Jiri Olsa
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=1337856142.9783.104.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=asharma@fb.com \
--cc=benjamin.redelings@nescent.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=drepper@gmail.com \
--cc=eranian@google.com \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gorcunov@openvz.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=robert.richter@amd.com \
--cc=tzanussi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox