From: George Dunlap <george.dunlap@eu.citrix.com>
To: Keir Fraser <Keir.Fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Anthony Boorsma <Anthony.Boorsma@dornerworks.com>
Subject: Re: [PATCH 1/1] Xen ARINC653 scheduler
Date: Tue, 13 Apr 2010 14:53:45 +0100 [thread overview]
Message-ID: <4BC47769.3010404@eu.citrix.com> (raw)
In-Reply-To: <C7E12C96.F733%keir.fraser@eu.citrix.com>
Anthony, if you rework the patch to make a new .adjust_global callback
in the generic scheduler interface, and a new
SCHEDOP_{get,put}_global_info, I'll support merging the new scheduler.
Let me know if you need any help or clarification.
-George Dunlap
Keir Fraser wrote:
> On 06/04/2010 16:40, "George Dunlap" <George.Dunlap@eu.citrix.com> 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
>
>
>
next prev parent reply other threads:[~2010-04-13 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 20:23 [PATCH 1/1] Xen ARINC653 scheduler Anthony Boorsma
2010-03-25 0:18 ` George Dunlap
2010-03-30 22:33 ` Anthony Boorsma
2010-03-31 10:54 ` George Dunlap
2010-03-31 10:56 ` George Dunlap
2010-04-06 14:37 ` Anthony Boorsma
2010-04-06 15:40 ` George Dunlap
2010-04-06 17:23 ` Keir Fraser
2010-04-06 17:39 ` Dulloor
2010-04-13 13:53 ` George Dunlap [this message]
2010-03-31 9:04 ` HongWoo Lee
2010-04-13 13:18 ` Anthony Boorsma
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=4BC47769.3010404@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Anthony.Boorsma@dornerworks.com \
--cc=Keir.Fraser@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.