From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [PATCH 09/16] xen: sched: close potential races when switching scheduler to CPUs Date: Wed, 6 Apr 2016 17:51:41 +0200 Message-ID: <1459957901.3166.87.camel@citrix.com> References: <20160318185524.8117.74837.stgit@Solace.station> <20160318190505.8117.89778.stgit@Solace.station> <56F2E8F7.4000200@citrix.com> <1459873591.3166.54.camel@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6615460159862596127==" Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1anpkV-0001xF-DC for xen-devel@lists.xenproject.org; Wed, 06 Apr 2016 15:52:07 +0000 In-Reply-To: <1459873591.3166.54.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: George Dunlap , xen-devel@lists.xenproject.org Cc: Tianyang Chen , Meng Xu List-Id: xen-devel@lists.xenproject.org --===============6615460159862596127== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-TeWRnsDCsDpkCfp2XXA1" --=-TeWRnsDCsDpkCfp2XXA1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2016-04-05 at 18:26 +0200, Dario Faggioli wrote: > On Wed, 2016-03-23 at 19:05 +0000, George Dunlap wrote: > > On 18/03/16 19:05, Dario Faggioli wrote: > > > This also means that, in Credit2 and RTDS, we can get rid > > > of the code that was doing the scheduler lock remapping > > > in csched2_free_pdata() and rt_free_pdata(), and of their > > > triggering ASSERT-s. > > >=20 > > > Signed-off-by: Dario Faggioli > > Similar to my comment before -- in my own tree I squashed patches > > 6-9 > > into a single commit and found it much easier to review. :-) > >=20 > I understand your point. >=20 > I'll consider doing something like this for v2 (that I'm just > finishing > putting together), but I'm not sure I like it. >=20 BTW, I changed my mind and, in the patch series I'm about to send, I did as you suggest and squashed these patches into one. :-) The changelog is indeed rather long, but still fine, IMO, and there's a lot less duplication, both in `git log' and in code (if one looks at it 'patches after patches', rather than just the final result). 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) --=-TeWRnsDCsDpkCfp2XXA1 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 v2 iEYEABECAAYFAlcFMI0ACgkQk4XaBE3IOsSQQQCfRRctxfzqZyaKZE5otZbpxmie 540An12FzdFT0HAfRO640V1xnI9iopmP =6ZLm -----END PGP SIGNATURE----- --=-TeWRnsDCsDpkCfp2XXA1-- --===============6615460159862596127== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --===============6615460159862596127==--