From: Andi Kleen <andi@firstfloor.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Stephane Eranian <eranian@google.com>,
Jiri Olsa <jolsa@redhat.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
linux-man@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Chuck Ebbert <cebbert.lkml@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [patch] perf_event_open.2: 3.19 PERF_SAMPLE_REGS_INTR support
Date: Mon, 2 Mar 2015 23:58:07 +0100 [thread overview]
Message-ID: <20150302225807.GJ823@two.firstfloor.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1503021721090.20187@vincent-weaver-1.umelst.maine.edu>
> do not enable REGS_USER and REG_INTR at the same time
> as REGS_USER will have REG_INTR values and
> cannot be used for user stack unwinding
If that's true it would be a bug. But I doubt it.
The PEBS handler sets up its own pt_regs, so they should
be independent.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2015-03-02 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 5:33 [patch] perf_event_open.2: 3.19 PERF_SAMPLE_REGS_INTR support Vince Weaver
2015-02-17 5:33 ` Michael Kerrisk (man-pages)
2015-02-26 7:51 ` Michael Kerrisk (man-pages)
2015-02-28 22:26 ` Jiri Olsa
2015-03-01 14:14 ` Stephane Eranian
2015-03-02 19:31 ` Vince Weaver
2015-03-02 20:26 ` Stephane Eranian
2015-03-02 21:19 ` Vince Weaver
2015-03-02 21:22 ` Stephane Eranian
2015-03-02 22:23 ` Vince Weaver
2015-03-02 22:30 ` Stephane Eranian
2015-03-02 22:58 ` Andi Kleen [this message]
2015-03-06 18:37 ` Vince Weaver
2015-03-06 19:51 ` Stephane Eranian
2015-03-06 23:05 ` Andi Kleen
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=20150302225807.GJ823@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=cebbert.lkml@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.weaver@maine.edu \
/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