xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tianyang Chen <tiche@seas.upenn.edu>
To: Dario Faggioli <dario.faggioli@citrix.com>,
	"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 13:10:56 -0500	[thread overview]
Message-ID: <56B0F130.4050605@seas.upenn.edu> (raw)
In-Reply-To: <1454401798.9227.22.camel@citrix.com>



On 2/2/2016 3:29 AM, Dario Faggioli wrote:
> 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.
>

Got it, thanks for the heads up.

--
Tianyang

      reply	other threads:[~2016-02-02 18:10 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
2016-02-02 18:10   ` Tianyang Chen [this message]

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=56B0F130.4050605@seas.upenn.edu \
    --to=tiche@seas.upenn.edu \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=mengxu@cis.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).