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: Tue, 10 Aug 2010 15:27:54 +0100 [thread overview]
Message-ID: <C887207A.1D484%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <19553.24054.564316.142633@mariner.uk.xensource.com>
On 10/08/2010 15:11, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
> Juergen Gross writes ("[Xen-devel] [Patch] use full-size cpumask for
> vcpu-pin"):
>> The reason is the allocation of the cpumap for pinning: the size is only for
>> the ACTUAL number of physical cpus in the system, not the possible number.
>> The solution is to allocate a cpumap for up to NR_CPUS.
>
> Thanks for this patch. However, this doesn't seem to be even slightly
> backwards-compatible, because it changes the layout of the physinfo
> sysctl response.
The domctl and sysctl hypercalls do not need to be backward compatible
across major Xen releases. All other hypercalls absolutely do.
-- Keir
next prev parent reply other threads:[~2010-08-10 14:27 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 [this message]
2010-08-11 4:32 ` Juergen Gross
2010-08-13 12:31 ` Ian Jackson
2010-08-13 12:58 ` Keir Fraser
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=C887207A.1D484%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).