From: Ian Campbell <ian.campbell@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>, xen-devel@lists.xen.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH OSSTEST v2 3/6] ts-xen-install: Add dom0_mem runvar to control dom0 memory
Date: Tue, 8 Sep 2015 12:48:44 +0100 [thread overview]
Message-ID: <1441712924.24450.75.camel@citrix.com> (raw)
In-Reply-To: <1438880611-13244-4-git-send-email-anthony.perard@citrix.com>
On Thu, 2015-08-06 at 18:03 +0100, Anthony PERARD wrote:
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> ---
> ts-xen-install | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/ts-xen-install b/ts-xen-install
> index 0f53382..17edfb7 100755
> --- a/ts-xen-install
> +++ b/ts-xen-install
> @@ -153,7 +153,8 @@ sub setupboot () {
> logm("No Xen console device defined for host");
> }
> if (toolstack($ho)->{Dom0MemFixed}) {
> - $xenhopt .= " dom0_mem=512M,max:512M";
> + my $mem = $r{'dom0_mem'} // 512;
I think the highest preference should be for $r{"$ho->{Ident}_dom0_mem"}
(which makes it host specific in multi host jobs). I think it is probably
still worth having a global dom0_mem runvar you have here too. So:
my $mem = $r{"$ho->{Ident}_dom0_mem"} // $r{'dom0_mem'} // 512;
(maybe needs wrapping)
> + $xenhopt .= " dom0_mem=${mem}M,max:${mem}M";
> }
>
> # If /boot/microcode.cpio is present then ts-host-install has
next prev parent reply other threads:[~2015-09-08 11:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 17:03 [PATCH OSSTEST v2 0/6] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
2015-08-06 17:03 ` [PATCH OSSTEST v2 1/6] ts-kernel-build: Enable CONFIG_NETFILTER_XT_TARGET_CHECKSUM Anthony PERARD
2015-08-06 17:03 ` [PATCH OSSTEST v2 2/6] ts-kernel-build: Compile CONFIG_CRYPTO_XTS in Anthony PERARD
2015-09-08 11:45 ` Ian Campbell
2015-08-06 17:03 ` [PATCH OSSTEST v2 3/6] ts-xen-install: Add dom0_mem runvar to control dom0 memory Anthony PERARD
2015-09-08 11:48 ` Ian Campbell [this message]
2015-09-08 12:52 ` Ian Campbell
2015-08-06 17:03 ` [PATCH OSSTEST v2 4/6] ts-openstack-devstack: Deploy OpenStack on a host Anthony PERARD
2015-09-08 13:03 ` Ian Campbell
2015-09-08 14:36 ` Ian Jackson
2015-09-25 12:36 ` Anthony PERARD
2015-09-25 12:35 ` Anthony PERARD
2015-09-25 12:45 ` Ian Campbell
2015-08-06 17:03 ` [PATCH OSSTEST v2 5/6] ts-openstack-tempest: Run Tempest to check OpenStack Anthony PERARD
2015-09-08 13:06 ` Ian Campbell
2015-09-25 13:04 ` Anthony PERARD
2015-09-25 13:17 ` Ian Campbell
2015-09-25 13:54 ` Ian Jackson
2015-08-06 17:03 ` [PATCH OSSTEST v2 6/6] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2015-09-08 13:14 ` Ian Campbell
2015-09-25 13:10 ` Anthony PERARD
2015-09-09 16:13 ` [PATCH OSSTEST v2 0/6] Have OpenStack tested on top of xen's master and libvirt's master Ian Campbell
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=1441712924.24450.75.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).