And you don't need to keep cr3 in the TSS.
> > Doable I believe but not simple, and there is still the TS issue.
> I finally realized the TS problem is basically unsolvable. There is no
> way to know what the value was before a switch happened.
I believe the TS value can be inferred from the thread flags except
between kernel_fpu_begin() and kernel_fpu_end().
> (BTW some other Free kernel has interesting things in its descriptor
> tables: DPL 1 execute-only code segments, conforming code, expand-down
> data, multiple LDTs etc... It uncovered a bug in my code, too.)
Interesting, but using 3 privilege levels is not very portable, and
you'll need another per process stack.
Multiple LDT, how can this be useful and what are the semantics?
There are enough problems with LDT eating up vmalloc space (I believe
I have a solution to that particular problem).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/