qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [RfC PATCH 2/2] vga: make vram size configurable
Date: Thu, 24 May 2012 09:20:45 -0300	[thread overview]
Message-ID: <4FBE279D.1010201@siemens.com> (raw)
In-Reply-To: <1337849095-21444-3-git-send-email-kraxel@redhat.com>

On 2012-05-24 05:44, Gerd Hoffmann wrote:
> Zap the global VGA_RAM_SIZE #define, make the vga ram size configurable
> for standard vga and vmware vga.  cirrus and qxl are left with a fixed
> size (and private VGA_RAM_SIZE #define) for now.
> 
> qxl needs some non-trivial adjustments in the mode list handling deal
> with a runtime-configurable size, which calls for a separate qxl patch.
> 
> cirrus emulates cards which have 2 MB (isa) and 4 MB (pci), so I guess
> it would make sense to use these sizes.  That change would break
> migration though, so I left it fixed at 8 MB size.  Making it
> configurabls is pretty pointless for cirrus as we have to match real
> hardware.

We still have the concept of compat machines. So raise to defaults to
more handy sizes should be feasible, provided we keep the old values for
legacy machines.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

      reply	other threads:[~2012-05-24 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  8:44 [Qemu-devel] [RfC PATCH 0/2] vga: make ram size configurable Gerd Hoffmann
2012-05-24  8:44 ` [Qemu-devel] [RfC PATCH 1/2] vga: raise xres+yres limits Gerd Hoffmann
2012-05-24  8:44 ` [Qemu-devel] [RfC PATCH 2/2] vga: make vram size configurable Gerd Hoffmann
2012-05-24 12:20   ` Jan Kiszka [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=4FBE279D.1010201@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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).