All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Robert VanVossen <Robert.VanVossen@dornerworks.com>,
	"<xen-devel@lists.xen.org>" <xen-devel@lists.xen.org>,
	Joshua Whitehead <josh.whitehead@dornerworks.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: Clarifying the state of ARINC653 scheduler (and other components) in Xen 4.5 and beyond
Date: Mon, 8 Jun 2015 22:59:54 +0200	[thread overview]
Message-ID: <1433797194.2388.23.camel@citrix.com> (raw)
In-Reply-To: <3FDAE9EB-2D4C-41E2-83D9-B8A21609A267@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2132 bytes --]

On Mon, 2015-06-08 at 14:01 +0100, Lars Kurth wrote:
> > On 8 Jun 2015, at 13:19, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > 
> > In MAINTAINERS S: Supported means:
> > 
> > "Someone is actually paid to look after this.", which I think is
> > distinct from "This works well enough that the project is happy to
> > recommend it is used in production". It's a shame that Supported can be
> > taken to mean both things.
> > 
> > For reference Maintained is "Someone actually looks after it.".
> > 
> > Alternatively if someone can think of another way to express "paid
> > maintainer" we could switch to that.
>
> And then there is of course the question what we do with ARINC653. 
> 
Not sure we actually need to do something. The status in MAINTAINERS is
consistent with the existing semantic, as there's actually people
actively looking after the scheduler (and paid to do so, AFAIK).

Wrt the wiki page, the best way of capturing the state of things is,
basing on what's in there for the other schedulers, 'Supported' there
too. The scheduler has a very limited scope, and is useful only in a
handful of situations, and that's by design. But for those situations it
works pretty well, AFAIK.

Moreover, there is people in the community providing help to interested
users on how to set it up (there has been a thread on xen-users about
this rather recently).

Whether we should recommend to use it in production, well, I think we
could, of course for those people and only for them having a requirement
for compliance with the ARINC653 standard, which certainly is not the
most common thing around.

Whether it's actually being used in production by anyone, I don't
know... although they may not be allowed to say much/everything, maybe
Robbie and Josh could comment on this... but is this that relevant?

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-06-08 20:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 10:43 Clarifying the state of ARINC653 scheduler (and other components) in Xen 4.5 and beyond Lars Kurth
2015-06-08 12:00 ` Jan Beulich
2015-06-08 12:19   ` Ian Campbell
2015-06-08 13:01     ` Lars Kurth
2015-06-08 20:59       ` Dario Faggioli [this message]
2015-06-09  9:53         ` Jan Beulich
2015-06-10  9:42           ` Lars Kurth
2015-06-10  9:51             ` Jan Beulich
2015-06-10  9:51             ` Andrew Cooper
2015-06-11 16:14               ` Lars Kurth
2015-06-12 15:24               ` Lars Kurth

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=1433797194.2388.23.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Robert.VanVossen@dornerworks.com \
    --cc=josh.whitehead@dornerworks.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.