From: Michal Novotny <minovotn@redhat.com>
To: Masaki Kanno <kanno.masaki@jp.fujitsu.com>,
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:55:23 +0200 [thread overview]
Message-ID: <49D07AEB.2050500@redhat.com> (raw)
In-Reply-To: <DEC9B10C7013DDkanno.masaki@jp.fujitsu.com>
Hi Kan,
looks fine to me. Sorry about indents - I forgot I was writing it in
gedit now and not Midnight Commander editor - and that I forgot about
scheduler type.
Best regards,
Michal
Masaki Kanno wrote:
> Hi Michal,
>
> I have added the following fixes to your patch.
> - Check scheduler type
> - Replace tab-indent with space-indent
>
> How about the patch?
>
> Signed-off-by: Michal Novotny <minovotn@redhat.com>
> Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
>
> Best regards,
> Kan
>
>
> Mon, 30 Mar 2009 09:35:42 +0200, Michal Novotny wrote:
>
>
>> 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
>>>>
>>>>
>>>
>>>
>> -------------------------------text/plain-------------------------------
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
prev parent reply other threads:[~2009-03-30 7:55 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
2009-03-30 7:52 ` [PATCH] Check for valid CPU_CAP value when creating(constructing) " Masaki Kanno
2009-03-30 7:55 ` Michal Novotny [this message]
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=49D07AEB.2050500@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.