From: Yonit Halperin <yhalperi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, spice-devel@freedesktop.org
Subject: Re: [Qemu-devel] [Spice-devel] [PATCH] qxl: make sure primary surface is saved on migration also in compat mode
Date: Tue, 14 Feb 2012 11:15:30 +0200 [thread overview]
Message-ID: <4F3A2632.6090809@redhat.com> (raw)
In-Reply-To: <4F3A2513.4060105@redhat.com>
On 02/14/2012 11:10 AM, Yonit Halperin wrote:
> On 02/14/2012 10:35 AM, Gerd Hoffmann wrote:
>> On 02/14/12 09:10, Yonit Halperin wrote:
>>> RHBZ #790083
>>>
>>> Signed-off-by: Yonit Halperin<yhalperi@redhat.com>
>>
>> You are doing two things in one patch: (a) fix the compat mode bug,
>> which also matches the patch description, and (b) skip vram when it is
>> unused (in compat mode).
>>
>> I'd love to see (b) done in a different way: simply walk all surfaces
>> and tag them dirty. Will have the same effect for compat mode (no
>> surfaces used -> nothing tagged dirty) and additionally it will (in
>> native mode) only migrate over the vram areas which are actually filled
>> with surfaces.
>>
> I can do it, by retrieving the surfaces addresses from the tracked guest
> commands. However, if we already do it, it would be even better if we
> just dirty only the areas that are actually modified by the update_area
> calls. The problem is that (1) spice-server updates surfaces also
> without request from driver. We can add a cb to the interface or use the
> async_complete cb with a special flag (2) async_complete cb is called
> from spice server context. We can add a pipe for update_area dirty
> events, and make sure that it is handled, before migration moves from
> the live stage.
Giving it another thought, I don't really like it because surfaces are
destroyed with high frequency. So it will be a waste.
So doing it just before migration sounds better.
>
> Yonit.
>> thanks,
>> Gerd
>
> _______________________________________________
> Spice-devel mailing list
> Spice-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel
next prev parent reply other threads:[~2012-02-14 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 8:10 [Qemu-devel] [PATCH] qxl: make sure primary surface is saved on migration also in compat mode Yonit Halperin
2012-02-14 8:35 ` Gerd Hoffmann
2012-02-14 9:10 ` Yonit Halperin
2012-02-14 9:15 ` Yonit Halperin [this message]
2012-02-14 9:24 ` Gerd Hoffmann
2012-02-14 9:33 ` 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=4F3A2632.6090809@redhat.com \
--to=yhalperi@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 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).