linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lauraa@codeaurora.org (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Add unwinding annotations for 64bit division functions
Date: Mon, 19 Sep 2011 18:55:39 -0700 (PDT)	[thread overview]
Message-ID: <2285dff3fee56758b6279062a5a30dc7.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1109191913210.12663@xanadu.home>


On Mon, September 19, 2011 4:22 pm, Nicolas Pitre wrote:
> On Mon, 19 Sep 2011, Laura Abbott wrote:
>
>> The 64bit division functions never had unwinding annotations
>> added. This prevents a backtrace from being printed within
>> the function and if a division by 0 occurs. Add the annotations.
>>
>> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
>> ---
>>  arch/arm/lib/div64.S |    8 ++++++++
>>  1 files changed, 8 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/lib/div64.S b/arch/arm/lib/div64.S
>> index faa7748..e55c484 100644
>> --- a/arch/arm/lib/div64.S
>> +++ b/arch/arm/lib/div64.S
>> @@ -13,6 +13,7 @@
>>   */
>>
>>  #include <linux/linkage.h>
>> +#include <asm/unwind.h>
>>
>>  #ifdef __ARMEB__
>>  #define xh r0
>> @@ -44,6 +45,7 @@
>>   */
>>
>>  ENTRY(__do_div64)
>> +UNWIND(.fnstart)
>>
>>  	@ Test for easy paths first.
>>  	subs	ip, r4, #1
>> @@ -189,7 +191,12 @@ ENTRY(__do_div64)
>>  	moveq	yh, xh
>>  	moveq	xh, #0
>>  	moveq	pc, lr
>> +UNWIND(.fnend)
>>
>> +UNWIND(.fnstart)
>> +UNWIND(.pad #4)
>> +UNWIND(.save {lr})
>> +Ldiv0_64:
>
> Why this phony fnend+fnstart here?
>
If a division by 0 occurs, we need to be able to access the saved LR on
the stack which is setup right before calling the __div0 function. This
can't go at the top of __do_div64 because if we try to do a backtrace from
within __do_div64 the annotation won't be correct as the LR was never
saved on the stack. (yes, __do_div64 is all register math but it's still
possible to take a prefetch abort in the middle of that function. Taking a
prefetch abort in the middle of __do_div64 is what found this issue in the
first place.) This setup handles both cases correctly.

>
> Nicolas
>

Laura

> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>


-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-09-20  1:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19 22:11 [PATCH] arm: Add unwinding annotations for 64bit division functions Laura Abbott
2011-09-19 23:22 ` Nicolas Pitre
2011-09-20  1:55   ` Laura Abbott [this message]
2011-09-20 13:27     ` Nicolas Pitre
2011-09-20 14:57       ` Catalin Marinas
2011-09-21 11:39     ` Dave Martin
2011-09-21 11:55       ` Russell King - ARM Linux
2011-09-21 13:33         ` Dave Martin
2011-09-22  7:28         ` Jon Medhurst (Tixy)
2011-09-22  9:48           ` Catalin Marinas
2011-09-22 11:06             ` Jon Medhurst (Tixy)
2011-09-22 11:57               ` Catalin Marinas
2011-09-22 12:13                 ` Jon Medhurst (Tixy)
2011-09-22 13:00                   ` Catalin Marinas
2011-09-22 13:19                     ` Jon Medhurst (Tixy)

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=2285dff3fee56758b6279062a5a30dc7.squirrel@www.codeaurora.org \
    --to=lauraa@codeaurora.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).