xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Patch] use full-size cpumask for vcpu-pin
Date: Fri, 13 Aug 2010 13:58:36 +0100	[thread overview]
Message-ID: <C88B000C.1DB2F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <19557.15157.439902.435164@mariner.uk.xensource.com>

On 13/08/2010 13:31, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:

> Juergen Gross writes ("[Xen-devel] [Patch] use full-size cpumask for
> vcpu-pin"):
>> attached patch solves a problem with vcpu-pinning and hot-plug of cpus:
> 
> Thanks.  This is a mixed tools/hypervisor patch.  We've discussed it
> and it seems good to me.  Keir, would you care to apply it, or would
> you like it to go through the tools tree ?
> 
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

Actually, now I look at it, I have to NACK the patch. Sorry I didn't look
closely enough earlier. I think the bug can be addressed without any
hypervisor changes: when vcpu-pinning, the tools can quite correctly pass a
cpumask to Xen just big enough to express just the CPUs in the new affinity
set. If the resulting mask is too narrow to address all CPUs in the system,
then Xen will pad it out with zeroes. If the resulting mask is too wide, Xen
will simply truncate it. All this is done silently at the time of the
setvcpuaffinity hypercall. Hence, Juergen's hypervisor changes are really
unnecessary, and a neater tools fix could probably be arrived at without the
hypervisor changes.

 -- Keir

> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-08-13 12:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02  6:40 [Patch] use full-size cpumask for vcpu-pin Juergen Gross
2010-08-10 14:11 ` Ian Jackson
2010-08-10 14:27   ` Keir Fraser
2010-08-11  4:32   ` Juergen Gross
2010-08-13 12:31 ` Ian Jackson
2010-08-13 12:58   ` Keir Fraser [this message]
2010-08-13 13:11     ` Ian Jackson
2010-08-13 13:15       ` Keir Fraser
2010-08-13 13:21         ` Keir Fraser
2010-08-13 13:25           ` Keir Fraser
2010-08-13 13:29             ` Ian Jackson
2010-08-13 13:30             ` Keir Fraser
2010-08-13 14:09               ` 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=C88B000C.1DB2F%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=juergen.gross@ts.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 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).