[Xen-changelog] [xen master] x86/hvm: don't set the BSP as initialised in hvm_vcpu_initialise

[patchbot@xxxxxxx]

commit 9761bfb9b7582ef50202f3b4e04d658713422c0d
Author:     Roger Pau Monné <roger.pau@xxxxxxxxxx>
AuthorDate: Mon Jan 18 14:52:31 2016 +0100
Commit:     Jan Beulich <jbeulich@xxxxxxxx>
CommitDate: Mon Jan 18 14:52:31 2016 +0100

    x86/hvm: don't set the BSP as initialised in hvm_vcpu_initialise

    The BSP will be marked as initialised after hvm_load_cpu_ctxt has loaded the
    initial state, which is called from the toolstack during domain creation.

    Previous to my HVMlite series HVM guests were started without setting any
    explicit CPU state (in fact we placed that horrible jmp at 0x0, because the
    IP was by default set to 0x0). This is no longer true, and now HVM guests
    require that a proper CPU context is loaded before starting. This change
    helps enforce this policy.

    Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
---
 xen/arch/x86/hvm/hvm.c |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
index a99edc2..f646c1e 100644
--- a/xen/arch/x86/hvm/hvm.c
+++ b/xen/arch/x86/hvm/hvm.c
@@ -2487,10 +2487,6 @@ int hvm_vcpu_initialise(struct vcpu *v)

         /* Init guest TSC to start from zero. */
         hvm_set_guest_tsc(v, 0);
-
-        /* Can start up without SIPI-SIPI or setvcpucontext domctl. */
-        v->is_initialised = 1;
-        clear_bit(_VPF_down, &v->pause_flags);
     }

     return 0;
--
generated by git-patchbot for /home/xen/git/xen.git#master

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog