From: Bill Davidsen <davidsen@tmr.com>
To: Roland McGrath <roland@redhat.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Various x86 syscall mechanisms
Date: Sun, 29 Jun 2008 20:07:39 -0400 [thread overview]
Message-ID: <486823CB.8050603@tmr.com> (raw)
In-Reply-To: <20080627204954.166D0154077@magilla.localdomain>
Roland McGrath wrote:
>> As far as I can work out, an x86_32 kernel will use "int 0x80" and
>> "sysenter" for system calls. 64-bit kernel will use just "syscall" for
>> 64-bit processes (though you can use "int 0x80" to access the 32-bit
>> syscall interface from a 64-bit process), but will allow "sysenter",
>> "syscall" or "int 0x80" for 32-on-64 processes.
>
> That is correct, with the caveats below.
>
Thanks for setting this out clearly, I've seen most of it (from Andi, I
think) in bits, and one of the scheduler folk had a comment relevant to
scheduling which I can't find now, but this is both technical and
historical, and thus a nice thing to hand to someone with a related
question.
Well done.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2008-06-30 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 22:00 Various x86 syscall mechanisms Jeremy Fitzhardinge
2008-06-20 23:39 ` Roland McGrath
2008-06-27 21:45 ` Jeremy Fitzhardinge
2008-06-27 21:52 ` Roland McGrath
2008-06-28 5:00 ` Andi Kleen
2008-06-30 0:07 ` Bill Davidsen [this message]
2008-06-21 0:27 ` H. Peter Anvin
2008-06-21 2:00 ` Jeremy Fitzhardinge
2008-06-21 14:02 ` Andi Kleen
2008-06-21 16:51 ` H. Peter Anvin
2008-07-01 12:06 ` Jan Engelhardt
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=486823CB.8050603@tmr.com \
--to=davidsen@tmr.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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