All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>,
	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: Sat, 18 Apr 2009 14:38:15 +0200	[thread overview]
Message-ID: <20090418123815.GA21240@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0904152018070.3560@digraph.polyomino.org.uk>

On Wed, Apr 15, 2009 at 08:19:33PM +0000, Joseph S. Myers wrote:

> >  Here is code to implement the getcontext API for MIPS.  This glibc patch 
> > is sent to the linux-mips mailing list, because it makes use of an 
> > internal syscall which has not been designated as a part of the public 
> > ABI.  I am writing to request this syscall to become fixed as a part of 
> > the ABI or to seek for an alternative.  See below for the rationale.
> 
> Was there any conclusion about whether the assumptions this patch makes 
> about the kernel are OK (and so it can go in) or not?

I've probably not spelled it out clearly enough in an earlier email on
this topic but yes, I think it's ok.  In all reality the stackframe has
de facto become a part of the ABI that needs to be kept stable.

  Ralf

  parent reply	other threads:[~2009-04-18 12: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
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 [this message]
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=20090418123815.GA21240@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@codesourcery.com \
    --cc=macro@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.