qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: weidong.huang@huawei.com, mst@redhat.com, qemu-devel@nongnu.org,
	arei.gonglei@huawei.com, pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] cirrus_vga: adding sanity check for vram size
Date: Fri, 9 May 2014 13:02:25 +0100	[thread overview]
Message-ID: <20140509120224.GB22335@work-vm> (raw)
In-Reply-To: <1399636479.5213.56.camel@nilsson.home.kraxel.org>

* Gerd Hoffmann (kraxel@redhat.com) wrote:
>   Hi,
> 
> > virt-manager/libvirt seems to default to 9 MByte of Vram for cirrus,
> > so this would break a lot of setups.
> 
> It wouldn't.  libvirt sticks that into the xml, but it doesn't set any
> qemu parameters.  The libvirt parameter actually predates the qemu
> property for setting the size.

Yeuch messy.

> > Looking at datasheets on the web seems to say the chips actually went
> > down to 1 MB or less.
> 
> I have my doubts we emulate that correctly (register telling the guest
> how much memory is actually there etc.).  Also it is pretty much useless
> these days, even the 4MB imply serious constrains when FullHD displays
> are commonplace.  Newer cirrus drivers such as the kernel's drm driver
> are specifically written to qemu's cirrus cards, I have my doubs that
> they are prepared to handle 1MB cirrus cards correctly.
> 
> Bottom line: Allowing less than 4MB is asking for trouble for no good
> reason ;)

OK, so checking for 4MB/8MB/16MB is probably safe, and it also would
have the benefit of shouting if someone fixed libvirt and it started
trying to configure a 9MB version.

Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2014-05-09 12:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 10:21 [Qemu-devel] [PATCH] cirrus_vga: adding sanity check for vram size arei.gonglei
2014-05-09 10:31 ` [Qemu-devel] [PATCH] cirrus_vga: adding sanity check for vram size [checkpatch false positive?] Gerd Hoffmann
2014-05-09 10:40   ` Gonglei (Arei)
2014-05-09 10:54     ` Gerd Hoffmann
2014-05-09 10:59       ` Gonglei (Arei)
2014-05-09 11:53         ` [Qemu-devel] [PATCH] cirrus_vga: adding sanity check for vram size Andreas Färber
2014-05-09 11:18 ` Dr. David Alan Gilbert
2014-05-09 11:50   ` Paolo Bonzini
2014-05-09 11:54   ` Gerd Hoffmann
2014-05-09 12:02     ` Dr. David Alan Gilbert [this message]
2014-05-12 17:05     ` Eric Blake
2014-05-12 17:53       ` Andreas Färber
2014-05-12 17:03   ` Eric Blake

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=20140509120224.GB22335@work-vm \
    --to=dgilbert@redhat.com \
    --cc=afaerber@suse.de \
    --cc=arei.gonglei@huawei.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weidong.huang@huawei.com \
    /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).