From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Alexander Graf <agraf@suse.de>,
Anthony Liguori <aliguori@us.ibm.com>,
rene@exactcode.de, Glauber Costa <glommer@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH][STABLE] cirrus: Properly re-register cirrus_linear_io_addr on vram unmap
Date: Fri, 29 Jan 2010 14:45:15 -0600 [thread overview]
Message-ID: <4B6348DB.4010500@codemonkey.ws> (raw)
In-Reply-To: <4B62ECE0.9060306@siemens.com>
On 01/29/2010 08:12 AM, Jan Kiszka wrote:
> This fixes CONFIG_FB_CIRRUS for Linux guests and probably much more:
>
> When switching away from linearly mapped vram, we also have to restore
> the I/O handlers for the LFB.
>
> This regression was once introduced by commit 2bec46dc97.
>
> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>
> ---
> hw/cirrus_vga.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/hw/cirrus_vga.c b/hw/cirrus_vga.c
> index 6fe433d..9f61a01 100644
> --- a/hw/cirrus_vga.c
> +++ b/hw/cirrus_vga.c
> @@ -2585,9 +2585,11 @@ static void map_linear_vram(CirrusVGAState *s)
>
> static void unmap_linear_vram(CirrusVGAState *s)
> {
> - if (s->vga.map_addr&& s->vga.lfb_addr&& s->vga.lfb_end)
> + if (s->vga.map_addr&& s->vga.lfb_addr&& s->vga.lfb_end) {
> s->vga.map_addr = s->vga.map_end = 0;
> -
> + cpu_register_physical_memory(s->vga.lfb_addr, s->vga.vram_size,
> + s->cirrus_linear_io_addr);
> + }
> cpu_register_physical_memory(isa_mem_base + 0xa0000, 0x20000,
> s->vga.vga_io_memory);
> }
>
>
>
>
prev parent reply other threads:[~2010-01-29 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 14:12 [Qemu-devel] [PATCH][STABLE] cirrus: Properly re-register cirrus_linear_io_addr on vram unmap Jan Kiszka
2010-01-29 20:45 ` Anthony Liguori [this message]
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=4B6348DB.4010500@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=glommer@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=rene@exactcode.de \
/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).