Xen devel - Sep 2005 - [PATCH][VT] Enable VMXAssist to bring up AP of SMP VMX guest

With this patch, we can enable VMXAssist to bring up APs of SMP VMX
guest.
On entry to VMXAssist:
1) %edx is the processor number, i.e. vcpu id, and for BSP it''s 0.
2) %ebx is the vector number from SIPI.
Also removed some ugly tailing space.

Signed-off-by: Xin Li <xin.b.li@intel.com>
Signed-off-by: Jun Nakajima  <jun.nakajima@intel.com>


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

On 28 Sep 2005, at 04:08, Li, Xin B wrote:
> With this patch, we can enable VMXAssist to bring up APs of SMP VMX
> guest.
> On entry to VMXAssist:
> 1) %edx is the processor number, i.e. vcpu id, and for BSP it''s 0.
> 2) %ebx is the vector number from SIPI.
> Also removed some ugly tailing space.
This looks fine for SMP bootstrap, but will current vmxassist support 
multiple CPUs concurrently in vmxassisted real mode? I wonder if a lot 
of global state needs to be made per-cpu to support that.

  -- Keir


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

>> With this patch, we can enable VMXAssist to bring up APs of SMP VMX
>> guest.
>> On entry to VMXAssist:
>> 1) %edx is the processor number, i.e. vcpu id, and for BSP
it''s 0.
>> 2) %ebx is the vector number from SIPI.
>> Also removed some ugly tailing space.
>
>This looks fine for SMP bootstrap, but will current vmxassist support 
>multiple CPUs concurrently in vmxassisted real mode? I wonder if a lot 
>of global state needs to be made per-cpu to support that.
>
For short term goal, it should be OK to let APs go to VMXAssist one by
one since BSP boots them one by one.
And for long term goal, you are thinking what we want to do, :-)
-Xin

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