From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [PATCH v3 2/5] build: Hook the schedulers into
 Kconfig
Date: Fri, 8 Jan 2016 16:59:15 +0100
Message-ID: <1452268755.22760.49.camel@citrix.com>
References: <1452187761-38328-1-git-send-email-jonathan.creekmore@gmail.com>
	<1452187761-38328-3-git-send-email-jonathan.creekmore@gmail.com>
	<20160108154744.GE32260@char.us.oracle.com>
	<568FDBBA.8050103@citrix.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2756200722230031838=="
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <prvs=808f92ac5=dario.faggioli@citrix.com>)
	id 1aHZRk-0004MN-W3
	for xen-devel@lists.xenproject.org; Fri, 08 Jan 2016 15:59:25 +0000
In-Reply-To: <568FDBBA.8050103@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Andrew Cooper <andrew.cooper3@citrix.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, Jonathan Creekmore <jonathan.creekmore@gmail.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>, xen-devel@lists.xenproject.org
List-Id: xen-devel@lists.xenproject.org

--===============2756200722230031838==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="=-zd5QnIfJIY6F3w2ngtgQ"

--=-zd5QnIfJIY6F3w2ngtgQ
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2016-01-08 at 15:54 +0000, Andrew Cooper wrote:
> On 08/01/16 15:47, Konrad Rzeszutek Wilk wrote:
> >=C2=A0
> > And the hypervisor did build with:
> >=20
> > [konrad@char xen]$ nm --defined xen-syms |grep schedulers
> > ffff82d080290d58 D __end_schedulers_array
> > ffff82d080290d58 D __start_schedulers_array
> >=20
> > :-)
> >=20
> > Not exactly sure if there is some way to make us _not_ shoot
> > ourselves in the foot by mistake.
> >=20
> > Perhaps the build should complain if the size of the
> > __schedulers_array is zero?
>=20
> Hmm yes - an ASSERT() at the bottom of the linker file would be a
> very
> good defensive measure.
>=20
+1

> A hypervisor without any schedulers compiled in will be rather sad.
>=20
Well, it depends on how many pCPUs the host you want to run the
hypervisor on has: if it has 0 of them, no scheduler at all is the
perfect solution... not to mention that the combination of these things
(0 CPUs and no scheduling), would make a lot of issues just instantly
disappear! :-D

Regards,
Dario
--=C2=A0
<<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)


--=-zd5QnIfJIY6F3w2ngtgQ
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

iEYEABECAAYFAlaP3NMACgkQk4XaBE3IOsRnugCbBL0mzFjAsaDYAN2vraY4KVPh
JeQAmQFAvgc2667wzfirFkfKVpExZdB1
=iGCD
-----END PGP SIGNATURE-----

--=-zd5QnIfJIY6F3w2ngtgQ--


--===============2756200722230031838==
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

--===============2756200722230031838==--