[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Brendan Cully <brendan@xxxxxxxxx>
Date: Wed, 4 Nov 2009 13:03:24 -0800
Delivery-date: Wed, 04 Nov 2009 13:04:17 -0800
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Mail-followup-to: xen-devel@xxxxxxxxxxxxxxxxxxx

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
me.

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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH] xc_resume: fix modify_returncode when PV guest width != host width
  - From: Keir Fraser

Prev by Date: RE: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation
Next by Date: Re: [Xen-devel] Strange error in domU after dom0 update
Previous by thread: [Xen-devel] inputs on porting network(nic) drivers from Linux to Xen
Next by thread: Re: [Xen-devel] [PATCH] xc_resume: fix modify_returncode when PV guest width != host width
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.