| To: | Ulrich Drepper <drepper@redhat.com> |
|---|---|
| Subject: | Re: thread-ready ABIs |
| From: | "H . J . Lu" <hjl@lucon.org> |
| Date: | Fri, 18 Jan 2002 11:08:44 -0800 |
| Cc: | GNU libc hacker <libc-hacker@sources.redhat.com>, linux-mips@oss.sgi.com |
| In-reply-to: | <m3elkn4ikq.fsf@myware.mynet>; from drepper@redhat.com on Fri, Jan 18, 2002 at 10:31:17AM -0800 |
| References: | <m3elkoa5dw.fsf@myware.mynet> <20020118101908.C23887@lucon.org> <m3elkn4ikq.fsf@myware.mynet> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Fri, Jan 18, 2002 at 10:31:17AM -0800, Ulrich Drepper wrote: > "H . J . Lu" <hjl@lucon.org> writes: > > > I don't see there are any registers we can use without breaking ABI. > > On the other hand, can we change the mips kernel to save k0 or k1 for > > user space? > > Are these registers which are readable by normal users but writable > only in ring 0? If yes, this is definitely worthwhile (similar to how I can write to k0/k1. But the value is not perserved by kernel. > x86 works). The only problem will be the MIPS variants which don't > have this register. I bet there are some. I don't think so. k0/k1 is reserved for OS. I don't know if OS can restore it for use space or not. H.J. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: thread-ready ABIs, Ulrich Drepper |
|---|---|
| Next by Date: | Re: thread-ready ABIs, Ulrich Drepper |
| Previous by Thread: | Re: thread-ready ABIs, Ulrich Drepper |
| Next by Thread: | Re: thread-ready ABIs, Ulrich Drepper |
| Indexes: | [Date] [Thread] [Top] [All Lists] |