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 ARINC653 scheduler

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 1/1] Xen ARINC653 scheduler
From: Dulloor <dulloor@xxxxxxxxx>
Date: Tue, 6 Apr 2010 13:39:28 -0400
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Anthony Boorsma <Anthony.Boorsma@xxxxxxxxxxxxxxx>
Delivery-date: Tue, 06 Apr 2010 10:40:23 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xI2UnmcPOli0ZEbpGtasqOtJ0RShwH9ubXG8u5UotoQ=; b=DdEjR3L3rfAL5LQL84nKspIX+n9M6Mbr2JIhm/o8fnudmPw/TuWhLuD1xDDgMCw6gJ QFdLZuOIj5zkWSeQ54+FGWul3WtSe7GUtTaIYay3zCrcSDT1hZLYOsPMR0B1hDkhH0ov SpJapYbEmk0gqQB/aATJE6ez5FR4jUWpnEOww=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=IosojzflXZ9C2qRh3nQ8xLJ8EvtE9ctRMJ5whKAL3N9IJUFpy7OnOP9A9NNa54se9H J5BQxg60vvvH1cbwFUJdgebwbgjmsmkTAaO6DAb8tqP+QPedjv1HnWBpeGP9gENIGk/X mQ9S4vKORMAGg2CaCk2qhijf3G4hgFKCq1aMg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7E12C96.F733%keir.fraser@xxxxxxxxxxxxx>
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: <4BBB55DF.4010008@xxxxxxxxxxxxx> <C7E12C96.F733%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Anthony,

Can you provide a working scenario (script/tool for configuration,
workload, etc) that you used to test/verify this scheduler ? That
would be interesting.

-dulloor

On Tue, Apr 6, 2010 at 1:23 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> On 06/04/2010 16:40, "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx> wrote:
>
>> The simplest thing to do would be to modify the interface to
>> SCHEDOP_{get,put}_info such that if you passed DOMID_INVALID (or another
>> "magic" domain value), it would interpret the structure as global
>> settings rather than per-domain settings.
>>
>> The other option would be to make a SCHEDOP_{get,put}_global_info, which
>> would call a (newly created) .adjust_global callback through the generic
>> scheduler interface.
>>
>> Keir: Thoughts?
>
> I'd opt for the latter, but my preference is not that strong.
>
>  -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

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