From: Laszlo Ersek <lersek@redhat.com>
To: Jan Beulich <JBeulich@suse.com>,
Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
julien.grall@arm.com, Gary Lin <GLin@suse.com>,
edk2-devel-01 <edk2-devel@lists.01.org>,
xen-devel@lists.xenproject.org
Subject: Re: Is: Fix for 4MB BIOS payload in hvmloader. Was:Re: [edk2] [PATCH 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables)
Date: Tue, 23 May 2017 18:04:00 +0200 [thread overview]
Message-ID: <f8529e1d-ac16-d7f4-33be-8b085087f080__20339.908442884$1495555520$gmane$org@redhat.com> (raw)
In-Reply-To: <59246AD9020000780015C380@prv-mh.provo.novell.com>
On 05/23/17 17:01, Jan Beulich wrote:
>>>> On 23.05.17 at 16:12, <konrad@kernel.org> wrote:
>> On Thu, May 18, 2017 at 02:36:33PM +0200, Laszlo Ersek wrote:
>>> The situation is further hampered by the fact that Xen is (apparently)
>>> right at 4.9.0-rc5, so they likely won't commit Jan's hvmloader patch
>>> until Xen 4.9 is out. This is a problem for a potential TianoCore-side
>>> BZ because the delay will make us forget about the issue.
>
> The patch went in in time for rc6.
Thank you Jan for the speedy fix!
While reviewing version 2 of this patch set, Jordan wrote in
<https://lists.01.org/pipermail/edk2-devel/2017-May/010776.html>:
> With the understanding that we're holding off on the final patch for
> now to coordinate with Xen:
>
> Series Reviewed-by: Jordan Justen <jordan.l.justen at intel.com>
"the final patch" referenced there was:
[edk2] [PATCH v2 5/5] OvmfPkg: make the 4MB flash size the default
(again)
https://lists.01.org/pipermail/edk2-devel/2017-May/010763.html
So I have now modified the commit message on that patch, adding the
following paragraph:
> Xen gained support for the 4MB flash image in Xen commit 0d6968635ce5
> ("hvmloader: avoid tests when they would clobber used memory",
> 2017-05-19), which is part of Xen 4.9.0-rc6.
Seeing Gary's Tested-by on the Xen commit, I've also pushed the reworded
edk2 patch, as commit 1c47fcd465a4.
Thanks!
Laszlo
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-23 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170506193023.4767-1-lersek@redhat.com>
[not found] ` <20170508042759.kuut2vueabxvimwk@GaryWorkstation>
[not found] ` <20170512020215.jvnmgzvrgdv66ere@GaryWorkstation>
[not found] ` <12b9e870-30e4-8b88-9851-771d94264552@redhat.com>
[not found] ` <149489525952.434.10185839319642314352@jljusten-skl>
[not found] ` <20170516042034.hpf3fllcarzkgomh@GaryWorkstation>
[not found] ` <5abcc684-72e4-990b-0682-7c163a7fc9cf@redhat.com>
2017-05-23 14:12 ` Is: Fix for 4MB BIOS payload in hvmloader. Was:Re: [edk2] [PATCH 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables) Konrad Rzeszutek Wilk
[not found] ` <20170523141200.GB29008@localhost.localdomain>
2017-05-23 15:01 ` Jan Beulich
2017-05-23 16:04 ` Laszlo Ersek [this message]
2017-05-23 15:02 ` Julien Grall
2017-05-23 16:20 ` Laszlo Ersek
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='f8529e1d-ac16-d7f4-33be-8b085087f080__20339.908442884$1495555520$gmane$org@redhat.com' \
--to=lersek@redhat.com \
--cc=GLin@suse.com \
--cc=JBeulich@suse.com \
--cc=edk2-devel@lists.01.org \
--cc=jordan.l.justen@intel.com \
--cc=julien.grall@arm.com \
--cc=konrad@kernel.org \
--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.