linux-mips
[Top] [All Lists]

Re: [PATCH, RFC] MIPS: Implement the getcontext API

To: David Daney <ddaney@caviumnetworks.com>
Subject: Re: [PATCH, RFC] MIPS: Implement the getcontext API
From: Brian Foster <brian.foster@innova-card.com>
Date: Wed, 4 Mar 2009 09:19:28 +0100
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>, Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org, libc-ports@sourceware.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:from:reply-to:to :subject:date:user-agent:cc:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; bh=lGXEOxqlUvUhIyniZDhZLqw8iFSzkmVqTBczFaoGz9Y=; b=hjZ34u3lS+mRXWTNJEKD+dIpEqBev8IYYwx6gra1BXaI+FEWRPCP8AU2Ej1qHiT7QS fPZt9UKndYK0k0YZra91p2o6pmStOA30oJLnHOTcysemvPJc5derOlEaE08QkKxJTzPe VRw+jnz5wPwr3DaOc3FWgFB0Z+JC8ak/CNXdE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:reply-to:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=yAK5Rqcdjes/4TP4oSbYG9+An2+eyxvmNYTtTwBfxiPwWnV1zhCxGWi41CeB5vGb2g Z5wbDdPmQBBsRf1+1FxmhKeGWb8FmlIHzfHooIhUhLJB7tmO7V/u1bEcUE8XxyKDfhvi KcYa0sNg5qQAl92/B98q+MykzvpcNn6QvgFZk=
In-reply-to: <49AD6139.60209@caviumnetworks.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <alpine.DEB.1.10.0902282326580.4064@tp.orcam.me.uk> <49AD6139.60209@caviumnetworks.com>
Reply-to: Brian Foster <brian.foster@innova-card.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: KMail/1.10.4 (Linux/2.6.27-11-generic; KDE/4.1.4; x86_64; ; )
On Tuesday 03 March 2009 17:56:25 David Daney wrote:
>[ ... ]
> When (and if) we move the sigreturn trampoline to a vdso we should be
> able to maintain the ABI.

 it's more a matter of “when” rather than “if”.
 there is still an intention here to use XI (we
 have SmartMIPS), which requires not using the
 signal (or FP) trampoline on the stack.

 moving the signal trampoline to a vdso (which
 is(? was?) called, maybe misleadingly, ‘vsyscall’,
 on other architectures) is the obvious solution to
 that part of the puzzle.  and yes, it is possible
 to maintain the ABI; the signal trampoline is still
 also put on the stack, and modulo XI, would work if
 used — the trampoline-on-stack is simply not used
 if there is a vdso with the signal trampoline.

cheers!
        -blf-

-- 
“How many surrealists does it take to   | Brian Foster
 change a lightbulb? Three. One calms   | somewhere in south of France
 the warthog, and two fill the bathtub  |   Stop E$$o (ExxonMobil)!
 with brightly-coloured machine tools.” |      http://www.stopesso.com

<Prev in Thread] Current Thread [Next in Thread>