WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-merge

[Xen-merge] fs/gs handling

To: xen-merge@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-merge] fs/gs handling
From: Chris Wright <chrisw@xxxxxxxx>
Date: Thu, 11 Aug 2005 19:41:45 -0700
Delivery-date: Fri, 12 Aug 2005 02:39:53 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-merge-request@lists.xensource.com?subject=help>
List-id: xen-merge <xen-merge.lists.xensource.com>
List-post: <mailto:xen-merge@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-merge-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
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

<Prev in Thread] Current Thread [Next in Thread>