[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] x86_emulate: properly do IP updates and other side effects on success
Il 07/08/2014 16:38, Jan Beulich ha scritto: On 07.08.14 at 15:24, <fabio.fantoni@xxxxxxx> wrote:Il 07/08/2014 10:30, Jan Beulich ha scritto:The two MMX/SSE/AVX code blocks failed to update IP properly, and these as well as get_reg_refix(), which "manually" updated IP so far, failed to do the TF and RF processing needed at the end of successfully emulated instructions. Reported-by: Andrei LUTAS <vlutas@xxxxxxxxxxxxxxx> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Tested-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>Thanks for the patch, I tested it to see if solves also qxl on linux domUs problem but with this patch the domU crashes and I cannot get a backtrace or specific errors.Are you saying that this is different from without that patch? Considering the lack of EIP update, the emulation of the instructions in question can't have done much good before, and - just like the reporters of the issue saw - the guest should have hung. Jan Before this patch the domU's org was always 100% cpu, spice show black screen and is possible a xl shutdown, after at xorg start, show domU's mouse in center in spice and domU crash. I'm unable to debug it, can you tell me what I must do to debug it and give you all possibile information? This is the exact git I used for my tests: https://github.com/Fantu/Xen/tree/rebase/m2r-stagingContains some libxl patch about spice used for a long time and with only qxl problem on linux domUs (with windows domUs is working good since your patch of long time ago about similar istructions and same performance as kvm after one or more patches in xen-unstable that I not know exactly and is still working also with this patch). Thanks for any reply and sorry for my bad english. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |