All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Brian Foster <brian.foster@innova-card.com>,
	"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>
Subject: Re: [PATCH, RFC] MIPS: Implement the getcontext API
Date: Wed, 04 Mar 2009 08:36:45 -0800	[thread overview]
Message-ID: <49AEAE1D.5030205@caviumnetworks.com> (raw)
In-Reply-To: <20090304121732.GA28381@caradoc.them.org>

Daniel Jacobowitz wrote:
> On Wed, Mar 04, 2009 at 09:19:28AM +0100, Brian Foster wrote:
>>  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.
> 
> That won't quite retain the ABI: you need to make sure everyone
> locates it by using the stack pointer instead of the return pc.
> Fortunately, GCC uses the return PC only for instruction matching
> today.  I have a vague memory it used to use the stack pointer but
> this was more reliable.

That is correct.  Due to various errata the trampoline cannot always be 
at a fixed offset to the signal context bits.  So we had to use the 
return PC as you indicate.

David Daney

  reply	other threads:[~2009-03-04 16:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01  0:12 [PATCH, RFC] MIPS: Implement the getcontext API Maciej W. Rozycki
2009-03-03 16:56 ` David Daney
2009-03-04  8:19   ` Brian Foster
2009-03-04 12:17     ` Daniel Jacobowitz
2009-03-04 16:36       ` David Daney [this message]
2009-04-02 13:29         ` Ralf Baechle
2009-04-02 20:06           ` Daniel Jacobowitz
2009-03-04 15:44     ` Ralf Baechle
2009-03-04 22:25       ` David VomLehn (dvomlehn)
2009-03-04 22:25         ` David VomLehn (dvomlehn)
2009-03-04 22:34         ` David Daney
2009-03-05  7:58           ` MIPS RI/XI & trampolines [was:- [PATCH, RFC] MIPS: Implement the getcontext API ] Brian Foster
2009-03-05 17:01             ` David Daney
2009-04-02 13:38         ` [PATCH, RFC] MIPS: Implement the getcontext API Ralf Baechle
2009-04-16  3:46           ` Markus Gothe
2009-04-17  5:53             ` Ralf Baechle
2009-03-05 15:34   ` Maciej W. Rozycki
2009-03-05 16:58     ` David Daney
2009-03-05 18:23       ` David VomLehn (dvomlehn)
2009-03-05 18:23         ` David VomLehn (dvomlehn)
2009-03-05 21:36         ` Ralf Baechle
2009-03-05 21:39           ` Roland McGrath
2009-03-05 21:53           ` Joseph S. Myers
2009-03-05 22:08             ` David VomLehn (dvomlehn)
2009-03-05 22:08               ` David VomLehn (dvomlehn)
2009-04-02 13:19 ` Ralf Baechle
2009-04-15 20:19 ` Joseph S. Myers
2009-04-15 21:37   ` David Daney
2009-04-18 12:38   ` Ralf Baechle
2009-04-18 17:32     ` Joseph S. Myers
2009-04-20 19:57       ` Maciej W. Rozycki
2009-04-28 19:17       ` Aurelien Jarno
2009-04-28 19:21         ` Philippe Vachon
2009-04-28 20:19         ` Maciej W. Rozycki
2009-04-28 20:53           ` Aurelien Jarno
2009-04-28 21:47             ` Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2009-04-05 18:57 Graziano Sorbaioli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49AEAE1D.5030205@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=brian.foster@innova-card.com \
    --cc=dan@debian.org \
    --cc=libc-ports@sourceware.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@codesourcery.com \
    --cc=macro@linux-mips.org \
    --cc=ralf@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.