<br><br><div class="gmail_quote">On Thu, Sep 8, 2011 at 9:50 AM, Mulyadi Santosa <span dir="ltr"><<a href="mailto:mulyadi.santosa@gmail.com">mulyadi.santosa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi :)<br>
<div class="im"><br>
On Thu, Sep 8, 2011 at 10:40, rohan puri <<a href="mailto:rohan.puri15@gmail.com">rohan.puri15@gmail.com</a>> wrote:<br>
> Hi Mulyadi,<br>
><br>
> Thanks for the response. I do agree with the issue concerning the no.of<br>
> registers available are less for 32 bit to that of 64 bit.<br>
><br>
> But even in this case if parameters are more than the no of register for 32<br>
> bit, then also before executing int 80h interrupt it stores the parameters<br>
> in the register and after that system call dispatcher puts them on the<br>
> kernel stack of that process. So, how the case where more than no of<br>
> registers are the parameters to the system call is handled.<br>
<br>
<br>
</div>Please don't top post :)<br>
<br>
Regarding passing the parameters when it is more than number of<br>
registers used in x86 32 bit, AFAIK it's using EDX to contain the<br>
address of user space memory that contains the data, later it will be<br>
copied to kernel stack IIRC.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">regards,<br>
<br>
Mulyadi Santosa<br>
Freelance Linux trainer and consultant<br>
<br>
blog: <a href="http://the-hydra.blogspot.com" target="_blank">the-hydra.blogspot.com</a><br>
training: <a href="http://mulyaditraining.blogspot.com" target="_blank">mulyaditraining.blogspot.com</a><br>
</div></div></blockquote></div><br>Sorry for top posting. :)<br><br>Got it now. Thanks.<br><br>Regards,<br>Rohan.<br>