All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yonit Halperin <yhalperi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: alevy@redhat.com, qemu-devel@nongnu.org, spice-devel@freedesktop.org
Subject: Re: [Qemu-devel] [PATCH] qxl: send interrupt after migration in case ram->int_pending != 0, RHBZ #732949
Date: Wed, 31 Aug 2011 14:18:01 +0300	[thread overview]
Message-ID: <4E5E1869.2060503@redhat.com> (raw)
In-Reply-To: <4E5E0BB8.4060809@redhat.com>

On 08/31/2011 01:23 PM, Gerd Hoffmann wrote:
> On 08/31/11 10:20, 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. In addition,
>> qxl_send_events ignored further interrupts of the same kind, since
>> ram->int_pending was set. As a result, the guest driver was stacked
>> or very slow (when the waiting for the interrupt was with timeout).
>
>> - if (!running&& qxl->mode == QXL_MODE_NATIVE) {
>> + if (running) {
>> + if (qxl->ram->int_pending) {
>> + /*
>> + * 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);
>> + }
>
> You can call qxl_set_irq unconditionally,
> it checks for int_pending anyway.
>
Hi,
qxl_set_irq doesn't test int_pending, but it will call qemu_set_irq 
with level=0 if !int_pending.
> cheers,
> Gerd
>

  reply	other threads:[~2011-08-31 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31  8:20 [Qemu-devel] [PATCH] qxl: send interrupt after migration in case ram->int_pending != 0, RHBZ #732949 Yonit Halperin
2011-08-31 10:23 ` Gerd Hoffmann
2011-08-31 11:18   ` Yonit Halperin [this message]
2011-08-31 12:12     ` Gerd Hoffmann

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=4E5E1869.2060503@redhat.com \
    --to=yhalperi@redhat.com \
    --cc=alevy@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=spice-devel@freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.