From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qxl: use correct rom size for revision < 4
Date: Wed, 12 Dec 2012 12:46:19 +0100 [thread overview]
Message-ID: <50C86E8B.5020705@redhat.com> (raw)
In-Reply-To: <1354808473-7634-1-git-send-email-alevy@redhat.com>
On 12/06/12 16:41, Alon Levy wrote:
> RHBZ 869981
>
> Before this patch revision < 4 (4 is the default) would result in a wrong
> qxl_rom size of 16384 instead of 8192 when building with
> spice-protocol-0.12, due to the addition of fields in
> the rom for client capabilities and monitors config that were added
> between spice-protocol 0.10 and 0.12.
>
> The solution is a bit involved, since I decided not to change QXLRom
> which is defined externally in spice-protocol. Instead for revision < 4
> we allocate 72 bytes for the QXLRom on the qxl_rom bar (bytes [0,71])
> and make sure no fields out of that range are accessed, via checking of
> the revision and nop-ing.
Ok, I see we tackle two issues here.
Number one is qxl accessing the new fields with revision being < 4.
That needs fixing indeed. But separate patch please.
Number two is breaking migration due to the rom size change. Can't we
just get the rom below 8k again instead? I think we can throw away a
whole bunch of modes. Each mode is four times in the list, for
orientation = { 0, 1, 2, 3 }. orientation is never ever used anywhere,
looks like historic leftover or something planned which was never
actually implemented.
So keeping orientation = 0 only and kick out everything else should give
us plenty of room ...
cheers,
Gerd
next prev parent reply other threads:[~2012-12-12 11:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 15:41 [Qemu-devel] [PATCH] qxl: use correct rom size for revision < 4 Alon Levy
2012-12-12 11:46 ` Gerd Hoffmann [this message]
2012-12-13 10:40 ` Alon Levy
2012-12-13 14:30 ` Yonit Halperin
2012-12-13 14:43 ` Gerd Hoffmann
2012-12-23 20:33 ` Alon Levy
2013-01-03 7:55 ` Gerd Hoffmann
2012-12-13 11:36 ` [Qemu-devel] [PATCH 1/2] qxl: stop using non revision 4 rom fields " Alon Levy
2012-12-13 11:36 ` [Qemu-devel] [PATCH 2/2] qxl: change rom so that 4096 < size < 8192 Alon Levy
2012-12-13 12:05 ` Gerd Hoffmann
2012-12-23 20:31 ` Alon Levy
2013-01-15 13:34 ` Alon Levy
2013-01-15 15:19 ` Gerd Hoffmann
2013-01-16 17:59 ` [Qemu-devel] [PATCH v2 0/2] fix two revision related errors Alon Levy
2013-01-16 17:59 ` [Qemu-devel] [PATCH v2 1/2] qxl: stop using non revision 4 rom fields for revision < 4 Alon Levy
2013-01-16 17:59 ` [Qemu-devel] [PATCH v2 2/2] qxl: change rom size to 8192 Alon Levy
2013-01-17 13:02 ` [Qemu-devel] [PATCH v2 0/2] fix two revision related errors Gerd Hoffmann
2013-01-17 13:28 ` Alon Levy
2013-01-17 13:44 ` Gerd Hoffmann
2013-01-20 16:30 ` Alon Levy
2013-01-21 6:26 ` Gerd Hoffmann
2013-01-21 12:47 ` Alon Levy
2013-01-21 12:48 ` [Qemu-devel] [PATCH v3 1/2] qxl: stop using non revision 4 rom fields for revision < 4 Alon Levy
2013-01-21 12:48 ` [Qemu-devel] [PATCH v3 2/2] qxl: change rom size to 8192 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=50C86E8B.5020705@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@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).