|
|
|
|
|
|
|
|
|
|
xen-changelog
[Xen-changelog] domain_setmaxmem takes an int, not a long, for the maxme
# HG changeset patch
# User emellor@ewan
# Node ID 3fbefefb54aaa3280061f65a90e05cba55cac080
# Parent 6d13fd58633825e35c069afc1116db86e796d58d
domain_setmaxmem takes an int, not a long, for the maxmem_kb parameter. The
underlying xc_domain_setmaxmem already took an unsigned int, and
PyArg_ParseTupleAndKeywords call was only parsing an int, so there is no way
that longer values would get through here in any case. Fixing the documentation
and the local variable is the best solution, until someone decides that we need
to support maxmem values greater than 2TiB.
Signed-off-by: Ewan Mellor <ewan@xxxxxxxxxxxxx>
diff -r 6d13fd586338 -r 3fbefefb54aa tools/python/xen/lowlevel/xc/xc.c
--- a/tools/python/xen/lowlevel/xc/xc.c Tue Sep 20 16:25:27 2005
+++ b/tools/python/xen/lowlevel/xc/xc.c Tue Sep 20 16:29:57 2005
@@ -847,7 +847,7 @@
XcObject *xc = (XcObject *)self;
u32 dom;
- unsigned long maxmem_kb;
+ unsigned int maxmem_kb;
static char *kwd_list[] = { "dom", "maxmem_kb", NULL };
@@ -1178,7 +1178,7 @@
METH_VARARGS | METH_KEYWORDS, "\n"
"Set a domain's memory limit\n"
" dom [int]: Identifier of domain.\n"
- " maxmem_kb [long]: .\n"
+ " maxmem_kb [int]: .\n"
"Returns: [int] 0 on success; -1 on error.\n" },
{ "domain_memory_increase_reservation",
_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-changelog] domain_setmaxmem takes an int, not a long, for the maxmem_kb parameter. The,
Xen patchbot -unstable <=
|
|
|
|
|