From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Doubt regarding asmlinkage
Date: Thu, 8 Sep 2011 11:20:26 +0700 [thread overview]
Message-ID: <CAGdaadby2A232qrKJaUj3euSAp5HdNPe-4eXSqEArxW9HGisSA@mail.gmail.com> (raw)
In-Reply-To: <CALJfu6PYT1k_yicGqkrS_p-2P14e0xw9v6FyDxd35CvQ-WT4Jw@mail.gmail.com>
Hi :)
On Thu, Sep 8, 2011 at 10:40, rohan puri <rohan.puri15@gmail.com> wrote:
> Hi Mulyadi,
>
> Thanks for the response. I do agree with the issue concerning the no.of
> registers available are less for 32 bit to that of 64 bit.
>
> But even in this case if parameters are more than the no of register for 32
> bit, then also before executing int 80h interrupt it stores the parameters
> in the register and after that system call dispatcher puts them on the
> kernel stack of that process. So, how the case where more than no of
> registers are the parameters to the system call is handled.
Please don't top post :)
Regarding passing the parameters when it is more than number of
registers used in x86 32 bit, AFAIK it's using EDX to contain the
address of user space memory that contains the data, later it will be
copied to kernel stack IIRC.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2011-09-08 4:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALJfu6OcCd7vdcEG+=PYAY2MrKyqHw7p5O2KNN7s0s7pxO5R+w@mail.gmail.com>
2011-09-07 12:09 ` Doubt regarding asmlinkage rohan puri
2011-09-08 2:42 ` Mulyadi Santosa
2011-09-08 3:40 ` rohan puri
2011-09-08 4:20 ` Mulyadi Santosa [this message]
2011-09-08 5:13 ` rohan puri
2011-09-08 7:17 ` Pei Lin
2011-09-08 9:19 ` rohan puri
2011-09-08 11:58 ` Pei Lin
2011-09-08 12:09 ` rohan puri
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=CAGdaadby2A232qrKJaUj3euSAp5HdNPe-4eXSqEArxW9HGisSA@mail.gmail.com \
--to=mulyadi.santosa@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 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.