linux-kernel - 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <485C2875.2050204@goop.org>
Date:	Fri, 20 Jun 2008 15:00:21 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Roland McGrath <roland@...hat.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Various x86 syscall mechanisms

Hi Roland,

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.

Why does 32-on-64 implement 32-bit syscall when native 32-bit doesn't 
seem to?  Or am I overlooking something here?  Does 32-bit also support 
syscall?

Thanks,
    J
--
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/