WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add sup

To: Kathy Hadley <Kathy.Hadley@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Sat, 19 Jun 2010 12:14:14 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Sat, 19 Jun 2010 04:15:15 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=c8hXauQNQzZHNWbfFjvu+tEYYKQkgRytyo3QMHzlSpE=; b=HtM2vmNNQUGl78+gEwR6cElnxDIUiMG8ygjuWi/J85vo9n2251zcMdFVlPSDp5ugEm JLfWiB7vXaa21Juc4IgMyIbHkEfzdvNl+9p2pUOWQaixM00vR5s1U6X9bDtgUE4fKXtX /409bmQVOWGgGw1lJbVawz3oVpziSzTP+1wng=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=esEiKO2zwmoVeeY0ZL8eSUd5WgPSPv57Lf4NEL1FOTub5B1exzP0K5rwJnAngg98eT UiCp+XUxMY7P3GPGMoScyNkiBm+MIGHgp5mETmSe00w0Lgq2N83sEgGBPTtUWeU1tXEo RyPjJzrfeSHpJScpNub4X9fnzt7PtLyiHsr4Q=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <D3E384327F5C6D48AADCEA84160B7D730147120A@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <D3E384327F5C6D48AADCEA84160B7D7301470F73@xxxxxxxxxxxxxxx> <C83F8771.17B7B%keir.fraser@xxxxxxxxxxxxx> <D3E384327F5C6D48AADCEA84160B7D730147120A@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Jun 18, 2010 at 6:35 PM, Kathy Hadley
<Kathy.Hadley@xxxxxxxxxxxxxxx> 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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>