From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: RT-Xen on ARM Date: Wed, 12 Jul 2017 08:13:01 +0200 Message-ID: <1499839981.7756.11.camel@citrix.com> References: <88185ae6-d1cf-898c-fe18-a569b0049230@epam.com> <1499243394.7486.5.camel@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3824201503979961433==" Return-path: Received: from mail6.bemta6.messagelabs.com ([193.109.254.103]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dVAtX-0005re-Bb for xen-devel@lists.xenproject.org; Wed, 12 Jul 2017 06:13:07 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Meng Xu Cc: xen-devel , Andrii Anisov List-Id: xen-devel@lists.xenproject.org --===============3824201503979961433== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="=-oKnGCDEEfYM7ydYYLnt/" --=-oKnGCDEEfYM7ydYYLnt/ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2017-07-07 at 14:29 -0400, Meng Xu wrote: > On Wed, Jul 5, 2017 at 4:29 AM, Dario Faggioli > wrote: > >=20 > The total utilization can help answer if the VCPU parameters are > feasible or not. > I'm just saying that we could keep track of utilization and, if on an host with N CPUs, we reach more than (N*100)%, we can warn the user that deadlines will be missed. This is a simple enough check, and it can live in the hypervisor. > But I'm thinking there may exist a better (yet optimal) approach to > answer the question: If all VCPUs on K cores are globally scheduled > or > completely partitioned onto each of the K cores, we can use > Utilization Bound of the EDF scheduling algorithm for checking if the > VCPU's performance can be safely provided. > This requires the VCPUs' parameters (which also computes the total > utilization), which are easy to get. >=20 I know there's math we can use, I'm just saying we don't want that in Xen. > Another thing is where this schedulability check should be provided: > in Xen kernel, in Xen toolstack, or as a separate utility tool? > In my opinion, a separate utility tool seems to be better than the > other tool approaches? >=20 Exactly. As said above, you don't put something as complex as that inside Xen. It can well live in toolstack, IMO, as far as we also add a (global, non per-domain) for telling whether we want admission or control not. Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-oKnGCDEEfYM7ydYYLnt/ 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 iQIcBAABCAAGBQJZZb3tAAoJEBZCeImluHPuJg0P/2w/EgxFXtnTmYEO+ZjR0dnE vU5behiRCdfo8T9NuOpBhfIkt3KvLbL4jS6kswU05XLyvmfzddzKr3kxRHB62z3d O37brGQEiehcAKMSvmoAI171E0i7bF0PK7PvsTFvjlv+gHSz55mx6LmVks7gKaIx j9W2Imk/8McKbgHoZiYBNdv+kUjpj0MYKpluBUq32MZpo4ArwvadMSbzGDIwcI3A PJyNKR+4owQQdpr91lux5swE5/LZJNmyP7DswM+le8GICtDhRM4ebwvJKNWJBveJ EpN8Whnon21Mtlx+DPWkR6S5kfqmw3raSE1siMbQWJ5ZHCO/Hi/EbJjLwnmQE692 ab/hP41Pp1vkMSnq03i8MEZ3MBidZjzCj6jA9M4IM+cgESZFKL5ubibPOz67UQTK SIR7RcSzEPRj1QYntIcpttBqc4pSolWBo6kT1yUtwOuHu0b/jcgCpIye15h3RXbn PSMSA7ZcOoqC/NUaDRdXgdwal6/I5vl3jH56se7eR5nBm48GMv8UTWSG/rXKoCT3 7NHzJTYrv66pEA/+Bt2Wpb0qENa8HJYIft41XZGPEUzibFNonD2igO/CYqk1U8Ba Wwy1H11oJQG19/mhkhKkvpEzD+8jmCzB6W6OgVhnUhe4PXMWFMR87qptOkAAAfnN T9RGYy/J9m8KpyF8KaiI =oMSk -----END PGP SIGNATURE----- --=-oKnGCDEEfYM7ydYYLnt/-- --===============3824201503979961433== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============3824201503979961433==--