All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 4] videoram allocation and stdvga improvements
Date: Wed, 14 Jan 2009 19:00:38 +0000	[thread overview]
Message-ID: <496E3656.7000206@eu.citrix.com> (raw)
In-Reply-To: <20090113143136.GI5033@const.bordeaux.inria.fr>

Samuel Thibault wrote:

> Samuel Thibault, le Tue 13 Jan 2009 15:01:08 +0100, a écrit :
>> Stefano Stabellini, le Tue 13 Jan 2009 12:17:47 +0000, a écrit :
>>> In order to simplify the codepath and the libxc API, this patch series
>>> removes the videoram allocation code from hvmloader and lets qemu do the
>>> job, using xc_domain_memory_populate_physmap.
>> That's what it was doing before I made hvmloader do it.  The reason was
>> to make save/restore work fine with stubdomains dirty log, etc.
> 
> Ah, now I remember the precise reason, written in the 18383 changelog:
> 
> When creating an HVM domain, if e.g. another domain is created before
> qemu allocates video memory, the extra 8MB memory ballooning is not
> available any more, because it got consumed by the other domain.
> 

The current design of the autoballoner is limited, as a consequence the
autoballoner is racy and it should not be used at all if the user plans
to start multiple domains at the same time.

  parent reply	other threads:[~2009-01-14 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 12:17 [PATCH 0 of 4] videoram allocation and stdvga improvements Stefano Stabellini
2009-01-13 14:01 ` Samuel Thibault
2009-01-13 14:31   ` Samuel Thibault
2009-01-13 14:45     ` Keir Fraser
2009-01-14 19:00     ` Stefano Stabellini [this message]
2009-01-14 22:19       ` Samuel Thibault

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=496E3656.7000206@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=samuel.thibault@ens-lyon.org \
    --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.