From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 1/2] libxl: turn NUMA placement misconfigs into warnings
Date: Fri, 3 Jul 2015 16:52:01 +0200 [thread overview]
Message-ID: <1435935121.14347.88.camel@citrix.com> (raw)
In-Reply-To: <21910.27981.264095.978895@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1855 bytes --]
On Fri, 2015-07-03 at 12:09 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH 1/2] libxl: turn NUMA placement misconfigs into warnings"):
> > On Wed, 2015-07-01 at 15:38 +0100, Ian Jackson wrote:
> > > But, be aware that you are making a semantic change to the API which
> > > cannot be reverted for backwards-compatibility reasons.
> >
> > Is any further action required due to this?
>
> Not if it doesn't cause you or Dario to change your mind about the
> patch :-).
>
It doesn't. This is the right thing to do, and should have been like
this from the beginning!
Just FTR, the reason why we were using the numa_autoplacement for sanity
checking was that, a while back, we were always passing a (potentially)
valid cpumap (for vcpu affinity) as part of the domain config. Hence we
needed something to distinguish the case were such a cpumap was full (or
empty, I can't recall) because of an explicit user choice, or as a mean
to ask libxl to perform the automatic placement.
I can't remember either why we did not do it, in the first place, the
way it is now (i.e., cpumaps *not allocated* --> do the placement), but
I never liked the fact that, if one[*] sets the affinity explicitly, but
forget to set numa_autoplacement to false, the domain does not build.
So, in summary, no, I don't think I will easily change my mind about
this needing to be a warning, rather than a fatal error.
Thanks and Regards,
Dario
[*] of course I'm talking about downstream toolstacks, like xl or
libvirt, not actual users, as in xl we do this consistently!
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-03 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 14:02 [PATCH 0/2] libxl: fix NUMA placement preventing domain config to be re-used Dario Faggioli
2015-07-01 14:03 ` [PATCH 1/2] libxl: turn NUMA placement misconfigs into warnings Dario Faggioli
2015-07-01 14:38 ` Ian Jackson
2015-07-03 10:35 ` Ian Campbell
2015-07-03 11:09 ` Ian Jackson
2015-07-03 14:52 ` Dario Faggioli [this message]
2015-07-01 14:03 ` [PATCH 2/2] libxl: unset info->numa_placement upon successful placement Dario Faggioli
2015-07-01 14:39 ` Ian Jackson
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=1435935121.14347.88.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).