kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: subingangadharan@gmail.com (subin gangadharan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: arm assembly doubt
Date: Sat, 18 Feb 2012 09:44:42 -0700	[thread overview]
Message-ID: <CAKRO8zLw-Uv4zw4oM_gKHT2V4E4pveE0H87c4fUV_PmUw_MKLQ@mail.gmail.com> (raw)
In-Reply-To: <BLU156-W139DAC639CFCC3AB603D66BC600@phx.gbl>

Hi ,

Thanks alot for sharing the information.

2012/2/18 ??? <buyit@live.cn>:
> Hi:
>
>      the  SWI is used for system APIs such as open, read, write. user mode
> applications call system APIs via SWI, which will change ARM mode from USER
> to SVC.
>      so when vector_swi is called, Linux will do as below:
>      1. store r0~r12, these registers are universal for USR mode SVC mode.
>      2. store r13 and r14 of USER mode. Note, SWI is triggered from USER
> mode, so here Linux store USER mode's r13 and r14, rather than SVC's.
>
>      for your two questions:
>      1. the ^ means to get USER mode registers, rather than current mode.
>      2. no matter how you arrange registers in opcode {}, stmdb will always
> push lr first, then sp. so after line 348, the stack view is as below:
> lr_usr
> sp_usr
> r12
> ...
> r0

This is where I really got confused,I was thinking sp will be pushed
first in that case stack view will be completely different. However
the system is working fine,so was sure there is some secret behind
this instruction.Thanks for revealing this mystery.


>
>> Date: Thu, 16 Feb 2012 19:35:17 -0700
>> Subject: Re: arm assembly doubt
>> From: subingangadharan at gmail.com
>> To: suren at gatech.edu
>> CC: kernelnewbies at kernelnewbies.org
>
>>
>> Thanks for the answer. Actually this is what I am trying to understand.
>>
>> ENTRY(vector_swi)
>> 345 sub sp, sp, #S_FRAME_SIZE
>> 346 stmia sp, {r0 - r12} @ Calling r0 - r12
>> 347 ARM( add r8, sp, #S_PC )
>> 348 ARM( stmdb r8, {sp, lr}^ ) @ Calling sp, lr
>> 349 THUMB( mov r8, sp )
>> 350 THUMB( store_user_sp_lr r8, r10, S_SP ) @ calling sp, lr
>> 351 mrs r8, spsr @ called from
>> non-FIQ mode, so ok.
>> 352 str lr, [sp, #S_PC] @ Save calling PC
>> 353 str r8, [sp, #S_PSR] @ Save CPSR
>> 354 str r0, [sp, #S_OLD_R0]
>>
>> In this case after the line number 348(if its in arm mode),will the
>> kernel stack have the contents
>> r0-r12,sp,lr in this order or r0-r12,lr,sp this one. Beccause I
>> believe stmdb r8, {sp, lr}^ will push the sp first then lr. In that
>> case sp and lr will be interchanged in struct pt_regs.
>>
>> Please correct me if I am wrong.
>>
>>
>>
>>
>>
>> On Wed, Feb 15, 2012 at 9:34 PM, Surenkumar Nihalani <suren@gatech.edu>
>> wrote:
>> > Hi,
>> > On Feb 15, 2012, at 11:30 PM, subin gangadharan wrote:
>> >
>> >> Hi ,
>> >>
>> >> I am trying to understand how system call is implmented in linux for
>> >> arm.And I am not that familiar with arm assembly.
>> >>
>> >> Could any body please help me to understand what exactly this ^ does
>> >> in this instruction stmdb r8,{sp,lr}^
>> >>
>> >> --
>> >> With Regards
>> >> Subin Gangadharan
>> >>
>> >> I am not afraid and I am also not afraid of being afraid.
>> >>
>> >> _______________________________________________
>> >> Kernelnewbies mailing list
>> >> Kernelnewbies at kernelnewbies.org
>> >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>> >
>> > Example:
>> >        LDFMD sp!, {r0-r12, pc}^
>> > - The ^ qualifier specifies that the CPSR is restored from the SPSR.
>> >   It must be used only from a privileged mode.
>> >
>>
>>
>>
>> --
>> With Regards
>> Subin Gangadharan
>>
>> I am not afraid and I am also not afraid of being afraid.
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



-- 
With Regards
Subin Gangadharan

I am not afraid and I am also not afraid of being afraid.

      reply	other threads:[~2012-02-18 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16  4:30 arm assembly doubt subin gangadharan
2012-02-16  4:34 ` Surenkumar Nihalani
2012-02-17  2:35   ` subin gangadharan
2012-02-18 13:36     ` 卜弋天
2012-02-18 16:44       ` subin gangadharan [this message]

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=CAKRO8zLw-Uv4zw4oM_gKHT2V4E4pveE0H87c4fUV_PmUw_MKLQ@mail.gmail.com \
    --to=subingangadharan@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).