From: Dario Faggioli <raistlin@linux.it>
To: Andrew Kane <Andrew.Kane@dornerworks.com>
Cc: george.dunlap@eu.citrix.com, xen-devel@lists.xensource.com,
Steve.VanderLeest@dornerworks.com, Ian.Campbell@citrix.com
Subject: Re: [PATCH v2] libxl: libxl_domain_sched_params_set case for ARINC 653 scheduler
Date: Wed, 25 Jul 2012 17:48:11 +0200 [thread overview]
Message-ID: <1343231291.21187.6.camel@Abyss> (raw)
In-Reply-To: <c6d90859a30a996ac524.1343230932@arlpc33>
[-- Attachment #1.1: Type: text/plain, Size: 1609 bytes --]
On Wed, 2012-07-25 at 11:42 -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.
>
> Signed-off-by: Andrew Kane <Andrew.Kane@dornerworks.com>
>
Hi again Andrew,
> 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;
>
I don't know if you've seen it, as I said it in my second e-mail, while
replying to you, so I'm asking here again. Is it ok that you need to do
this for libxl_domain_sched_params_set() bit *NOT* for
libxl_domain_sched_params_get()? If it is, sorry for bothering... If
not, you probably should add that too. :-)
To me it seems it could be needed, but it might well be me not knowing
enough of ARINC's interface. :-P
Thanks and 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-25 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 15:42 [PATCH v2] libxl: libxl_domain_sched_params_set case for ARINC 653 scheduler Andrew Kane
2012-07-25 15:45 ` Ian Campbell
2012-07-25 16:41 ` Ian Campbell
2012-07-25 15:48 ` Dario Faggioli [this message]
2012-07-25 18:11 ` Andrew Kane
2012-07-25 22:11 ` Dario Faggioli
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=1343231291.21187.6.camel@Abyss \
--to=raistlin@linux.it \
--cc=Andrew.Kane@dornerworks.com \
--cc=Ian.Campbell@citrix.com \
--cc=Steve.VanderLeest@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).