From: Dario Faggioli <dario.faggioli@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Juergen Gross <jgross@suse.com>, Meng Xu <mengxu@cis.upenn.edu>,
Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH v4 0/6] xen: sched: fix locking of {insert, remove}_vcpu()
Date: Wed, 04 Nov 2015 18:17:24 +0100 [thread overview]
Message-ID: <20151104170839.20002.15551.stgit@Solace.station> (raw)
Hi,
This series, improves how inserting vCPUs in schedulers runqueues is done,
including fixing a couple of bugs, and paving the way for more improvement in
Credit2 runqueue handling (will be submitted as a separate series).
v3 is here:
http://lists.xenproject.org/archives/html/xen-devel/2015-10/msg03278.html
Message-Id: <20151029225158.25219.4625.stgit@Solace.station>
Only patch 1 really changed from v3, and patches 1 and 2 are the only one that
seem to me to be missing suitable Ack-s.
There is a git branch for this series here:
git://xenbits.xen.org/people/dariof/xen.git rel/sched/fix-vcpu-ins-rem-v4
Regards,
Dario
---
Dario Faggioli (6):
xen: sched: fix locking of remove_vcpu() in credit1
xen: sched: fix locking for insert_vcpu() in credit1 and RTDS
xen: sched: clarify use cases of schedule_cpu_switch()
xen: sched: better handle (not) inserting idle vCPUs in runqueues
xen: sched: get rid of the per domain vCPU list in RTDS
xen: sched: get rid of the per domain vCPU list in Credit2
xen/common/cpupool.c | 7 -----
xen/common/sched_credit.c | 18 ++++++++-----
xen/common/sched_credit2.c | 55 ++++++++++++++--------------------------
xen/common/sched_rt.c | 61 ++++++++++++++++++++++----------------------
xen/common/schedule.c | 57 +++++++++++++++++++++++++++++++----------
5 files changed, 103 insertions(+), 95 deletions(-)
--
<<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)
next reply other threads:[~2015-11-04 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 17:17 Dario Faggioli [this message]
2015-11-04 17:17 ` [PATCH v4 1/6] xen: sched: fix locking of remove_vcpu() in credit1 Dario Faggioli
2015-11-04 17:22 ` George Dunlap
2015-11-04 17:17 ` [PATCH v4 2/6] xen: sched: fix locking for insert_vcpu() in credit1 and RTDS Dario Faggioli
2015-11-24 11:34 ` George Dunlap
2015-11-04 17:17 ` [PATCH v4 3/6] xen: sched: clarify use cases of schedule_cpu_switch() Dario Faggioli
2015-11-04 17:17 ` [PATCH v4 4/6] xen: sched: better handle (not) inserting idle vCPUs in runqueues Dario Faggioli
2015-11-04 17:18 ` [PATCH v4 5/6] xen: sched: get rid of the per domain vCPU list in RTDS Dario Faggioli
2015-11-04 17:18 ` [PATCH v4 6/6] xen: sched: get rid of the per domain vCPU list in Credit2 Dario Faggioli
2015-11-23 14:03 ` [PATCH v4 0/6] xen: sched: fix locking of {insert, remove}_vcpu() George Dunlap
2015-11-23 14:40 ` Jan Beulich
2015-11-23 14:50 ` George Dunlap
2015-11-23 15:00 ` Jan Beulich
2015-11-24 3:27 ` Meng Xu
2015-11-24 8:05 ` Jan Beulich
2015-11-24 11:03 ` George Dunlap
2015-11-24 11:49 ` 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=20151104170839.20002.15551.stgit@Solace.station \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jgross@suse.com \
--cc=mengxu@cis.upenn.edu \
--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.