From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] qxl: change rom so that 4096 < size < 8192
Date: Thu, 13 Dec 2012 13:05:48 +0100 [thread overview]
Message-ID: <50C9C49C.10400@redhat.com> (raw)
In-Reply-To: <1355398603-22186-2-git-send-email-alevy@redhat.com>
On 12/13/12 12:36, Alon Levy wrote:
> This is a simpler solution to 869981, where migration breaks since qxl's
> rom bar size has changed. Instead of ignoring fields in QXLRom, which is what has
> actually changed, we remove some of the modes, a mechanism already
> accounted for by the guest. To reach exactly two pages and not one, we
> remove two out of four orientations, the remaining are normal and right
> turn (chosen arbitrarily). Leaving only normal would result in a single
> page which would also break migration.
>
> Added assertions to ensure changes in spice-protocol in the future
> causing increase or decrease of page size will result in failure at
> startup (could do this compile time also but not sure how).
The assertions are not in the patch.
> #define QXL_MODE_EX(x_res, y_res) \
> QXL_MODE_16_32(x_res, y_res, 0), \
> - QXL_MODE_16_32(y_res, x_res, 1), \
> - QXL_MODE_16_32(x_res, y_res, 2), \
> - QXL_MODE_16_32(y_res, x_res, 3)
> + QXL_MODE_16_32(x_res, y_res, 1)
Why do you leave orientation = 1 in? Just to keep the size above 4K?
Shouldn't we just hardcode the rom size to 8k instead? Then assert that
everything fits into 8k? Or even better add a compile time check?
While being at it it might be a good idea to move the mode table to a
fixed, large enougth offset (say 0x4096), so it doesn't move around
again in case we extend QXLRom one more time.
cheers,
Gerd
next prev parent reply other threads:[~2012-12-13 12:06 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
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 [this message]
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=50C9C49C.10400@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).