xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Doug Goldstein <cardoe@cardoe.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Rich Persaud <persaur@gmail.com>,
	Committers <committers@xenproject.org>,
	Anthony Liguori <aliguori@amazon.com>,
	"security@xen.org" <security@xen.org>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: Radical proposal v2: Publish Amazon's verison now, Citrix's version soon
Date: Thu, 11 Jan 2018 11:59:00 -0500	[thread overview]
Message-ID: <20180111165900.GZ29272@char.us.oracle.com> (raw)
In-Reply-To: <72ad1fd7-f24b-01c3-ca2b-24a4ccffd191@citrix.com>

On Thu, Jan 11, 2018 at 03:17:45PM +0000, George Dunlap wrote:
> On 01/10/2018 01:34 PM, George Dunlap wrote:
> > * Executive summary
> > 
> > - We've agreed on a "convergence" point for PV shim functionality that
> >   covers as many users as possible:
> >  - 'HVM' functionality: boots in HVM mode, has support for Xen 3.4
> >    event channels, &c, booted via 'sidecar'
> >  - 'PVH' functionality: boots in PVH mode, booted via toolstack
> >    changes
> > 
> > - "Vixen" (the Amazon shim) and PVH shim (mostly developed by Citrix)
> >   each cover some users and not others; neither one (yet) covers all
> >   users
> 
> Proposed codenames we can use for shorthand:
> 
> "Vixen": Amazon's HVM+sidecar shim solution
> "Comet": Citrix's PVH+toolstack shim solution
> "Rudolph": Long-term solution combining both
> 
> In the Xen mythos then, Rudolph could be the child of Vixen and Comet. :-)

<groans>

> 
> Cultural references (given that 'Vixen' and 'Comet' were both developed
> in the run up to Christmas):
> 
> * https://www.teachervision.com/twas-night-christmas-full-text
> *
> http://www.metrolyrics.com/rudolph-the-red-nosed-reindeer-lyrics-christmas-carols.html
> 
>  -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      reply	other threads:[~2018-01-11 16:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 13:34 Radical proposal v2: Publish Amazon's verison now, Citrix's version soon George Dunlap
2018-01-10 13:50 ` Jan Beulich
2018-01-10 14:40   ` Anthony Liguori
2018-01-10 16:39     ` Radical proposal v2: Publish Amazon's verison now, Citrix's version soon [and 1 more messages] Ian Jackson
2018-01-10 16:44       ` Roger Pau Monné
2018-01-10 16:48       ` George Dunlap
2018-01-10 16:50       ` Jan Beulich
2018-01-10 13:51 ` Radical proposal v2: Publish Amazon's verison now, Citrix's version soon Juergen Gross
2018-01-10 14:38   ` Lars Kurth
2018-01-10 18:38   ` Anthony Liguori
2018-01-10 17:25 ` Stefano Stabellini
2018-01-11  8:12   ` Jan Beulich
2018-01-11 16:23     ` Stefano Stabellini
2018-01-11 16:28       ` George Dunlap
2018-01-11 16:36         ` Stefano Stabellini
2018-01-11 16:52           ` Rich Persaud
2018-01-11 16:55             ` George Dunlap
2018-01-11 16:56             ` Stefano Stabellini
2018-01-11 17:06               ` Jan Beulich
2018-01-11 15:17 ` George Dunlap
2018-01-11 16:59   ` Konrad Rzeszutek Wilk [this message]

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=20180111165900.GZ29272@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=aliguori@amazon.com \
    --cc=cardoe@cardoe.com \
    --cc=committers@xenproject.org \
    --cc=george.dunlap@citrix.com \
    --cc=persaur@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=security@xen.org \
    --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 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).