xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Kathy Hadley <Kathy.Hadley@dornerworks.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
Date: Fri, 18 Jun 2010 18:49:10 +0100	[thread overview]
Message-ID: <C8417026.17EE1%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <D3E384327F5C6D48AADCEA84160B7D730147120A@mcbain.dw.local>

On 18/06/2010 18:35, "Kathy Hadley" <Kathy.Hadley@dornerworks.com> wrote:

> 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 would be passed in to you?

Or if you don't care about cpu pools you can just set it to zero. That's the
default cpupool created at boot time which all CPUs are bound to by default.

 -- Keir

  reply	other threads:[~2010-06-18 17:49 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 15:04 [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools) Kathy Hadley
2010-06-16 15:50 ` George Dunlap
2010-06-16 16:00   ` Kathy Hadley
2010-06-16 16:13     ` Keir Fraser
2010-06-16 16:14     ` George Dunlap
2010-06-16 16:20       ` Keir Fraser
2010-06-16 16:25         ` Kathy Hadley
2010-06-16 16:31           ` Keir Fraser
2010-06-16 16:40             ` Kathy Hadley
2010-06-16 16:49               ` Keir Fraser
2010-06-16 18:03                 ` Kathy Hadley
2010-06-17  7:04                   ` Keir Fraser
2010-06-17 18:16                     ` Kathy Hadley
2010-06-17 18:26                       ` Keir Fraser
2010-06-18 17:35                     ` Kathy Hadley
2010-06-18 17:49                       ` Keir Fraser [this message]
2010-06-19 11:14                       ` George Dunlap
2010-06-22 19:10                     ` Kathy Hadley
2010-06-22 19:16                       ` Keir Fraser
2010-06-23 19:57                         ` Kathy Hadley
2010-06-23 20:23                           ` Keir Fraser
2010-06-23 21:16                             ` Kathy Hadley
2010-06-23 22:36                               ` Keir Fraser
2010-06-24 12:53                                 ` Kathy Hadley
2010-06-24 13:08                                   ` Dan Magenheimer
2010-06-24 13:18                                     ` Kathy Hadley
2010-06-24 13:23                                     ` Keir Fraser
2010-06-24 13:32                                       ` Kathy Hadley
2010-06-30 20:44                                 ` Kathy Hadley
2010-06-30 20:54                                   ` Keir Fraser
2010-07-14 17:32                                     ` Kathy Hadley
2010-07-14 18:04                                       ` Keir Fraser
2010-06-16 16:25         ` George Dunlap
2010-06-17  5:02         ` Juergen Gross
2010-06-17  6:09           ` Keir Fraser

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=C8417026.17EE1%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Kathy.Hadley@dornerworks.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).