This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |