qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yonit Halperin <yhalperi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qxl: don't render stuff when the vm is stopped.
Date: Wed, 15 Feb 2012 15:59:47 +0200	[thread overview]
Message-ID: <4F3BBA53.5050305@redhat.com> (raw)
In-Reply-To: <4F3BB4F7.3030906@redhat.com>

On 02/15/2012 03:36 PM, Gerd Hoffmann wrote:
> On 02/15/12 14:22, Yonit Halperin wrote:
>> Hi,
>> On 02/15/2012 03:11 PM, Gerd Hoffmann wrote:
>>> This patch fixes the local qxl renderer to not kick spice-server in case
>>> the vm is stopped.  First it is pointless because we render evevything
>>> when the vm is stopped.  Thus there is nothing to render anyway because
>>> a stopped guest can hardly queue more commands.
>> hmm...When the vm is stopped we render only commands that we already
>> read. We don't do more reading from the command ring.
>
> Ah, ok.
>
>> So there may be
>> other pending commands that were not rendered. That is why I
>> suggested allowing rendering when the vm is stopped. But
>> not allowing it during loading the vm during migration.
>
> I'd prefer to keep things simple: let the spice worker run when the
> guest runs, no exceptions.
>
> We may leave some unrendered commands in the ring then.  Ok.  Is that a
> problem for some reason?  Note that the guest may have more commands
> queued which spice-server simply doesn't see yet due to the ring being
> full.  If we stop the guest the wrong moment we can end up with a
> half-done screen update operation no matter what.

Ok. Then ack after correcting the patch comment.

Thanks,
Yonit.
>
> cheers,
>    Gerd
>

  reply	other threads:[~2012-02-15 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15 13:11 [Qemu-devel] [PATCH] qxl: don't render stuff when the vm is stopped Gerd Hoffmann
2012-02-15 13:22 ` Yonit Halperin
2012-02-15 13:36   ` Gerd Hoffmann
2012-02-15 13:59     ` Yonit Halperin [this message]
2012-02-15 13:59 ` Alon Levy

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=4F3BBA53.5050305@redhat.com \
    --to=yhalperi@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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).