All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Don Slutz <dslutz@verizon.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] libxl: fix cirrus vga video memory setting with upstream qemu
Date: Thu, 8 May 2014 11:10:13 +0100	[thread overview]
Message-ID: <1399543813.9513.33.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <536A2523.6010609@m2r.biz>

On Wed, 2014-05-07 at 14:20 +0200, Fabio Fantoni wrote:
> Il 02/05/2014 22:04, Fabio Fantoni ha scritto:
> > 2014-05-02 21:44 GMT+02:00 Don Slutz <dslutz@verizon.com 
> > <mailto:dslutz@verizon.com>>:
> >
> >     On 05/02/14 07:41, Ian Campbell wrote:
> >
> >         On Sat, 2014-04-19 at 14:16 +0200, Fabio Fantoni wrote:
> >
> >             Reading one qemu-devel post seems that setting video memory of
> >             cirrus vga with upstream qemu is wrong even if not show
> >             errors.
> >
> >
> >     Fabio,
> >       You can add my:
> >
> >     Reviewed-by: Don Slutz <dslutz@verizon.com
> >     <mailto:dslutz@verizon.com>>
> >
> >     I have a similar code change locally (part of my pending
> >     list of to dos) (I just changed the global arg...).
> >
> >
> >         You later provided links but I think the conversation should be
> >         referenced here.
> >
> >
> >     I was part of the conversation.  When I was looking into upstreaming
> >     a change I have (pci_min_hole) to xen & qemu, I was asked by QEMU
> >     to report if it was not used (i.e. non x86 cpu's).  While I was
> >     testing my
> >     change to QEMU under xen I noticed:
> >
> >     Warning: "-global vga.vram_size_mb=16" not used
> >
> >
> >     In /var/log/xen/qemu-dm-<guest>.log
> >
> >     Here is the cross post to xen-devel:
> >
> >
> >      [Xen-devel] [PATCH v3 2/4] GlobalProperty: Display warning about
> >     unused -global
> >
> >
> >     http://lists.xen.org/archives/html/xen-devel/2014-03/msg03128.html
> >
> >
> >
> >
> >         Is this change correct for all versions of mainline qemu which
> >         people
> >         might be using with Xen?
> >
> >
> >     What I know is that "-global cirrus-vga.vgamem_mb=32" does work
> >     with upstream QEMU 1.5.0, 1.6.0, 1.7.0 and 2.0.0.  I had added a debug
> >     output into the QEMU version above that show the amount of video ram
> >     that gets allocated and so the testing was quick and easy.  My
> >     understanding of QEMU is that when specified this way:
> >
> >      "-device cirrus-vga,vgamem_mb=32"
> >
> >     the error checking in QEMU will report when it does not like it:
> >
> >     qemu-system-x86_64: Property '.vram_size_mb' not found
> >
> >
> >     (unlike -global).  So while I have not tested it, I would guess that
> >     any QEMU that accepts "-device cirrus-vga" will also either
> >     accept the change or report and error and not start. (Note: the
> >     change from "-vga cirrus" to "-device cirrus-vga" was done since
> >     4.3.0 and has yet to generate a bug).
> >
> >
> > Thanks for your reply, probably with my bad english I not understand 
> > good this part of your reply.
> > I changed to -device following this official qemu doc:
> > http://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/qdev-device-use.txt;hb=master
> > I did several tests of additional vga's parameters without using 
> > the-global in recent days with cirrus, stdvga and qxl, I've never seen 
> > errors and the amount of videoram by domUs seem ok.
> 
> Ping

I'm not sure who this was addressed to but for my part I am waiting for
a refreshed patch which addresses the questions asked in
<1399030886.32736.63.camel@kazak.uk.xensource.com> in the commit
message. Those questions have been partially answered here but it seem
that at least Don's comments about which versions it worked with were
wrt a different patch using a different variation on the options.

Ian.

  reply	other threads:[~2014-05-08 10:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 12:16 [PATCH] libxl: fix cirrus vga video memory setting with upstream qemu Fabio Fantoni
2014-04-22 13:11 ` Ian Jackson
2014-04-22 13:21   ` Fabio Fantoni
2014-04-24 10:33     ` Fabio Fantoni
2014-05-02  9:11       ` Fabio Fantoni
2014-05-02 11:41 ` Ian Campbell
2014-05-02 19:44   ` Don Slutz
2014-05-02 20:04     ` Fabio Fantoni
2014-05-07 12:20       ` Fabio Fantoni
2014-05-08 10:10         ` Ian Campbell [this message]
2014-05-08 10:41           ` Fabio Fantoni
2014-05-08 11:33             ` Ian Campbell
2014-05-08 15:03               ` Fabio Fantoni
2014-05-08 15:19                 ` Ian Campbell
2014-05-09  8:01                   ` Fabio Fantoni
2014-05-09  9:09                     ` Ian Campbell
2014-05-09 14:03                       ` Stefano Stabellini
2014-05-09 14:08                         ` Ian Campbell
2014-05-09 14:24                         ` Fabio Fantoni
2014-05-09 14:48                           ` Fabio Fantoni

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=1399543813.9513.33.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=fabio.fantoni@m2r.biz \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.