From: Andrew Kane <Andrew.Kane@dornerworks.com>
To: xen-devel@lists.xensource.com
Cc: george.dunlap@eu.citrix.com
Subject: [PATCH] libxl: libxl_domain_sched_params_set case for ARINC 653 scheduler
Date: Tue, 24 Jul 2012 12:59:54 -0400 [thread overview]
Message-ID: <857a035d6a4a835bb258.1343149194@arlpc33> (raw)
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.
Signed-off-by: Andrew Kane <Andrew.Kane@dornerworks.com>
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.
+ return 0;
+}
+
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;
default:
LOG(ERROR, "Unknown scheduler");
ret=ERROR_INVAL;
next reply other threads:[~2012-07-24 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 16:59 Andrew Kane [this message]
2012-07-24 18:31 ` [PATCH] libxl: libxl_domain_sched_params_set case for ARINC 653 scheduler Dario Faggioli
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=857a035d6a4a835bb258.1343149194@arlpc33 \
--to=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).