From: Sergey Dyasli <sergey.dyasli@citrix.com>
To: "Jürgen Groß" <jgross@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
George Dunlap <George.Dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Dario Faggioli <dfaggioli@suse.com>
Subject: Re: [PATCH] sched: print information about scheduler granularity
Date: Thu, 16 Apr 2020 09:20:45 +0000 [thread overview]
Message-ID: <1587028832608.72974@citrix.com> (raw)
In-Reply-To: <996ed66e-3782-5187-a804-9291741a2241@suse.com>
On 16/04/2020 09:57, Jürgen Groß wrote:
> On 16.04.20 10:33, Sergey Dyasli wrote:
>> Currently it might be not obvious which scheduling mode is being used
>> by the scheduler. Alleviate this by printing additional information
>> about the selected granularity. Messages now look like these:
>>
>> 1. boot
>> (XEN) [00089808f0ea7496] Using scheduler: SMP Credit Scheduler (credit) in core-scheduling mode
>>
>> 2. xl debug-keys r
>> (XEN) [ 45.914314] Scheduler: SMP Credit Scheduler (credit) in 2-way core-scheduling mode
>>
>> Signed-off-by: Sergey Dyasli <sergey.dyasli@citrix.com>
>
> Hmm, do we need that?
>
> The xen commandline ins part of the boot messages and is contained
> in the "xl info" output.
It's true that you can see "sched-gran=core" in "xl info" output. But that's
just the switch - not the end result. A user might want to verify that he did
everything correctly and core-scheduling mode has indeed been enabled.
--
Thanks,
Sergey
next prev parent reply other threads:[~2020-04-16 9:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 8:33 [PATCH] sched: print information about scheduler granularity Sergey Dyasli
2020-04-16 8:57 ` Jürgen Groß
2020-04-16 9:20 ` Sergey Dyasli [this message]
2020-04-16 9:25 ` Jürgen Groß
2020-04-16 9:38 ` Sergey Dyasli
2020-04-16 16:47 ` Dario Faggioli
2020-04-17 7:54 ` Jürgen Groß
2020-04-16 16:43 ` Dario Faggioli
2020-04-17 7:57 ` Jürgen Groß
2020-04-17 13:43 ` Sergey Dyasli
2020-04-17 13:52 ` Jürgen Groß
2020-04-17 14:37 ` Dario Faggioli
2020-04-17 14:36 ` 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=1587028832608.72974@citrix.com \
--to=sergey.dyasli@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=dfaggioli@suse.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.