From: Michal Novotny <minovotn@redhat.com>
To: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Check for valid CPU_CAP value when creating (constructing) new domain
Date: Mon, 30 Mar 2009 09:35:42 +0200 [thread overview]
Message-ID: <49D0764E.60300@redhat.com> (raw)
In-Reply-To: <DDC9B1061F355Ekanno.masaki@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
Hi Kan,
this is new version of my patch implementing check for both CPU_CAP and
CPU_WEIGHT and also considering int type for both (asserting it).
Best regards,
Michal
Masaki Kanno wrote:
> Hi Michal,
>
> Why does the patch implement only CPU_CAP?
> You should consider CPU_WEIGHT too.
> And you should consider scheduler types too.
>
> Best regards,
> Kan
>
> Mon, 30 Mar 2009 08:43:07 +0200, Michal Novotny wrote:
>
>
>> Hi,
>>
>> This patch implements check for valid cpu_cap value when creating domain (
>> in range 0 to VcpuCount * 100 as when changing scheduler parameters).
>>
>> Signed-off-by: Michal Novotny <minovotn@redhat.com>
>>
>>
>> -------------------------------text/plain-------------------------------
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
[-- Attachment #2: xen-valid-cap-value-when-creating-domain.patch --]
[-- Type: text/plain, Size: 967 bytes --]
diff -r 0b13d9787622 tools/python/xen/xend/XendDomainInfo.py
--- a/tools/python/xen/xend/XendDomainInfo.py Tue Mar 24 06:55:29 2009 +0000
+++ b/tools/python/xen/xend/XendDomainInfo.py Mon Mar 30 09:27:37 2009 +0200
@@ -2305,6 +2305,20 @@
# Set maximum number of vcpus in domain
xc.domain_max_vcpus(self.domid, int(self.info['VCPUs_max']))
+ # Check for cpu_{cap|weight} validity
+ cap = self.getCap()
+ weight = self.getWeight()
+
+ assert type(weight) == int
+ assert type(cap) == int
+
+ if weight < 1 or weight > 65535:
+ raise VmError("Cpu weight out of range, valid values are within range from 1 to 65535")
+
+ if cap < 0 or cap > dominfo.getVCpuCount() * 100:
+ raise VmError("Cpu cap out of range, valid range is from 0 to %s for specified number of vcpus" %
+ (dominfo.getVCpuCount() * 100))
+
# Test whether the devices can be assigned with VT-d
pci = self.info["platform"].get("pci")
pci_str = ''
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-03-30 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 6:43 [PATCH] Check for valid CPU_CAP value when creating (constructing) new domain Michal Novotny
2009-03-30 7:07 ` Masaki Kanno
2009-03-30 7:35 ` Michal Novotny [this message]
2009-03-30 7:52 ` [PATCH] Check for valid CPU_CAP value when creating(constructing) " Masaki Kanno
2009-03-30 7:55 ` Michal Novotny
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=49D0764E.60300@redhat.com \
--to=minovotn@redhat.com \
--cc=kanno.masaki@jp.fujitsu.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.