linux-kernel - Re: Various x86 syscall mechanisms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <486823CB.8050603@tmr.com>
Date:	Sun, 29 Jun 2008 20:07:39 -0400
From:	Bill Davidsen <davidsen@....com>
To:	Roland McGrath <roland@...hat.com>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Various x86 syscall mechanisms

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@....com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/