linux-kernel - Re: [PATCH RFC WIP] x86/paravirt: add register-saving thunks to reduce caller register pressure

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090130210625.GD1253@ucw.cz>
Date:	Fri, 30 Jan 2009 22:06:25 +0100
From:	Pavel Machek <pavel@...e.cz>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Zachary Amsden <zach@...are.com>, "H. Peter Anvin" <hpa@...or.com>,
	Ian Campbell <Ian.Campbell@...rix.com>,
	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC WIP] x86/paravirt: add register-saving thunks to
	reduce caller register pressure


> This patch seeks to alleviate this pressure by introducing wrapper
> thunks that will do the register saving/restoring, so that the
> callsite doesn't need to worry about it, but the callee function can
> be conventional compiler-generated code.  In many cases (particularly
> performance-sensitive cases) the callee will be in assembler anyway,
> and need not use the compiler's calling convention.
>
> Standard calling convention is:
> 	 arguments	    return	scratch
> x86-32	 eax edx ecx	    eax		?

esi edi ebp ?

actually standard calling convention is all arguments on stack iirc
but we use regparm=3 for kernel...?

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/