Actually don't have to.....whatever u read, is always guaranteed to be those stuff that u WRITE, not what another process has WRITE. This is because, ANY WRITE, is always guaranteed to be reset to a clean set of registers when the writer process is switch out of context. Therefore, for efficient processing, there is only ONE cleaning up. And one initialization as well. (ie, since the trigger flag is set for this particular WRITER process, upon switching IN, its set of FPU registers will be initialized to what it has written in the past.....and for switching IN context of any other process, nothing needs to be done, as it has never write to FPU before, and therefore the FPU is guaranteed to be clean. Again u may ask WHY? Puzzled it out.....) On Tue, Feb 26, 2008 at 2:00 PM, Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx> wrote: > Hello... > > Hm, i think lazy FPU also implies that read will switch the related > registers to current process's context. if not, well, that would be a > security hole... > > regards, > > Mulyadi. > -- Peter Teoh HP: 96809281 -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
