From: Don Slutz <dslutz@verizon.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Shriram Rajagopalan <rshriram@cs.ubc.ca>,
Yang Hongyang <yanghy@cn.fujitsu.com>
Subject: Re: [PATCH 1/1] xc_domain_restore: Allow QEMU to increase memory
Date: Wed, 15 Apr 2015 14:17:51 -0400 [thread overview]
Message-ID: <552EAB4F.208@one.verizon.com> (raw)
In-Reply-To: <1429108252.15516.301.camel@citrix.com>
On 04/15/15 10:30, Ian Campbell wrote:
> On Mon, 2015-04-13 at 12:09 -0400, Don Slutz wrote:
>>
>> +/* Leave some slack so that hvmloader does not complain about lack of
>> + * memory at boot time ("Could not allocate order=0 extent").
>> + * Once hvmloader is modified to cope with that situation without
>> + * printing warning messages, QEMU_SPARE_PAGES can be removed.
>
> How and where is hvmloader involved in a domain restore?
>
If the domU is created paused, saved, and restored, hvmloader will be
the 1st thing to execute. This comment is in QEMU and this old (bad)
way needed to leave room for hvmloader.
My understanding is that when xc_domain_populate_physmap_exact() returns
an error (which outputs and error on the console), hvmloader
will "correctly handle this.
-Don Slutz
> Ian.
>
prev parent reply other threads:[~2015-04-15 18:17 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 16:09 [PATCH 1/1] xc_domain_restore: Allow QEMU to increase memory Don Slutz
2015-04-13 16:20 ` Wei Liu
2015-04-13 23:51 ` Don Slutz
2015-04-13 16:25 ` Andrew Cooper
2015-04-13 23:51 ` Don Slutz
2015-04-14 8:53 ` Wei Liu
2015-04-14 17:34 ` Don Slutz
2015-04-14 17:51 ` Wei Liu
2015-04-15 9:46 ` Stefano Stabellini
2015-04-15 10:09 ` Ian Campbell
2015-04-15 11:15 ` Hongyang Yang
2015-04-15 11:27 ` Stefano Stabellini
2015-04-15 11:56 ` Ian Campbell
2015-04-15 18:19 ` Don Slutz
2015-04-14 8:53 ` Andrew Cooper
2015-04-14 9:22 ` Hongyang Yang
2015-04-14 9:28 ` Andrew Cooper
2015-04-14 9:42 ` Hongyang Yang
2015-04-15 14:32 ` Ian Campbell
2015-04-15 20:41 ` Don Slutz
2015-04-14 9:29 ` Wei Liu
2015-04-14 9:40 ` Hongyang Yang
2015-04-14 9:52 ` Wei Liu
2015-04-14 17:43 ` Don Slutz
2015-04-14 17:54 ` Wei Liu
2015-04-14 22:06 ` [PATCH v2 1/1] tools: Handle xc_maxmem adjustments Don Slutz
2015-04-15 9:53 ` Andrew Cooper
2015-04-15 9:57 ` Stefano Stabellini
2015-04-15 10:03 ` Andrew Cooper
2015-04-15 10:21 ` George Dunlap
2015-04-15 11:48 ` Stefano Stabellini
2015-04-15 21:43 ` Don Slutz
2015-04-15 10:16 ` George Dunlap
2015-04-15 10:25 ` George Dunlap
2015-04-15 10:30 ` Andrew Cooper
2015-04-15 14:34 ` [PATCH 1/1] xc_domain_restore: Allow QEMU to increase memory Ian Campbell
2015-04-15 16:36 ` Wei Liu
2015-04-15 16:45 ` Ian Campbell
2015-04-15 16:52 ` Wei Liu
2015-04-15 18:24 ` Don Slutz
2015-04-16 9:00 ` Ian Campbell
2015-04-16 9:14 ` George Dunlap
2015-04-16 9:29 ` Ian Campbell
2015-04-14 3:46 ` Hongyang Yang
2015-04-14 8:46 ` Wei Liu
2015-04-15 14:30 ` Ian Campbell
2015-04-15 18:17 ` Don Slutz [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=552EAB4F.208@one.verizon.com \
--to=dslutz@verizon.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=rshriram@cs.ubc.ca \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yanghy@cn.fujitsu.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.