[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-merge] fs/gs handling



Any reason that fs/gs are specifically handled with mov not movl in
these cases?

 #define deactivate_mm(tsk, mm) \
-       asm("movl %0,%%fs ; movl %0,%%gs": :"r" (0))
+       asm("mov %0,%%fs ; mov %0,%%gs": :"r" (0))

or

+static inline void __prepare_arch_switch(void)
...
+       __asm__ __volatile__ ( "mov %%fs,%0 ; mov %%gs,%1"
+               : "=m" (*(int *)&current->thread.fs),
+                 "=m" (*(int *)&current->thread.gs));
+       __asm__ __volatile__ ( "mov %0,%%fs ; mov %0,%%gs"
+               : : "r" (0) );



_______________________________________________
Xen-merge mailing list
Xen-merge@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-merge


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.