public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Gary Lin <glin@suse.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
	edk2-devel-01 <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables)
Date: Fri, 12 May 2017 10:40:34 +0200	[thread overview]
Message-ID: <12b9e870-30e4-8b88-9851-771d94264552@redhat.com> (raw)
In-Reply-To: <20170512020215.jvnmgzvrgdv66ere@GaryWorkstation>

On 05/12/17 04:02, Gary Lin wrote:
> On Mon, May 08, 2017 at 12:27:59PM +0800, Gary Lin wrote:
>> On Sat, May 06, 2017 at 09:30:18PM +0200, Laszlo Ersek wrote:
>>> (All hail Saturday!)
>>>
>>> Gary, can you please fetch this from my repo (URL & branch name below)
>>> and test it with Xen? Please test both the 4MB and the 2MB build. (I
>>> also tested both, with qemu + "-bios".)
>> Hi Laszlo,
>>
>> I have done some simples test with xen, and the 2MB build seems fine.
>> It booted into grub2 menu successfully. However, the 4MB build never boots.
>> The QEMU window showed less than 1 sec and then disappeared.
>>
>> Here is the snippet from 'xl dmesg'
>>
>> (d15)  - CPU0 ... 39-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
>> (d15) Testing HVM environment:
>> (d15)  - REP INSB across page boundaries ... passed
>> (d15)  - GS base MSRs and SWAPGS ... passed
>> (d15) Passed 2 of 2 tests
>> (d15) Writing SMBIOS tables ...
>> (d15) Loading OVMF ...
>> (d15) no BIOS ROM image found
>> (d15) *** HVMLoader bug at hvmloader.c:381
>> (d15) *** HVMLoader crashed.
>>
>> I'm pretty sure that the ovmf path is right, so it seems Xen just rejected
>> the 4MB build :-\
>>
>> I'll try to dig more information.
>>
> There is a function in the xen hvmloader clearing the memory from
> 0x400000 to 0x800000. Unfortunately, the hvm_start_info struct of the
> 4MB OVMF was loaded to 0x588000, so the struct was cleared mistakenly
> and hvmloader cannot find the firmware. Xen is not ready for the 4MB
> build yet :-\
> 
> The discussion in xen-devel:
> https://lists.xen.org/archives/html/xen-devel/2017-05/msg01053.html

Thank you for the feedback!

In this case, I think we should drop the last patch from this series.

However, your test results also confirm that the 2MB build continues to
work with Xen, which means that the reworking of the
EmuVariableFvbRuntimeDxe driver in this series, and the underlying
tweaks+cleanups series, cause no regression.

Can you please respond, with your "Regression-tested-by", to:

(1) the full series

  [edk2] [PATCH 0/7] OvmfPkg: small cleanups and tweaks

(2) and patches 1 through 3 in this series? (Patch #4 is just
documentation, for which Tested-by would be strange.)

Thank you!
Laszlo


>>> Note: this series depends on:
>>>
>>>   [edk2] [PATCH 0/7] OvmfPkg: small cleanups and tweaks
>>>   https://lists.01.org/pipermail/edk2-devel/2017-May/010527.html
>>>
>>> and it has been pushed to my github repo as such.
>>>
>>> Repo:   https://github.com/lersek/edk2.git
>>> Branch: emu4k
>>>
>>> Cc: Gary Ching-Pang Lin <glin@suse.com>
>>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>>>
>>> Thanks,
>>> Laszlo
>>>
>>> Laszlo Ersek (5):
>>>   OvmfPkg/EmuVariableFvbRuntimeDxe: strip trailing whitespace
>>>   OvmfPkg/EmuVariableFvbRuntimeDxe: change block size to 4KB
>>>   OvmfPkg/PlatformPei: align EmuVariableNvStore at any page boundary
>>>   OvmfPkg/README: document 4MB flash layout
>>>   OvmfPkg: make the 4MB flash size the default (again)
>>>
>>>  OvmfPkg/OvmfPkgIa32.dsc                |   2 +-
>>>  OvmfPkg/OvmfPkgIa32X64.dsc             |   2 +-
>>>  OvmfPkg/OvmfPkgX64.dsc                 |   2 +-
>>>  OvmfPkg/EmuVariableFvbRuntimeDxe/Fvb.h |  26 ++-
>>>  OvmfPkg/EmuVariableFvbRuntimeDxe/Fvb.c | 191 +++++++++-----------
>>>  OvmfPkg/PlatformPei/Platform.c         |  20 +-
>>>  OvmfPkg/README                         |  39 +++-
>>>  7 files changed, 143 insertions(+), 139 deletions(-)
>>>
>>> -- 
>>> 2.9.3
>>>
>>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
>>



  reply	other threads:[~2017-05-12  8:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06 19:30 [PATCH 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables) Laszlo Ersek
2017-05-06 19:30 ` [PATCH 1/5] OvmfPkg/EmuVariableFvbRuntimeDxe: strip trailing whitespace Laszlo Ersek
2017-05-12  9:07   ` Gary Lin
2017-05-06 19:30 ` [PATCH 2/5] OvmfPkg/EmuVariableFvbRuntimeDxe: change block size to 4KB Laszlo Ersek
2017-05-12  9:07   ` Gary Lin
2017-05-15 23:50   ` Jordan Justen
2017-05-06 19:30 ` [PATCH 3/5] OvmfPkg/PlatformPei: align EmuVariableNvStore at any page boundary Laszlo Ersek
2017-05-12  9:08   ` Gary Lin
2017-05-06 19:30 ` [PATCH 4/5] OvmfPkg/README: document 4MB flash layout Laszlo Ersek
2017-05-06 19:30 ` [PATCH 5/5] OvmfPkg: make the 4MB flash size the default (again) Laszlo Ersek
2017-05-08  4:27 ` [PATCH 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables) Gary Lin
2017-05-12  2:02   ` Gary Lin
2017-05-12  8:40     ` Laszlo Ersek [this message]
2017-05-16  0:40       ` Jordan Justen
2017-05-16  4:20         ` Gary Lin
2017-05-18 12:36           ` Laszlo Ersek
2017-05-23 14:12             ` Is: Fix for 4MB BIOS payload in hvmloader. Was:Re: " Konrad Rzeszutek Wilk
     [not found]               ` <59246AD9020000780015C380@prv-mh.provo.novell.com>
2017-05-23 16:04                 ` Laszlo Ersek
     [not found]               ` <6af13bb5-0bfb-c9e3-e9fe-d1361d851e7d@arm.com>
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-list 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=12b9e870-30e4-8b88-9851-771d94264552@redhat.com \
    --to=devel@edk2.groups.io \
    /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