All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH] Config.mk: update OVMF changeset
Date: Mon, 9 Dec 2013 11:17:24 +0000	[thread overview]
Message-ID: <52A5A6C4.40907@eu.citrix.com> (raw)
In-Reply-To: <20131209111046.GG32155@zion.uk.xensource.com>

On 12/09/2013 11:10 AM, Wei Liu wrote:
> On Mon, Dec 09, 2013 at 11:04:23AM +0000, George Dunlap wrote:
>> On 12/08/2013 08:50 PM, Wei Liu wrote:
>>> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
>>> Cc: Ian Campbell <ian.campbell@citrix.com>
>>> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
>>> Cc: George Dunlap <george.dunlap@eu.citrix.com>
>> This lacks a description of what the effect will be of updating to
>> this changeset.  I'm guessing that the OVMF side of your recent
>> fixes have gotten checked in?
>>
> Yes, necessary patches to integrate OVMF with Xen is upstreamed now.
>
> The original changeset in Config.mk:
> 1. doesn't work with guest > 4G ram
> 2. messes up PCI resource mapping
>
> The version of OVMF fixes those bugs and works well for me.

re the interface, we generally plan on building OVMF ourselves, right?  
I don't think the interface between Xen and OVMF necessarily needs to be 
stable at this point.

In any case, the interface changes are already in Xen; this doesn't make 
the interface available, it just makes it easier for people to build OVMF.

Release-acked-by: George Dunlap <george.dunlap@eu.citrix.com>

  reply	other threads:[~2013-12-09 11:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08 20:50 [PATCH] Config.mk: update OVMF changeset Wei Liu
2013-12-09 11:04 ` George Dunlap
2013-12-09 11:10   ` Wei Liu
2013-12-09 11:17     ` George Dunlap [this message]
2013-12-09 11:33       ` Ian Campbell
2013-12-09 15:46       ` Ian Campbell
2015-10-14 11:41 Wei Liu
2015-10-22 15:55 ` Ian Campbell
2015-10-22 15:58   ` Ian Jackson
2015-10-22 16:02     ` Wei Liu
2015-10-22 16:09     ` Ian Campbell
2015-10-22 16:11       ` Stefano Stabellini
2015-10-22 17:08         ` Ian Jackson
2015-10-23  8:01           ` Jan Beulich
2015-10-23  9:11             ` Ian Campbell
2015-10-23 10:08               ` Stefano Stabellini
2015-10-23 11:18                 ` Ian Jackson
2015-10-23 11:38                   ` Stefano Stabellini
2015-10-23 11:56                     ` Ian Jackson
2015-10-23 11:52                   ` Jan Beulich
2015-10-23 12:16                   ` Ian Campbell
2015-10-23 12:43                     ` Stefano Stabellini
2015-10-23 12:56                       ` Ian Campbell
2015-10-23 13:16                         ` Fabio Fantoni
2015-10-23 13:38                           ` Ian Campbell
2015-11-12 10:06 Wei Liu
2015-11-16 12:08 ` Ian Campbell
2015-11-16 12:10   ` Wei Liu
2017-03-23 17:10 Anthony PERARD
2017-09-22 17:20 Anthony PERARD
2017-09-25  7:31 ` Jan Beulich
2017-09-25 14:20   ` Dario Faggioli
2018-07-25 14:38 Anthony PERARD
2020-08-12  9:55 Wei Liu

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=52A5A6C4.40907@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.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.