|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH][SVM] HVM fix for SWINT event injection
On 27/7/07 16:31, "Woller, Thomas" <thomas.woller@xxxxxxx> wrote:
> Please apply to xen-unstable.
> Applies cleanly to c/s 15651.
> Signed-off-by Tom Woller <thomas.woller@xxxxxxx>
The right thing to do here is copy the exitintinfo->eventinj only if
eventinj.fields.v==0. And to add a comment that in future the two events
should be 'merged' in the architecturally correct manner (e.g., turned into
#DF in some cases).
At least I *think* this is the right thing to do -- but now I think about
it, is it actually ever okay to copy a SWINT from exitintinfo into eventinj?
At the time the #PF vmexit happens, will EIP have been incremented across
the SWINT instruction? If not, does eventinj of a SWINT correctly cause EIP
to be incremented?
> Note that HVM guests will not boot on AMD-V with xen-staging.hg c/s
> 15652.
> Keir, do you want me to take a look at staging c/s 15652 on AMD-V w/
> HVM?
Yes please!
Thanks,
Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|