From: Andres Lagar-Cavilla <andres@lagarcavilla.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] libxenlight: implement libxl_set_memory_target
Date: Thu, 10 Dec 2009 10:10:52 -0500 [thread overview]
Message-ID: <4B210F7C.3000007@lagarcavilla.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0912101430130.27995@kaball-desktop>
Oh, I'm working with an old changeset. Yikes. Thanks,
Andres
Stefano Stabellini wrote:
> On Thu, 10 Dec 2009, Andres Lagar-Cavilla wrote:
>
>> Errrr, no.
>> http://xenbits.xen.org/xen-unstable.hg?file/8f304c003af4/tools/libxl/libxl.c
>> shows that the videoram node will be set only if we are using a
>> device-model. And specifically if we are in fully virtualized mode, i.e.
>> dm_info->type == XENFV, i.e. *not* PV
>>
>
> I understand that this can be confusing, but at the moment we have two
> videoram parameters: dm_info->videoram is for the device model while
> b_info->video_memkb is for domain building.
> If you look at init_dm_info, you'll see that dm_info->videoram is set
> from b_info->video_memkb.
> Also if you read libxl_dom.c:build_post you'll see that no matter if the
> guest is a pv or an hvm domain, memory/videoram will be written to
> xenstore anyway.
>
>
next prev parent reply other threads:[~2009-12-10 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091208200031.4903B5980EB@homiemail-mx11.g.dreamhost.com>
2009-12-08 20:29 ` [PATCH] libxenlight: implement libxl_set_memory_target Andres Lagar-Cavilla
2009-12-09 13:19 ` Stefano Stabellini
2009-12-09 20:47 ` Andres Lagar-Cavilla
2009-12-10 13:37 ` Stefano Stabellini
2009-12-10 14:01 ` Andres Lagar-Cavilla
2009-12-10 14:41 ` Stefano Stabellini
2009-12-10 15:10 ` Andres Lagar-Cavilla [this message]
2009-12-08 18:23 Stefano Stabellini
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=4B210F7C.3000007@lagarcavilla.com \
--to=andres@lagarcavilla.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.