Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@paralogos.com>
To: Brian Foster <brian.foster@innova-card.com>
Cc: linux-mips@linux-mips.org, David Daney <ddaney@avtrex.com>,
	Thiemo Seufer <ths@networkno.de>,
	Andrew Dyer <adyer@righthandtech.com>
Subject: Re: Adding(?) XI support to MIPS-Linux?
Date: Wed, 18 Jun 2008 11:36:53 +0200	[thread overview]
Message-ID: <4858D735.5020406@paralogos.com> (raw)
In-Reply-To: <200806181042.12911.brian.foster@innova-card.com>

Brian Foster wrote:
>  Whilst thinking about the problem and possible solutions,
>  it occurred to me there could be a defect in the current
>  trampoline:  Suppose there is a signal, either at point A,
>  due to <instr> itself, or at point B, which is caught on
>  this stack, and the user-land signal-handler ‘return’s.
>
>  Doesn't the signal-handler/sigreturn stack-frame overwrite
>  the FP trampoline?   In which case, when the signal-hander
>  returns, more-or-less anything could happen.  (And very
>  unlikely to be what's wanted!)
>   
When I first integrated the FP emulator into the kernel, back in 2.2.x, 
I seem to
recall that someone found this problem and that I came up with a tweak 
to signal
stack setup that protected the FP branch delay slot trampoline.  Maybe 
I'm mistaken,
or maybe the tweak was lost?

          Regards,

          Kevin K.

  reply	other threads:[~2008-06-18  9:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200806091658.10937.brian.foster@innova-card.com>
2008-06-09 15:37 ` Re: Adding(?) XI support to MIPS-Linux? Brian Foster
2008-06-09 19:32   ` Kevin D. Kissell
2008-06-09 20:46     ` Thiemo Seufer
     [not found]       ` <200806101119.06227.brian.foster@innova-card.com>
2008-06-10  9:32         ` Brian Foster
2008-06-10  9:57           ` Thiemo Seufer
2008-06-10 16:21             ` David Daney
2008-06-11 13:16               ` Brian Foster
2008-06-11 18:51                 ` Kevin D. Kissell
2008-06-12 12:03                   ` Brian Foster
2008-06-18  8:42                 ` Brian Foster
2008-06-18  9:36                   ` Kevin D. Kissell [this message]
2008-06-18  9:45                     ` Brian Foster
2008-06-11  9:06     ` Ralf Baechle
2008-06-11  9:35       ` Kevin D. Kissell
     [not found] <200806091050.m59AoUUl014012@smtp02.msg.oleane.net>
2008-06-09 10:55 ` Brian Foster

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=4858D735.5020406@paralogos.com \
    --to=kevink@paralogos.com \
    --cc=adyer@righthandtech.com \
    --cc=brian.foster@innova-card.com \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ths@networkno.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox