Your first chunk is not clear as to where it applies. Maybe you are using a different code base. The second chunck is not necessary. Although the FPU values in thread struct for the new thread are stale, the new program cannot assume the fpu register values and cannot use them without initialization anyway. I don't see such a code in x86's code. Current call to start_thread() is ok with or without this change. I am afraid future use of start_thread() may give undesired effect after we make this change. As for the new fpu context switch code, I wrote a experiemental patch after much discussion with Ralf and Kevin. It is at http://linux.junsun.net/patches/oss.sgi.com/experimental/020304-half-fpu-context-switch I also did some performance study of this patch. Did not get much feedbacks when I asked last time. :-( Jun Carsten Langgaard wrote: > I believe this is the patch that solve the problem. > The lazy fpu stuff has cause so many problems, that we have decided (together > with Ralf) to get rid of it, and do the FPU context save and restore a little bit > differently. > We now have a solution here locally and we are testing it at the moment. > > /Carsten > > > Index: arch/mips/kernel/traps.c > =================================================================== > RCS file: /cvs/linux/arch/mips/kernel/traps.c,v > retrieving revision 1.99.2.14 > diff -u -r1.99.2.14 traps.c > --- arch/mips/kernel/traps.c 2002/05/28 06:33:13 1.99.2.14 > +++ arch/mips/kernel/traps.c 2002/06/18 07:53:47 > + { > + __enable_fpu(); > save_fp(last_task_used_math); > + /* last_task_used_math loose fpu */ > + ((struct pt_regs *)(__KSTK_TOS(last_task_used_math) - > + sizeof(struct pt_regs)))-> > + cp0_status &= ~ST0_CU1; > + } > > Index: include/asm-mips/processor.h > =================================================================== > RCS file: /cvs/linux/include/asm-mips/processor.h,v > retrieving revision 1.43.2.2 > diff -u -r1.43.2.2 processor.h > --- include/asm-mips/processor.h 2002/05/28 06:11:56 1.43.2.2 > +++ include/asm-mips/processor.h 2002/06/18 07:56:58 > @@ -215,6 +215,7 @@ > regs->cp0_epc = new_pc; \ > regs->regs[29] = new_sp; \ > current->thread.current_ds = USER_DS; \ > + current->used_math = 0; \ > } while (0) > > unsigned long get_wchan(struct task_struct *p); > > > > Jun Sun wrote: > > >>Carsten Langgaard wrote: >> >> >>>This is one of the bugs, among others, we have fixed. >>>I'm not sure, if Ralf have integrated the patches we send him yet. >>> >>> >>Carsten, >> >>Do you remember the cause and the fix? It appears to me the first ctc1 >>instruction should trap into kernel and mark current process as fpu owner, and >>should not cause fcr31 corruption. >> >>Or somehow the ctc1 does not trap into kernel? >> >>Jun >> >> >>>/Carsten >>> >>>Louis Hamilton wrote: >>> >>> >>> >>>>We have a customer here testing a 2.4.16 mips kernel on an embedded >>>>Linux RM7000/SR71000 based system who has written a test that they >>>>believe has uncovered a bug in Linux. The FPU control register appears >>>>to not get saved and restored. I've reproduced the problem described >>>>below and find the results consistent with their description. The >>>>problem occurs on both the RM7000 and SR71000 cpus. >>>> >>>>It looks like save_fp_context and restore_fp_context are not being >>>>called since the kernel save-restore logic thinks the process is not >>>>using floating point math. If you do some fp math before calling the >>>>test routine below, it seems to works fine. >>>> >>>>Is this a known caveat? A true bug? Or a contorted corner case >>>>unlikely to be seen under typical end-user usage (see customer's >>>>last paragraph :-) ? If true bug, recommended remedy? >>>> >>>>TIA, >>>>Louis >>>> >>>>Louis Hamilton >>>>hamilton@redhat.com >>>> >>>>------ customer reports the following: --------- >>>>We found a bug in Linux. A ^C (control-C) typed into a shell (or a >>>>running program, it doesn't matter), causes the FCR (floating-point >>>>control register) to be corrupted in another, unrelated process. This >>>>is repeatable behavior. >>>> >>>>This can be reproduced with the following short assembly language >>>>program that loops forever, waiting for the FCR to change. >>>> >>>> .align 2 >>>> .globl mips_float_debug_loop >>>>mips_float_debug_loop: >>>> li $9, 0xF000F02F >>>> ctc1 $9, $31 # set FCR to some non-zero value >>>> nop >>>>1: cfc1 $8, $31 # get FCR >>>> beq $8, $9, 1b # spin, waiting for FCR to change >>>> nop >>>> or $2, $0, $8 >>>> jr $31 >>>> nop >>>> >>>>You can call this function from a short C program and the return value >>>>is the (corrupted) FCR, which turns out to alwyas be: 0x00000002. >>>> >>>>Run the above loop in one window (connected to the board using telnet) >>>>and then in another window (connected to the same board) type ^C. >>>> >>>>I'm surprised this bug hasn't been encountered by other MIPS vendors. >>>> >>>><end> >>>> >>>-- >>>_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com >>>|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527 >>>| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555 >>> TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556 >>> Denmark http://www.mips.com >>> >>> >>> >>> >>> > > -- > _ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com > |\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527 > | \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555 > TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556 > Denmark http://www.mips.com > > > >
