xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>, Tim Deegan <tim@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Dario Faggioli <dfaggioli@suse.com>,
	Julien Grall <julien.grall@arm.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: [Xen-devel] [PATCH v3 0/4] xen/sched: use new idle scheduler for free cpus
Date: Mon,  9 Sep 2019 11:33:35 +0200	[thread overview]
Message-ID: <20190909093339.7134-1-jgross@suse.com> (raw)

These three patches have been carved out from my core scheduling series
as they are sufficiently independent to be applied even without the big
series.

Without this little series there are messages like the following to be
seen on the console when booting with smt=0:

(XEN) Adding cpu 1 to runqueue 0
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...

By assigning cpus to Cpupool-0 only after all cpus are up and by not
using the more complicated credit2 scheduler for cpus not in any
cpupool this situation can simply no longer happen, as parking the not
to be started threads is done before.

Changes in V3:
- use ZERO_BLOCK_PTR (Patch 3)
- add patch 4

Changes in V2:
- commit messages updated
- renamed functions (Patch 2)

Juergen Gross (4):
  xen/sched: populate cpupool0 only after all cpus are up
  xen/sched: remove cpu from pool0 before removing it
  xen/sched: add minimalistic idle scheduler for free cpus
  xen/sched: switch to debugtrace in cpupool handling

 xen/common/cpupool.c       | 228 +++++++++++++++++++++++++++------------------
 xen/common/sched_credit.c  |   9 --
 xen/common/sched_null.c    |   7 --
 xen/common/schedule.c      | 172 +++++++++++++++++-----------------
 xen/include/xen/sched-if.h |   2 +
 5 files changed, 229 insertions(+), 189 deletions(-)

-- 
2.16.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2019-09-09  9:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  9:33 Juergen Gross [this message]
2019-09-09  9:33 ` [Xen-devel] [PATCH v3 1/4] xen/sched: populate cpupool0 only after all cpus are up Juergen Gross
2019-09-13 16:54   ` Dario Faggioli
2019-09-09  9:33 ` [Xen-devel] [PATCH v3 2/4] xen/sched: remove cpu from pool0 before removing it Juergen Gross
2019-09-13 17:27   ` Dario Faggioli
2019-09-14  5:04     ` Juergen Gross
2019-09-09  9:33 ` [Xen-devel] [PATCH v3 3/4] xen/sched: add minimalistic idle scheduler for free cpus Juergen Gross
2019-09-09  9:33 ` [Xen-devel] [PATCH v3 4/4] xen/sched: switch to debugtrace in cpupool handling Juergen Gross
2019-09-12  8:24   ` 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=20190909093339.7134-1-jgross@suse.com \
    --to=jgross@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dfaggioli@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wl@xen.org \
    --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).