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

Re: [Xen-devel] [PATCH RFC XEN v1 12/14] tools: libxc: implement modify_returncode for ARM.



On Wed, 2015-12-16 at 16:22 +0000, Stefano Stabellini wrote:
> On Wed, 9 Dec 2015, Ian Campbell wrote:
> > Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
> > ---
> > Âtools/libxc/xc_resume.c | 18 ++++++++++++++++++
> > Â1 file changed, 18 insertions(+)
> > 
> > diff --git a/tools/libxc/xc_resume.c b/tools/libxc/xc_resume.c
> > index 87d4324..fa16c3e 100644
> > --- a/tools/libxc/xc_resume.c
> > +++ b/tools/libxc/xc_resume.c
> > @@ -81,6 +81,24 @@ static int modify_returncode(xc_interface *xch,
> > uint32_t domid)
> > ÂÂÂÂÂreturn 0;
> > Â}
> > Â
> > +#elif defined (__arm__) || defined(__aarch64__)
> > +
> > +static int modify_returncode(xc_interface *xch, uint32_t domid)
> > +{
> > +ÂÂÂÂvcpu_guest_context_any_t ctxt;
> > +ÂÂÂÂint rc;
> 
> 
> Should we call xc_domain_getinfo and check for info.shutdown_reason !=
> SHUTDOWN_suspend, like x86 does?

Yes absolutely, I'd missed that aspect and thought x86 was only looking for
HVM vs PV.

Actually, I bet I can refactor a bunch of this into common code with only a
small arch specific core.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

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