| To: | "Kevin D. Kissell" <kevink@mips.com> |
|---|---|
| Subject: | Re: thread-ready ABIs |
| From: | "H . J . Lu" <hjl@lucon.org> |
| Date: | Fri, 18 Jan 2002 20:11:39 -0800 |
| Cc: | Ulrich Drepper <drepper@redhat.com>, GNU libc hacker <libc-hacker@sources.redhat.com>, linux-mips@oss.sgi.com |
| In-reply-to: | <01b801c1a081$3f6518e0$0deca8c0@Ulysses>; from kevink@mips.com on Sat, Jan 19, 2002 at 01:35:38AM +0100 |
| References: | <m3elkoa5dw.fsf@myware.mynet> <20020118101908.C23887@lucon.org> <01b801c1a081$3f6518e0$0deca8c0@Ulysses> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Sat, Jan 19, 2002 at 01:35:38AM +0100, Kevin D. Kissell wrote: > > It would, in principle, be possible to save/restore k0 > or k1 (but not both) if no other clever solution can be found. > There are other VM OSes that manage to do so for MIPS, > for other outside-the-old-ABI reasons. It does, of course, > add some instructions and some memory traffic to the > low-level exception handling , and we would have to look > at whether we would want to make such a feature standard > or specific to a "thread-ready" kernel build. I like the read-only k0 idea. We just need to make a system call to tell kernel what value to put in k0 before returning to the user space. It shouldn't be too hard to implement. I will try it next week. H.J. |
| Previous by Date: | Re: thread-ready ABIs, Kevin D. Kissell |
|---|---|
| Next by Date: | [PATCH] SR7100 support, Jason Gunthorpe |
| Previous by Thread: | Re: thread-ready ABIs, Kevin D. Kissell |
| Next by Thread: | Re: thread-ready ABIs, Dominic Sweetman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |