From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 1/7] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature
Date: Tue, 18 Aug 2015 10:38:18 +0100 [thread overview]
Message-ID: <20150818093817.GE10301@arm.com> (raw)
In-Reply-To: <55CC1410.1090900@linaro.org>
Hi David,
On Thu, Aug 13, 2015 at 04:50:40AM +0100, David Long wrote:
> On 08/11/15 13:31, Will Deacon wrote:
> > On Tue, Aug 11, 2015 at 01:52:38AM +0100, David Long wrote:
> >> + REG_OFFSET_NAME(x30),
> >
> > Does this interact badly with perf tools, which expect to pass "lr" for
> > x30? (see tools/perf/arch/arm64/include/perf_regs.h).
> >
>
> Possibly, I can test that when I'm back from my short vacation this
> week. The lr/x30 thing seems to be a recurring issue. Perhaps it is
> best simply to add a reundant entry for x30 as "lr". It's simple enough
> to do, although just slightly ugly looking as it would have to be done
> without a macro. Would one ever use "x31" in place of "sp"?
No; "sp" should always be "sp". Let me know how you get on with perf. I
couldn't quite tie the two ends together, but it does look like it expects
"lr" to work.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: David Long <dave.long@linaro.org>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Russell King <linux@arm.linux.org.uk>,
"sandeepa.s.prabhu@gmail.com" <sandeepa.s.prabhu@gmail.com>,
William Cohen <wcohen@redhat.com>,
Steve Capper <steve.capper@linaro.org>,
"Jon Medhurst (Tixy)" <tixy@linaro.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
Mark Brown <broonie@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 1/7] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature
Date: Tue, 18 Aug 2015 10:38:18 +0100 [thread overview]
Message-ID: <20150818093817.GE10301@arm.com> (raw)
In-Reply-To: <55CC1410.1090900@linaro.org>
Hi David,
On Thu, Aug 13, 2015 at 04:50:40AM +0100, David Long wrote:
> On 08/11/15 13:31, Will Deacon wrote:
> > On Tue, Aug 11, 2015 at 01:52:38AM +0100, David Long wrote:
> >> + REG_OFFSET_NAME(x30),
> >
> > Does this interact badly with perf tools, which expect to pass "lr" for
> > x30? (see tools/perf/arch/arm64/include/perf_regs.h).
> >
>
> Possibly, I can test that when I'm back from my short vacation this
> week. The lr/x30 thing seems to be a recurring issue. Perhaps it is
> best simply to add a reundant entry for x30 as "lr". It's simple enough
> to do, although just slightly ugly looking as it would have to be done
> without a macro. Would one ever use "x31" in place of "sp"?
No; "sp" should always be "sp". Let me know how you get on with perf. I
couldn't quite tie the two ends together, but it does look like it expects
"lr" to work.
Will
next prev parent reply other threads:[~2015-08-18 9:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 0:52 [PATCH v8 0/7] arm64: Add kernel probes (kprobes) support David Long
2015-08-11 0:52 ` David Long
2015-08-11 0:52 ` [PATCH v8 1/7] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature David Long
2015-08-11 0:52 ` David Long
2015-08-11 17:31 ` Will Deacon
2015-08-11 17:31 ` Will Deacon
2015-08-13 3:50 ` David Long
2015-08-13 3:50 ` David Long
2015-08-18 9:38 ` Will Deacon [this message]
2015-08-18 9:38 ` Will Deacon
2015-08-11 0:52 ` [PATCH v8 2/7] arm64: Add more test functions to insn.c David Long
2015-08-11 0:52 ` David Long
2015-08-11 18:00 ` Will Deacon
2015-08-11 18:00 ` Will Deacon
2015-08-13 4:23 ` David Long
2015-08-13 4:23 ` David Long
2015-08-11 0:52 ` [PATCH v8 3/7] arm64: Kprobes with single stepping support David Long
2015-08-11 0:52 ` David Long
2015-08-12 13:37 ` Will Deacon
2015-08-12 13:37 ` Will Deacon
2015-12-08 6:05 ` David Long
2015-12-08 6:05 ` David Long
2015-08-13 11:42 ` Steve Capper
2015-08-13 11:42 ` Steve Capper
2015-08-11 0:52 ` [PATCH v8 4/7] arm64: kprobes instruction simulation support David Long
2015-08-11 0:52 ` David Long
2015-08-12 14:29 ` Will Deacon
2015-08-12 14:29 ` Will Deacon
2015-08-11 0:52 ` [PATCH v8 5/7] arm64: Add trampoline code for kretprobes David Long
2015-08-11 0:52 ` David Long
2015-08-12 14:47 ` Will Deacon
2015-08-12 14:47 ` Will Deacon
2015-08-11 0:52 ` [PATCH v8 6/7] arm64: Add kernel return probes support (kretprobes) David Long
2015-08-11 0:52 ` David Long
2015-08-11 0:52 ` [PATCH v8 7/7] kprobes: Add arm64 case in kprobe example module David Long
2015-08-11 0:52 ` David Long
2015-08-12 16:22 ` Steve Capper
2015-08-12 16:22 ` Steve Capper
2015-08-11 16:56 ` [PATCH v8 0/7] arm64: Add kernel probes (kprobes) support Will Deacon
2015-08-11 16:56 ` Will Deacon
2015-08-11 17:03 ` David Long
2015-08-11 17:03 ` David Long
2015-08-11 17:36 ` Will Deacon
2015-08-11 17:36 ` Will Deacon
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=20150818093817.GE10301@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.