From: nikolay.borisov@arm.com (Nikolay Borisov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/7] ARM: Introduce arm_get_current_stack_frame()
Date: Tue, 13 May 2014 15:57:57 +0100 [thread overview]
Message-ID: <000501cf6ebb$ba64ed70$2f2ec850$@borisov@arm.com> (raw)
In-Reply-To: <20140513145526.GX32718@rric.localhost>
> -----Original Message-----
> From: Robert Richter [mailto:rric.net at gmail.com] On Behalf Of Robert
> Richter
> Sent: 13 May 2014 15:55
> To: Nikolay Borisov
> Cc: linux-arm-kernel at lists.infradead.org; Dave P Martin; Will Deacon;
> anurag19aggarwal at gmail.com; a.p.zijlstra at chello.nl;
> sebastian.hesselbarth at gmail.com
> Subject: Re: [PATCH 2/7] ARM: Introduce arm_get_current_stack_frame()
>
> On 13.05.14 10:46:53, Nikolay Borisov wrote:
> > #define instruction_pointer(regs) (regs)->ARM_pc
> > +#define frame_pointer(regs) \
> > + IS_ENABLED(CONFIG_THUMB2_KERNEL) ? regs->ARM_r7 \
> > + : regs->ARM_fp \
>
> (regs)->... should be used here both.
>
Yeah, I fixed it already in my local version. Thanks.
> -Robert
next prev parent reply other threads:[~2014-05-13 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 9:46 [PATCH 0/7] Fix handling of FP in THUMB2 mode Nikolay Borisov
2014-05-13 9:46 ` [PATCH 1/7] ARM: Make thread_save_fp macro aware of " Nikolay Borisov
2014-05-13 9:46 ` [PATCH 2/7] ARM: Introduce arm_get_current_stack_frame() Nikolay Borisov
2014-05-13 14:55 ` Robert Richter
2014-05-13 14:57 ` Nikolay Borisov [this message]
2014-05-13 9:46 ` [PATCH 3/7] ARM: perf: Make perf use arm_get_current_stackframe Nikolay Borisov
2014-05-13 9:46 ` [PATCH 4/7] ARM: time: Make use of arm_get_current_stackframe Nikolay Borisov
2014-05-13 9:46 ` [PATCH 5/7] ARM: unwind: Use arm_get_current_stackframe Nikolay Borisov
2014-05-13 9:46 ` [PATCH 6/7] ARM: traps: Make use of the frame_pointer macro Nikolay Borisov
2014-05-13 9:46 ` [PATCH 7/7] ARM: oprofile: Use of arm_get_current_stackframe Nikolay Borisov
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='000501cf6ebb$ba64ed70$2f2ec850$@borisov@arm.com' \
--to=nikolay.borisov@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.