|To:||Rich Felker <firstname.lastname@example.org>|
|Subject:||Re: Is r25 saved across syscalls?|
|From:||David Daney <email@example.com>|
|Date:||Mon, 10 Sep 2012 11:04:55 -0700|
|Dkim-signature:||v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=EX57iYaZsxkx6zesvcJPdvD8OFOwy8yP9r5YUnzXNQw=; b=Ngi5kcqWdPs7t43yuHUQ9879hKttKcxtx6UBIkYfL3c+mFqhS9TjB9FendH1OrhURD 7iVFt0rWM8o0HIeoHuGoP6grbA5lDKei/QlotSQIVNGgsOrd5gvrdubOMICEezGOGXRb h1Ih4NjsAXJ/H08l9Uxi4jGGc+KCwSrAnsX8Wbx2i6NR2AX5ZDeLWdfR5pHTsvV7QQsL oUxhuMbJSbKR4yLTXn/fGlPk0feaiio+ciZJTDpFi+C2VQxElaBrnGcy6kktru0VgkHx o3mAaEerLbSeJF5aF2jR8HTBRGyt1pzMuR7Hec2zanpRjIkiZynunw4DUtuB1n0Bo8kO 0Osw==|
|List-software:||Ecartis version 1.0.0|
|References:||<20120909193008.GA15157@brightrain.aerifal.cx> <20120910170830.GB24448@linux-mips.org> <20120910172248.GN27715@brightrain.aerifal.cx>|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0|
On 09/10/2012 10:22 AM, Rich Felker wrote:
On Mon, Sep 10, 2012 at 07:08:30PM +0200, Ralf Baechle wrote:On Sun, Sep 09, 2012 at 03:30:08PM -0400, Rich Felker wrote:The kernel syscall entry/exit code seems to always save and restore r25. Is this stable/documented behavior I can rely on? If there's a reason it _needs_ to be preserved, knowing that would help convince me it's safe to assume it will always be done. The intended usage is to be able to make syscalls (where the syscall # is not a constant that could be loaded with lwi) without a stack frame, as in "move $2,$25 ; syscall".The basic design idea is that syscalls use a calling convention similar to subroutine calls. $25 is $t9, so a temp register which is callee saved. So if the kernel is saving $t9 and you've been relying on that, consider yourself lucky - there's not guarantee for that.Is there any documentation of what the kernel does guarantee?
Not really. The glibc souces can be used as the canonical implementation as we cannot break it. glibc assumes $25 is clobbered.
All existing syscall-making code I've seen depends at least on r4-r7 not being clobbered when a signal interrupts a syscall
This is an internal kernel implementation detail. Relying on it in userspace is probably not a good idea.
and sets it up for restart (since the arguments still need to be there when it's restarted), and seems to also depend on r4-r6 not being clobbered when the syscall successfully returns (since they're not listed in the clobber list, e.g. in uClibc's inline syscall asm).
Some versions of uClibc's inline syscall asm are buggy. So they cannot be used as an indication of what is supported.
These are requirements beyond the normal function call convention (which does not require the callee preserve the values of r4-r7).
I would assume these are clobbered (from glibc sources ports/sysdeps/unix/sysv/linux/mips/mips64/n64/sysdep.h):
"$1", "$3", "$10", "$11", "$12", "$13", "$14", "$15", "$24", "$25", "hi", "lo"
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH v2 0/3] MIPS: JZ4740: Move PWM driver to PWM framework, Thierry Reding|
|Next by Date:||Re: Is r25 saved across syscalls?, Rich Felker|
|Previous by Thread:||Re: Is r25 saved across syscalls?, Rich Felker|
|Next by Thread:||Re: Is r25 saved across syscalls?, Rich Felker|
|Indexes:||[Date] [Thread] [Top] [All Lists]|