From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yonit Halperin <yhalperi@redhat.com>
Cc: alevy@redhat.com, qemu-devel@nongnu.org,
spice-devel@freedesktop.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/2] qxl: send interrupt after migration in case ram->int_pending != 0, RHBZ #732949
Date: Thu, 1 Sep 2011 22:36:24 +0300 [thread overview]
Message-ID: <20110901193623.GN10989@redhat.com> (raw)
In-Reply-To: <1314794254-11624-1-git-send-email-yhalperi@redhat.com>
On Wed, Aug 31, 2011 at 03:37:33PM +0300, Yonit Halperin wrote:
> if qxl_send_events was called from spice server context, and then
> migration had completed before a call to pipe_read, the target
> guest qxl driver didn't get the interrupt.
This is a general issue with interrupt migration, and PCI core has code
to handle this, migrating interrupts. So rather than work around this
in qxl I'd like us to first understand whether there really exists such
a problem, since if yes it would affect other devices.
Could you help with that please?
> In addition,
> qxl_send_events ignored further interrupts of the same kind, since
> ram->int_pending was set.
Maybe this is the only issue?
A way to check would be to call
uint32_t pending = le32_to_cpu(d->ram->int_pending);
uint32_t mask = le32_to_cpu(d->ram->int_mask);
int level = !!(pending & mask);
qxl_ring_set_dirty(d);
instead of qxl_set_irq, and see if that is enough.
Note: I don't object to reusing qxl_set_irq in
production, just let us make sure we don't hide bugs.
> As a result, the guest driver was stacked
> or very slow (when the waiting for the interrupt was with timeout).
You need to sign off :)
> ---
> hw/qxl.c | 9 +++++++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/hw/qxl.c b/hw/qxl.c
> index b34bccf..c7edc60 100644
> --- a/hw/qxl.c
> +++ b/hw/qxl.c
> @@ -1362,7 +1362,6 @@ static void pipe_read(void *opaque)
> qxl_set_irq(d);
> }
>
> -/* called from spice server thread context only */
> static void qxl_send_events(PCIQXLDevice *d, uint32_t events)
> {
> uint32_t old_pending;
> @@ -1463,7 +1462,13 @@ static void qxl_vm_change_state_handler(void *opaque, int running, int reason)
> PCIQXLDevice *qxl = opaque;
> qemu_spice_vm_change_state_handler(&qxl->ssd, running, reason);
>
> - if (!running && qxl->mode == QXL_MODE_NATIVE) {
> + if (running) {
> + /*
> + * if qxl_send_events was called from spice server context before
> + * migration ended, qxl_set_irq for these events might not have been called
> + */
> + qxl_set_irq(qxl);
> + } else if (qxl->mode == QXL_MODE_NATIVE) {
> /* dirty all vram (which holds surfaces) and devram (primary surface)
> * to make sure they are saved */
> /* FIXME #1: should go out during "live" stage */
> --
> 1.7.4.4
>
next prev parent reply other threads:[~2011-09-01 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 12:37 [Qemu-devel] [PATCH v2 1/2] qxl: send interrupt after migration in case ram->int_pending != 0, RHBZ #732949 Yonit Halperin
2011-08-31 12:37 ` [Qemu-devel] [PATCH v2 2/2] qxl: s/qxl_set_irq/qxl_update_irq/ Yonit Halperin
2011-08-31 12:42 ` [Qemu-devel] [PATCH v2 1/2] qxl: send interrupt after migration in case ram->int_pending != 0, RHBZ #732949 Gerd Hoffmann
2011-09-01 19:36 ` Michael S. Tsirkin [this message]
2011-09-04 5:38 ` Yonit Halperin
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=20110901193623.GN10989@redhat.com \
--to=mst@redhat.com \
--cc=alevy@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@freedesktop.org \
--cc=yhalperi@redhat.com \
/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).