From: Dario Faggioli <raistlin@linux.it>
To: Andrew Kane <Andrew.Kane@dornerworks.com>
Cc: george.dunlap@eu.citrix.com, xen-devel@lists.xensource.com
Subject: Re: [PATCH] libxl: libxl_domain_sched_params_set case for ARINC 653 scheduler
Date: Tue, 24 Jul 2012 20:31:30 +0200 [thread overview]
Message-ID: <1343154690.13198.6.camel@Abyss> (raw)
In-Reply-To: <857a035d6a4a835bb258.1343149194@arlpc33>
[-- Attachment #1.1: Type: text/plain, Size: 2392 bytes --]
Hi Andrew,
On Tue, 2012-07-24 at 12:59 -0400, Andrew Kane wrote:
> Implements sched_arinc653_domain_set to match the existing API. Currently,
> there is no domain-specific configuration when using the ARINC 653 scheduler,
> so we simply return success.
>
Cool, thanks for doing this. I've only a small question...
> diff -r 4a28c496acbf -r 857a035d6a4a tools/libxl/libxl.c
> --- a/tools/libxl/libxl.c Mon Jul 23 17:58:33 2012 +0100
> +++ b/tools/libxl/libxl.c Tue Jul 24 11:41:39 2012 -0400
> @@ -3642,6 +3642,14 @@ libxl_scheduler libxl_get_scheduler(libx
> return sched;
> }
>
> +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-specific
> + // configuration, so we simply return success.
>
I think using C (/* */) style for comment is highly recommended, if not
required. :-)
> + return 0;
> +}
> +
>
It's certainly not a bit deal, and the compiler might be doing this on
its own already but, as the function doesn't actually do anything, why
not putting the comment down in the switch [*]?
That way we still avoid LIBXL_SCHEDULING_ARNIC653 being caught by the
default: clause and resulting in an error, but without introducing an
empty function that might look confusing.
If in future there will be the need for a specific
sched_arnic653_domain_set function, we can add it then.
> static int sched_credit_domain_get(libxl__gc *gc, uint32_t domid,
> libxl_domain_sched_params *scinfo)
> {
> @@ -3909,6 +3917,9 @@ int libxl_domain_sched_params_set(libxl_
> case LIBXL_SCHEDULER_CREDIT2:
> ret=sched_credit2_domain_set(gc, domid, scinfo);
> break;
> + case LIBXL_SCHEDULER_ARINC653:
> + ret=sched_arinc653_domain_set(gc, domid, scinfo);
> + break;
>
[*] I mean right here... :-)
> default:
> LOG(ERROR, "Unknown scheduler");
> ret=ERROR_INVAL;
>
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-07-24 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 16:59 [PATCH] libxl: libxl_domain_sched_params_set case for ARINC 653 scheduler Andrew Kane
2012-07-24 18:31 ` Dario Faggioli [this message]
2012-07-24 19:09 ` Andrew Kane
2012-07-24 22:48 ` Dario Faggioli
2012-07-25 8:59 ` Ian Campbell
2012-07-25 9:15 ` George Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1343154690.13198.6.camel@Abyss \
--to=raistlin@linux.it \
--cc=Andrew.Kane@dornerworks.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).