From: Dario Faggioli <dario.faggioli@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 1/2] xen: fix a (latent) cpupool-related race during domain destroy
Date: Thu, 14 Jul 2016 16:54:53 +0200 [thread overview]
Message-ID: <1468508093.13039.55.camel@citrix.com> (raw)
In-Reply-To: <37bfb624-111a-32ed-ebfa-1f0be387dba0@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1870 bytes --]
On Thu, 2016-07-14 at 10:37 +0100, Andrew Cooper wrote:
> On 14/07/16 07:41, Dario Faggioli wrote:
> >
> > So, during domain destruction, we do:
> > cpupool_rm_domain() [ in domain_destroy() ]
> > sched_destroy_domain() [ in complete_domain_destroy() ]
> >
> > Therefore, there's a window during which, from the
> > scheduler's point of view, a domain is still there, but
> > without it being part of any cpupool.
> >
> > [...]
> >
> > On the other hand, cpupool_rm_domain() "only" does
> > cpupool related bookkeeping, and there's no harm
> > postponing it a little bit.
> >
> > Finally, considering that, during domain initialization,
> > we do:
> > cpupool_add_domain()
> > sched_init_domain()
> >
> > It looks like it makes much more sense for the domain
> > destroy path to look like the opposite of it, i.e.:
> > sched_destroy_domain()
> > cpupool_rm_domain()
> >
> > This patch does that, and it's considered worth, as it
> > fixes a bug, even if only a latent one.
> >
> > Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
> As the cpupool bookkeeping is very closely related to the scheduler
> bookkeeping, how about having the sched_*_domain() functions involve
> the
> cpupool_*_domain() functions?
>
That's certainly a good point.
At minimum, I certainly can (and probably should have :-P) put a couple
of ASSERT()-s in place.
However, both cpupool_add_domain() and cpupool_rm_domain() are called
only once, and I guess I can make them go into sched_init_domain() and
sched_destroy_domain(), respectively.
Dario
--
<<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: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-14 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 6:41 [PATCH 0/2] xen: cpupool (small) improvement and (latent) bug fix Dario Faggioli
2016-07-14 6:41 ` [PATCH 1/2] xen: fix a (latent) cpupool-related race during domain destroy Dario Faggioli
2016-07-14 9:37 ` Andrew Cooper
2016-07-14 14:54 ` Dario Faggioli [this message]
2016-07-14 14:55 ` Andrew Cooper
2016-07-14 6:41 ` [PATCH 2/2] xen: cpupool: small optimization when moving between pools 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=1468508093.13039.55.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.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 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.