From: Paul Durrant <Paul.Durrant@citrix.com>
To: Igor Druzhinin <igor.druzhinin@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Igor Druzhinin <igor.druzhinin@citrix.com>,
"sstabellini@kernel.org" <sstabellini@kernel.org>,
"mst@redhat.com" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] xen: cleanup IOREQ server on exit
Date: Tue, 30 Jul 2019 08:34:57 +0000 [thread overview]
Message-ID: <709c0bad95d8471e8c821fceb83a9948@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <1564428563-1006-1-git-send-email-igor.druzhinin@citrix.com>
> -----Original Message-----
> From: Igor Druzhinin <igor.druzhinin@citrix.com>
> Sent: 29 July 2019 20:29
> To: xen-devel@lists.xenproject.org; qemu-devel@nongnu.org
> Cc: sstabellini@kernel.org; Anthony Perard <anthony.perard@citrix.com>; Paul Durrant
> <Paul.Durrant@citrix.com>; mst@redhat.com; Igor Druzhinin <igor.druzhinin@citrix.com>
> Subject: [PATCH] xen: cleanup IOREQ server on exit
>
> Device model is supposed to destroy IOREQ server for itself.
>
> Signed-off-by: Igor Druzhinin <igor.druzhinin@citrix.com>
Acked-by: Paul Durrant <paul.durrant@citrix.com>
> ---
> hw/i386/xen/xen-hvm.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/hw/i386/xen/xen-hvm.c b/hw/i386/xen/xen-hvm.c
> index e8e79e0..30a5948 100644
> --- a/hw/i386/xen/xen-hvm.c
> +++ b/hw/i386/xen/xen-hvm.c
> @@ -1242,6 +1242,8 @@ static void xen_exit_notifier(Notifier *n, void *data)
> {
> XenIOState *state = container_of(n, XenIOState, exit);
>
> + xen_destroy_ioreq_server(xen_domid, state->ioservid);
> +
> xenevtchn_close(state->xce_handle);
> xs_daemon_close(state->xenstore);
> }
> --
> 2.7.4
prev parent reply other threads:[~2019-07-30 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 19:29 [Qemu-devel] [PATCH] xen: cleanup IOREQ server on exit Igor Druzhinin
2019-07-30 8:34 ` Paul Durrant [this message]
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=709c0bad95d8471e8c821fceb83a9948@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=igor.druzhinin@citrix.com \
--cc=mst@redhat.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).