On Mon, Mar 09, 2015 at 08:27:43PM +0100, Jan Kiszka wrote: > For a very long time (since 2b3d2a20), the path handling a vmmcall > instruction of the guest on an Intel host only applied the patch but no > longer handled the hypercall. The reverse case, vmcall on AMD hosts, is > fine. As both em_vmcall and em_vmmcall actually have to do the same, we > can fix the issue by consolidating both into the same handler. > > Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> Applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
