bitkeeper revision 1.1389.20.1 (42836117f2yEkILParltXJcom3kTeA)

More descriptive 'flags' and 'id' field names for exec_domain/domain
structures seems a good idea after all. At the same time, I've renamed
the flag macros to be a bit neater and more descriptive, and more in
keeping with the style of such definitions in asm/mm.h, for example.
Signed-off-by: Keir Fraser <keir@xensource.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/xen/arch/x86/i387.c b/xen/arch/x86/i387.c
index af54d0af8a..b859e74110 100644
--- a/xen/arch/x86/i387.c
+++ b/xen/arch/x86/i387.c
@@ -18,7 +18,7 @@ void init_fpu(void)
     __asm__ __volatile__ ( "fninit" );
     if ( cpu_has_xmm )
         load_mxcsr(0x1f80);
-    set_bit(EDF_DONEFPUINIT, &current->flags);
+    set_bit(_VCPUF_fpu_initialised, &current->vcpu_flags);
 }
 
 void save_init_fpu(struct exec_domain *tsk)
@@ -28,7 +28,7 @@ void save_init_fpu(struct exec_domain *tsk)
      * This causes us to set the real flag, so we'll need
      * to temporarily clear it while saving f-p state.
      */
-    if ( test_bit(EDF_GUEST_STTS, &tsk->flags) )
+    if ( test_bit(_VCPUF_guest_stts, &tsk->vcpu_flags) )
         clts();
 
     if ( cpu_has_fxsr )
@@ -40,7 +40,7 @@ void save_init_fpu(struct exec_domain *tsk)
             "fnsave %0 ; fwait"
             : "=m" (tsk->arch.guest_context.fpu_ctxt) );
 
-    clear_bit(EDF_USEDFPU, &tsk->flags);
+    clear_bit(_VCPUF_fpu_dirtied, &tsk->vcpu_flags);
     stts();
 }