xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Shall we clear the cpumap in XEN_DOMCTL_setvcpuaffinity
Date: Wed, 12 May 2010 08:43:06 +0100	[thread overview]
Message-ID: <C8101A9A.13FD4%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659731E5F20AF@shsmsx501.ccr.corp.intel.com>

On 12/05/2010 08:22, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:

> When browse code, I noticed if the op->u.vcpuaffinity.cpumap is NULL, a random
> value of new_affinity will be passed to vcpu_set_affinity(), as in followed
> code.
> 
> I'm not sure if this is expected result. IMO, we should return -EINVAL if no
> cpu specified, as the return value at vcpu_set_affinity() for empty cpumap.

Xen-unstable:21350.

 Thanks,
 Keir

> Did I missed anything?
> 
>     case XEN_DOMCTL_getvcpuaffinity:
>     {
>         domid_t dom = op->domain;
>         struct domain *d = rcu_lock_domain_by_id(dom);
>         struct vcpu *v;
>         cpumask_t new_affinity;
> ......
>         if ( op->cmd == XEN_DOMCTL_setvcpuaffinity )
>         {
>             xenctl_cpumap_to_cpumask(  >>>>> the new_affinity is not
> initialized for if cpumap==NULL
>                 &new_affinity, &op->u.vcpuaffinity.cpumap);
>             ret = vcpu_set_affinity(v, &new_affinity);
>         }
> 
> Thanks
> --jyh

  reply	other threads:[~2010-05-12  7:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12  7:22 Shall we clear the cpumap in XEN_DOMCTL_setvcpuaffinity Jiang, Yunhong
2010-05-12  7:43 ` Keir Fraser [this message]
2010-05-12  7:57   ` Jiang, Yunhong
2010-05-12  8:11     ` Keir Fraser

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=C8101A9A.13FD4%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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).