This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH] xc_resume: fix modify_returncode when PV guest width

To: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] xc_resume: fix modify_returncode when PV guest width != host width
From: Brendan Cully <brendan@xxxxxxxxx>
Date: Wed, 4 Nov 2009 13:03:24 -0800
Delivery-date: Wed, 04 Nov 2009 13:04:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-08-27)
It seems that xm save -c breaks PV guests when their address width
does not match that of domain 0. It looks to me like modify_returncode
is treating the guest VCPU context as native format, but honestly I
don't quite understand the purpose of vcpu_guest_context_any_t.c.

I suspect I'm missing something obvious about how the compat code is
supposed to work, but at any rate, the attached patch fixes things for

Attachment: modify-returncode-width.patch
Description: Text document

Xen-devel mailing list