All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: "George Dunlap" <george.dunlap@eu.citrix.com>,
	"Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>,
	"Fabio Fantoni" <fabio.fantoni@heliman.it>,
	"David Vrabel" <david.vrabel@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: Xen 4.4 development update: RC0 imminent
Date: Thu, 5 Dec 2013 16:59:20 +0000	[thread overview]
Message-ID: <1386262760.20047.130.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <20131205164841.GB27631@zion.uk.xensource.com>

On Thu, 2013-12-05 at 16:48 +0000, Wei Liu wrote:

> > >>* Guest EFI booting (tianocore)
> > >>  - Wei Liu
> > >>
> > >A bunch of critical patches are neither applied upstream nor in our tree
> > >(though they are already acked / reviewed by maintainers), so I don't
> > >think we want to advertise it as "working"...
> > 
> > OK -- would the Xen side of these be something that could come in as
> > "bug fixes", or should I take this off the list of 4.4 features?
> >
> 
> I pinged maintainer this morning, let's see his response later. He's in
> GMT -8 timezone.
> 
> If we cannot get it merged within next week I would rather take it off
> our list.

IIRC the Xen side patches were pretty small and straight forward and the
only issue was agreeing the ABI for the struct passed from hvmloader to
ovmf.

Other than that lack of ABI agreement is there anything else which would
block taking the patches on our side. In particular do they break what
little functionality there is with the existing ovmf code base which we
pull in?

Ian.

  reply	other threads:[~2013-12-05 16:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 16:09 Xen 4.4 development update: RC0 imminent George Dunlap
2013-12-05 16:29 ` George Dunlap
2013-12-05 16:34   ` Wei Liu
2013-12-05 16:39     ` George Dunlap
2013-12-05 16:48       ` Wei Liu
2013-12-05 16:59         ` Ian Campbell [this message]
2013-12-05 17:06           ` Wei Liu
2013-12-05 17:16             ` Ian Campbell
2013-12-05 17:34               ` Wei Liu
2013-12-05 17:53                 ` George Dunlap
2013-12-05 18:03                   ` Wei Liu
2013-12-06  9:27                     ` Ian Campbell
2013-12-06 10:51                       ` Wei Liu
2013-12-05 16:39   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-05 16:41     ` George Dunlap
2013-12-05 16:42   ` Roger Pau Monné
2013-12-05 16:51     ` George Dunlap
2013-12-05 17:01       ` Lars Kurth
2013-12-05 17:04         ` George Dunlap
2013-12-05 20:06           ` Russell Pavlicek
2013-12-05 23:54             ` Sander Eikelenboom
2013-12-06  9:39             ` Lars Kurth
2013-12-06 12:14             ` George Dunlap
2013-12-05 16:59   ` David Vrabel
2013-12-05 17:05     ` George Dunlap
2013-12-05 17:40       ` Dario Faggioli
2013-12-05 17:07     ` George Dunlap
2013-12-05 17:01   ` Olaf Hering
2013-12-05 17:06     ` David Vrabel
2013-12-05 17:32   ` Dario Faggioli
2013-12-06 13:30   ` Fabio Fantoni
2013-12-05 16:34 ` Andrew Cooper
2013-12-06  9:07   ` Jan Beulich
2013-12-06 13:07     ` George Dunlap
2013-12-06 14:58       ` Jan Beulich
2013-12-05 16:54 ` George Dunlap
2013-12-16 10:50   ` 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=1386262760.20047.130.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=fabio.fantoni@heliman.it \
    --cc=george.dunlap@eu.citrix.com \
    --cc=phcoder@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.