From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [PATCH] libxl: libxl_domain_sched_params_set case for ARINC 653 scheduler Date: Wed, 25 Jul 2012 00:48:34 +0200 Message-ID: <1343170114.13198.49.camel@Abyss> References: <857a035d6a4a835bb258.1343149194@arlpc33> <1343154690.13198.6.camel@Abyss> <8625277B-3B64-4473-A1AB-765E561DDC09@dornerworks.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1317155034840635696==" Return-path: In-Reply-To: <8625277B-3B64-4473-A1AB-765E561DDC09@dornerworks.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Kane Cc: george.dunlap@eu.citrix.com, "Ian.Campbell" , xen-devel@lists.xensource.com, Steve VanderLeest List-Id: xen-devel@lists.xenproject.org --===============1317155034840635696== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-ZsHFzLIFERroGaFyiHiX" --=-ZsHFzLIFERroGaFyiHiX Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2012-07-24 at 15:09 -0400, Andrew Kane wrote:=20 > >> +static int sched_arinc653_domain_set(libxl__gc *gc, uint32_t domid, > >> + const libxl_domain_sched_params = *scinfo) > >> +{ > >> + // Currently, the ARINC 653 scheduler does not take any domain-sp= ecific > >> + // configuration, so we simply return success. > >>=20 > > I think using C (/* */) style for comment is highly recommended, if not > > required. :-) >=20 > Oops. That's what I get for trusting the editor with comments. =3D) >=20 :-) > Our thought was to define this following the structure that exists for th= e > other schedulers, both for consistency and to facilitate future work > on the ARINC 653 scheduler. >=20 Yeah, I got that, and it's not bad thinking actually. Thinking a bit more about this, right below libxl_domain_sched_params_set() (in libxl.c) there is another function called libxl_domain_sched_params_get(), doing pretty much the same thing, although of course it retrieves instead of setting. Shouldn't you be doing something similar to that too? > If/when we actually need domain-specific configuration like this, > it would only involve changes in the sched_arinc653_domain_set > function, and wouldn't require any changes to > libxl_domain_sched_params_set. >=20 > If the preference is to hold off on implementing a > sched_arinc653_domain_set function until there's actually something > to put in it, I'm happy to change it. =3D) >=20 It's mostly a matter of taste I guess. The way I pointed is my preference, but I really don't care that much. If you send a patch with proper commenting (and perhaps dealing with the *_get() path), I'll ack it no matter if you have those empty functions or not... Which will then mean it'll be up to Goerge and Ian (added to the Cc list) to decide what they like better. :-) Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-ZsHFzLIFERroGaFyiHiX 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.4.12 (GNU/Linux) iEUEABECAAYFAlAPJkIACgkQk4XaBE3IOsTzhQCY010d9F6/E5EjjNHHnvywPb60 jgCgggkg8mQpF2ooJMWQo/yVPIihjBU= =LlMq -----END PGP SIGNATURE----- --=-ZsHFzLIFERroGaFyiHiX-- --===============1317155034840635696== 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 --===============1317155034840635696==--