From: Paul Durrant <Paul.Durrant@citrix.com>
To: Anthony Perard <anthony.perard@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Qemu-devel] [PATCH] xen: handle inbound migration of VMs without ioreq server pages
Date: Tue, 9 Aug 2016 15:23:05 +0000 [thread overview]
Message-ID: <339fd6631cba40518264719ba8cf2018@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20160809151912.GC1835@perard.uk.xensource.com>
> -----Original Message-----
> From: Anthony PERARD [mailto:anthony.perard@citrix.com]
> Sent: 09 August 2016 16:19
> To: Paul Durrant
> Cc: xen-devel@lists.xenproject.org; qemu-devel@nongnu.org; Stefano
> Stabellini
> Subject: Re: [PATCH] xen: handle inbound migration of VMs without ioreq
> server pages
>
> On Mon, Aug 01, 2016 at 10:16:25AM +0100, Paul Durrant wrote:
> > VMs created on older versions on Xen will not have been provisioned with
> > pages to support creation of non-default ioreq servers. In this case
> > the ioreq server API is not supported and QEMU's only option is to fall
> > back to using the default ioreq server pages as it did prior to
> > commit 3996e85c ("Xen: Use the ioreq-server API when available").
> >
> > This patch therefore changes the code in xen_common.h to stop
> considering
> > a failure of xc_hvm_create_ioreq_server() as a hard failure but simply
> > as an indication that the guest is too old to support the ioreq server
> > API. Instead a boolean is set to cause reversion to old behaviour such
> > that the default ioreq server is then used.
> >
> > Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> > Cc: Stefano Stabellini <sstabellini@kernel.org>
> > Cc: Anthony Perard <anthony.perard@citrix.com>
>
> There are just two lines too long:
>
> WARNING: line over 80 characters
> #31: FILE: include/hw/xen/xen_common.h:110:
> +static inline int xen_get_default_ioreq_server_info(xc_interface *xc,
> domid_t dom,
>
> WARNING: line over 80 characters
> #34: FILE: include/hw/xen/xen_common.h:113:
> + evtchn_port_t *bufioreq_evtchn)
>
> With that fixed: Acked-by: Anthony PERARD <anthony.perard@citrix.com>
>
> Thanks,
>
Ok, I'll post v2 with those fixes and your ack. Thanks,
Paul
> --
> Anthony PERARD
next prev parent reply other threads:[~2016-08-09 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 9:16 [Qemu-devel] [PATCH] xen: handle inbound migration of VMs without ioreq server pages Paul Durrant
2016-08-01 9:35 ` Paul Durrant
2016-08-09 15:19 ` Anthony PERARD
2016-08-09 15:23 ` Paul Durrant [this message]
2016-08-11 20:07 ` Stefano Stabellini
2016-08-12 8:55 ` Paul Durrant
2016-08-12 22:09 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=339fd6631cba40518264719ba8cf2018@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).