All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Fantoni <fantonifabio@tiscali.it>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] tools/libxl: Improve videoram setting
Date: Thu, 10 Jan 2013 16:47:22 +0100	[thread overview]
Message-ID: <50EEE28A.7070607@tiscali.it> (raw)
In-Reply-To: <alpine.DEB.2.02.1301101440300.4981@kaball.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1690 bytes --]

Il 10/01/2013 15:40, Stefano Stabellini ha scritto:
> On Thu, 10 Jan 2013, Ian Campbell wrote:
>> On Thu, 2013-01-10 at 14:34 +0000, Stefano Stabellini wrote:
>>> diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
>>>> index e964bf1..2bfbcf4 100644
>>>> --- a/tools/libxl/xl_cmdimpl.c
>>>> +++ b/tools/libxl/xl_cmdimpl.c
>>>> @@ -832,7 +832,8 @@ static void parse_config_data(const char *config_source,
>>>>       xlu_cfg_get_defbool(config, "localtime", &b_info->localtime, 0);
>>>>
>>>>       if (!xlu_cfg_get_long (config, "videoram", &l, 0))
>>>> -        b_info->video_memkb = l * 1024;
>>>> +        if ( l > 8 )
>>>> +            b_info->video_memkb = l * 1024;
>>> Limiting the minimum amount of videoram could be a good idea, but the
>>> minimum should be 4MB, not 8MB
>> I'm not convinced by silently limiting the memory, this deserve at least
>> a WARNING if not an outright failure.
>>
>> Also, does this sort of limit checking make more sense in libxl?
> Yes, you are right on both comments
>
>
> -----
> Nessun virus nel messaggio.
> Controllato da AVG - www.avg.com
> Versione: 2013.0.2805 / Database dei virus: 2637/6021 -  Data di rilascio: 09/01/2013
>
>
About limiting to 8 mb minimum it seems to be necessary on upstream qemu 
otherwise qemu crash on start, besides libxl already has a default of 8 
mb if videoram is not set.
I'll add libxl error if videoram is < 8, can it be good?
About videoram setting, I didn't find the setting for stdvga in the code.
Here for example the commit for cirrus:
http://xenbits.xen.org/gitweb/?p=staging/qemu-upstream-unstable.git;a=commit;h=19403a68fb8eaefb2e1245b6a8384d3a3ffa7ca0


[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2013-01-10 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 11:07 [PATCH] tools/libxl: Improve videoram setting Fabio Fantoni
2013-01-10 14:34 ` Stefano Stabellini
2013-01-10 14:37   ` Ian Campbell
2013-01-10 14:40     ` Stefano Stabellini
2013-01-10 15:47       ` Fabio Fantoni [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=50EEE28A.7070607@tiscali.it \
    --to=fantonifabio@tiscali.it \
    --cc=Ian.Campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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.