From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Daniel Kiper <daniel.kiper@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH 2/2] libxl: xl mem-set should not enforce memory limits
Date: Fri, 15 Mar 2013 12:57:57 -0400 [thread overview]
Message-ID: <20130315165757.GB16644@phenom.dumpdata.com> (raw)
In-Reply-To: <1363365173.520.33.camel@zakaz.uk.xensource.com>
On Fri, Mar 15, 2013 at 04:32:53PM +0000, Ian Campbell wrote:
> On Fri, 2013-03-15 at 16:25 +0000, Daniel Kiper wrote:
> > xl mem-set should not enforce memory limits. If it does
>
> NB the title says libxl but this is actually an xl change.
>
> > then after decreasing reservation there is no chance to
> > increase reservation directly from guest domain by
> > writing to /sys/devices/system/xen_memory/xen_memory0/target*
>
> This is a feature not a bug I think. It is intentional that if the host
> admin sets a memory target the a guest admin cannot exceed that limit.
Even thought 'xm' did not do it?
>
> Ian.
>
> >
> > Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
> > ---
> > tools/libxl/xl_cmdimpl.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
> > index a98705e..9add281 100644
> > --- a/tools/libxl/xl_cmdimpl.c
> > +++ b/tools/libxl/xl_cmdimpl.c
> > @@ -2492,7 +2492,7 @@ static void set_memory_target(uint32_t domid, const char *mem)
> > exit(3);
> > }
> >
> > - libxl_set_memory_target(ctx, domid, memorykb, 0, /* enforce */ 1);
> > + libxl_set_memory_target(ctx, domid, memorykb, 0, 0);
> > }
> >
> > int main_memset(int argc, char **argv)
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-03-15 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 16:25 [PATCH 0/2] libxl: memory management patches Daniel Kiper
2013-03-15 16:25 ` [PATCH 1/2] libxl: xl mem-max et consortes must update static-max in xenstore too Daniel Kiper
2013-03-16 13:39 ` Konrad Rzeszutek Wilk
2013-03-15 16:25 ` [PATCH 2/2] libxl: xl mem-set should not enforce memory limits Daniel Kiper
2013-03-15 16:32 ` Ian Campbell
2013-03-15 16:57 ` Konrad Rzeszutek Wilk [this message]
2013-03-15 16:59 ` Ian Campbell
2013-03-15 17:10 ` Daniel Kiper
2013-03-15 17:07 ` Daniel Kiper
2013-03-15 17:09 ` Ian Jackson
2013-03-15 17:18 ` George Dunlap
2013-03-15 17:19 ` Daniel Kiper
2013-03-15 17:26 ` Konrad Rzeszutek Wilk
2013-03-15 20:01 ` Ian Campbell
2013-03-16 13:37 ` Konrad Rzeszutek Wilk
2013-03-18 9:51 ` Ian Campbell
2013-03-19 17:02 ` Konrad Rzeszutek Wilk
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=20130315165757.GB16644@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=daniel.kiper@oracle.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.