|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/
>This is probably because vmx_vmexit_handler() takes its regs
>argument 'by
>value'. I expect the compiler has therefore decided it can
>optimise away
>some writes to that argument because the result of the write
>is not used
>inside vmx_vmexit_handler and it assumes the caller will discard the
>argument on return. Hence why this went away with a debug build -- we
>optimise less aggressively.
>
>Either the writeback needs to happen explicitly via
>guest_cpu_user_regs()-returned pointer. Or, more simply, we change the
>vmx_vmexit_handler interface. It'll have negligible cost to
>pass a pointer.
>
Pretty clear and reasonable to me :-)
Thanks
-Xin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616,
Li, Xin B <=
|
|
|
|
|