From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [Bug] sched: credit2: Assertion failed Date: Tue, 2 Feb 2016 09:29:58 +0100 Message-ID: <1454401798.9227.22.camel@citrix.com> References: <56B04A3D.1040209@seas.upenn.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3713216161800465167==" Return-path: In-Reply-To: <56B04A3D.1040209@seas.upenn.edu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tianyang Chen , "xen-devel@lists.xen.org" , George Dunlap , Meng Xu List-Id: xen-devel@lists.xenproject.org --===============3713216161800465167== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-2FdlD1iZ0HE8KHjHTdNe" --=-2FdlD1iZ0HE8KHjHTdNe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2016-02-02 at 01:18 -0500, Tianyang Chen wrote: > The following script caused an unresponsive dom0 and it can not be=C2=A0 > reproduced all the time. The dom0 is using credit2 scheduler. >=20 > #!/bin/bash > xl cpupool-list -c > xl cpupool-cpu-remove Pool-0 3 > xl cpupool-cpu-remove Pool-0 2 > xl cpupool-create name=3D\"r\" sched=3D\"credit\" > xl cpupool-create name=3D\"t\" sched=3D\"credit\" > xl cpupool-cpu-add r 3 > xl cpupool-cpu-add t 2 >=20 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=C2= =A0 > pool is also credit2. There is an assertion failure (see bug.txt), > which=C2=A0 > is essentially the same thing I got when trying to make the new rtds=C2= =A0 > scheduler cpupool safe. >=20 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 --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-2FdlD1iZ0HE8KHjHTdNe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlawaQYACgkQk4XaBE3IOsSroQCggSu5XtYlxqiPFjZQE/agvtIV GJMAn1tu146mziPS4lYcJUb/h7pr1wYU =AXgw -----END PGP SIGNATURE----- --=-2FdlD1iZ0HE8KHjHTdNe-- --===============3713216161800465167== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============3713216161800465167==--