From: Yu Zhiguo <yuzg@cn.fujitsu.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: [PATCH 0/2] xl: Add subcommand mem-max and fix mem-set
Date: Wed, 12 May 2010 14:26:27 +0800 [thread overview]
Message-ID: <4BEA4A13.3000801@cn.fujitsu.com> (raw)
In-Reply-To: <4BE67620.7010803@cn.fujitsu.com>
Yu Zhiguo wrote:
>
> I'm trying to add subcommand 'mem-max', I think xc_domain_setmaxmem should
> be used in it but not here.
>
> I'll move this code to 'mem-max', and in 'mem-set', a check should be added
> because setting memory larger than max memory is invalid.
>
> 1. Add 'mem-max'
> Add libxl_domain_setmaxmem, it calls xc_domain_setmaxmem.
> /local/domain/$domid/memory/static-max should be updated when set max memory,
> it is missing now.
>
> 2. fix 'mem-set'
> Delete xc_domain_setmaxmem.
> Get max memory from /local/domain/$domid/memory/static-max, and then do value check.
> It seems that we cannot get max memory use libxc routines.
>
I fixed it, please check.
[PATCH 1/2] xl: Add command 'xl mem-max'
[PATCH 2/2] xl: Add check for command 'xl mem-set'
Regards
Yu Zhiguo
next prev parent reply other threads:[~2010-05-12 6:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 9:39 [PATCH] xl: Update memory info in xenstore when use 'xl mem-set' Yu Zhiguo
2010-05-07 17:42 ` Ian Jackson
2010-05-09 8:45 ` Yu Zhiguo
2010-05-12 6:26 ` Yu Zhiguo [this message]
2010-05-12 6:41 ` [PATCH 0/2] xl: Add subcommand mem-max and fix mem-set Yu Zhiguo
2010-05-12 11:33 ` Stefano Stabellini
2010-05-12 11:39 ` Stefano Stabellini
2010-05-14 2:15 ` [PATCH] xl: Fix missing memory target in xenstore Yu Zhiguo
2010-05-12 15:33 ` [PATCH 0/2] xl: Add subcommand mem-max and fix mem-set Jonathan Knowles
2010-05-13 12:21 ` 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=4BEA4A13.3000801@cn.fujitsu.com \
--to=yuzg@cn.fujitsu.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.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 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).