Ingo Molnar wrote:
> for example, your test_fs() code does:
>
> for(i = 0; i < COUNT; i++) {
> asm volatile("push %%fs; mov %1, %%fs; addl $1, %%fs:%0; popl %%fs"
> : "+m" (*offset): "r" (seg) : "memory");
> sync();
> }
>
> that loads (and uses) a single selector value for %fs, and doesnt do any
> mixed use as far as i can see.
I'm not sure what you're getting at. Each loop iteration is analogous
to a user->kernel->user transition with respect to the
save/reload/use/restore pattern on the segment register. In this case,
%fs starts as a null selector, gets reloaded with a non NULL selector,
and then is restored to null. Do you mean some other mixing?
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
