Hello,
> > The proper way to save it is to use kernel_fpu_begin()
>
> Thanks! I will look into it. This is what I was looking for.
>
> I been running this kernel with my copy for three days, and never had
> oops, but I was really worried.
kernel_fpu_begin() is not enough for this purpose as user_*_copy may
cause pagefault and sleep in it. You should know lazy FPU swtich mechanism.
The mechanism will be confued by your your copy routine and may save
broken FPU context or another process may use broken FPU registers.
You should also care about do_page_fault like this:
do_page_fault()
{
if (fault happens in user_*_copy) {
save FPU context on stack;
recover FPU context to the previous state;
}
.........
.........
.........
if (fault happens in user_*_copy) {
recover FPU context from stack;
}
}
> > > > Also I'm pretty sure that using movntq (= forcing destination out of
> > > > cache) is not a good strategy for generic copy_from_user(). It may
> > > > be a win for the copies in write ( user space -> page cache ),
> > >
> > > Yes, that why I included postfetch in the code because movntq does not leave
> > > them in the L2 cache.
> >
> > That looks rather wasteful - first force it out and then trying to get it in
> > again. I have my doubts on it being a good strategy for speed.
>
> It tried both, use just normal mov or movq <-> use movntq + postfetch, and the later
> was much much faster, because postfetch needs to read only every 64 bytes.
>
> I will ckeck kernel_fpu_begin() fisrt and if using fpu register is too much
> overhead than I will remove them.
I guess kernel_fpu_begin() might not be heavy as many processes don't use
fpu registers so much.
Thank you,
Hirokazu Takahashi.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:18 EST