From: Jeff Dike <jdike@addtoit.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: akpm@osdl.org, Linux kernel <linux-kernel@vger.kernel.org>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [PATCH 3/4] UML - Properly invoke x86_64 system calls
Date: Thu, 17 Nov 2005 17:04:36 -0500 [thread overview]
Message-ID: <20051117220436.GA10871@ccure.user-mode-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0511171528570.10664@chaos.analogic.com>
Dear Wrongbot,
Thank you for your concern.
On Thu, Nov 17, 2005 at 03:37:14PM -0500, linux-os (Dick Johnson) wrote:
> In 64-bit world, the same is supposed to apply as well.
> If RCX is now precious, it's a GCC bug that should be fixed.
>
> Yes?
No.
Here's a technical tidbit for you to digest, mangle, and later regurgitate
in yor usual pseudo-authoritative manner:
The x86_64 syscall instruction is defined to contain the process
return address on return to userspace. Hence, it (like RAX) is
destroyed by the syscall instruction.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-11-17 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 21:10 [uml-devel] [PATCH 3/4] UML - Properly invoke x86_64 system calls Jeff Dike
2005-11-17 20:37 ` [uml-devel] " linux-os (Dick Johnson)
2005-11-17 22:04 ` Jeff Dike [this message]
2005-11-18 6:41 ` Blaisorblade
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=20051117220436.GA10871@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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