Re: [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)

[George Dunlap <George.Dunlap@eu.citrix.com>]

On Fri, Jun 18, 2010 at 6:35 PM, Kathy Hadley
<Kathy.Hadley@dornerworks.com> wrote:
> I migrated to c/s 21632 in the staging tree.  I see that xen_sysctl_scheduler_op in sysctl.h was updated in c/s 21626 to add cpupool_id to the structure.  I call the following function from an application executing in Dom0 to adjust the ARINC 653 schedule:
>
> xc_sched_arinc653_sched_set(
>    xc_interface *xch,
>    xen_sysctl_sched_arinc653_schedule_t * sched)
> {
>    DECLARE_SYSCTL;
>
>    sysctl.cmd = XEN_SYSCTL_scheduler_op;
>    sysctl.u.scheduler_op.sched_id = XEN_SCHEDULER_ARINC653;
>    sysctl.u.scheduler_op.cmd = XEN_SYSCTL_SCHEDOP_putinfo;
>    set_xen_guest_handle(sysctl.u.scheduler_op.u.arinc653.schedule, sched);
>
>    return do_sysctl(xch, &sysctl);
> }
>
> In this function, which executes in Dom0, how do I determine the cpupool_id that I need to set in the sysctl data structure?

It should take a cpupool_id argument.  It may be that you're the only
consumer of this scheduler, and that your toolstack will always pass a
cpupool_id of 0 (the pool created by default on boot).  But on the off
chance that someone decides they want to make two pools, one of which
will use your scheduler, we want them to be able to specify one. :-)

 -George