All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Cc: Juergen Gross <JGross@suse.com>, Keir Fraser <keir.xen@gmail.com>,
	Justin Weaver <jtweaver@hawaii.edu>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] xen: postpone updating domains' node affinity when removing a CPU from a cpupool
Date: Wed, 11 Mar 2015 15:01:15 +0000	[thread overview]
Message-ID: <550058BB.7000102@eu.citrix.com> (raw)
In-Reply-To: <20150309164901.11859.95044.stgit@Solace.station>

On 03/09/2015 04:49 PM, Dario Faggioli wrote:
> 93be8285 ("update domU's node-affinity on the cpupool_unassign_cpu()
> path")  does the right thing, but does it too early. In fact, it
> is necessary to call domain_update_node_affinity() when a pCPU is
> removed from a cpupool, but that must happen after the pCPU is
> really gone from there.
> 
> More specifically, it is important that the update happens not
> before cpu_disable_scheduler() is called on that pCPU, to give
> that function the chance to fixup the vCPU affinity of the
> domains residing in the cpupool, if that is necessary.

It looks like domain_update_node_affinity() is already called for each
domain in the cpupool in cpu_disable_scheduler().  It doesn't look like
there should be a need to call it twice.  Can we just remove the call to
domain_update_node_affinity() in cpupool_unassign_cpu() and not add it back?

 -George

  parent reply	other threads:[~2015-03-11 15:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 16:49 [PATCH] xen: postpone updating domains' node affinity when removing a CPU from a cpupool Dario Faggioli
2015-03-11 10:32 ` Dario Faggioli
2015-03-11 15:01 ` George Dunlap [this message]
2015-03-11 16:04   ` Dario Faggioli
2015-03-12 13:45     ` [PATCH] xen: avoid updating node affinity twice " Dario Faggioli
2015-03-12 14:51       ` Jan Beulich
2015-03-12 15:52         ` Dario Faggioli
2015-03-13 11:15           ` George Dunlap
2015-03-12 14:52       ` George Dunlap
2015-03-12 15:56         ` Dario Faggioli

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=550058BB.7000102@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=JGross@suse.com \
    --cc=dario.faggioli@citrix.com \
    --cc=jtweaver@hawaii.edu \
    --cc=keir.xen@gmail.com \
    --cc=xen-devel@lists.xen.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 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.