From: Dario Faggioli <dario.faggioli@citrix.com>
To: Tianyang Chen <tiche@seas.upenn.edu>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
George Dunlap <george.dunlap@citrix.com>,
Meng Xu <mengxu@cis.upenn.edu>
Subject: Re: [Bug] sched: credit2: Assertion failed
Date: Tue, 2 Feb 2016 09:29:58 +0100 [thread overview]
Message-ID: <1454401798.9227.22.camel@citrix.com> (raw)
In-Reply-To: <56B04A3D.1040209@seas.upenn.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1724 bytes --]
On Tue, 2016-02-02 at 01:18 -0500, Tianyang Chen wrote:
> The following script caused an unresponsive dom0 and it can not be
> reproduced all the time. The dom0 is using credit2 scheduler.
>
> #!/bin/bash
> xl cpupool-list -c
> xl cpupool-cpu-remove Pool-0 3
> xl cpupool-cpu-remove Pool-0 2
> xl cpupool-create name=\"r\" sched=\"credit\"
> xl cpupool-create name=\"t\" sched=\"credit\"
> xl cpupool-cpu-add r 3
> xl cpupool-cpu-add t 2
>
Yes, this is known. It is because Credit2 does not support (hard)
affinity. There is a series on the list by someone implementing that,
but it needs refreshing, which I hope to get round to it soon.
> Another bug can be reproduced(not all the time) if the newly created
> pool is also credit2. There is an assertion failure (see bug.txt),
> which
> is essentially the same thing I got when trying to make the new rtds
> scheduler cpupool safe.
>
This is also known, and it will be fixed when I'll get back and
resubmit this:
http://lists.xenproject.org/archives/html/xen-devel/2015-09/msg03811.html
In fact, look at this patch:
http://lists.xenproject.org/archives/html/xen-devel/2015-09/msg03813.html
And I'll do that right in this days, so I'd say you can ignore this for
RTDS (as it will get fixed by the same series).
So both are known issues... I'll open bugs in our bugtraker for them to
avoid forgetting or tripping over them again.
Thanks and Regards,
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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-02 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 6:18 [Bug] sched: credit2: Assertion failed Tianyang Chen
2016-02-02 8:29 ` Dario Faggioli [this message]
2016-02-02 18:10 ` Tianyang Chen
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=1454401798.9227.22.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=mengxu@cis.upenn.edu \
--cc=tiche@seas.upenn.edu \
--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 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).