From: "Richard W.M. Jones" <rjones@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
"Gabriel L. Somlo" <gsomlo@gmail.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jordan Justen <jordan.l.justen@intel.com>,
Xiang Zheng <xiang.zheng@linaro.org>
Subject: Re: [PATCH 0/5] ArmVirtPkg, OvmfPkg: improve firmware duration of direct kernel boot
Date: Fri, 16 Mar 2018 08:57:09 +0000 [thread overview]
Message-ID: <20180316085709.GX2787@redhat.com> (raw)
In-Reply-To: <20180315190258.6580-1-lersek@redhat.com>
On Thu, Mar 15, 2018 at 08:02:53PM +0100, Laszlo Ersek wrote:
> (Copying Rich, Xiang and Gabriel for testing requests below.)
>
> Repo: https://github.com/lersek/edk2.git
> Branch: kernel_before_bootdevs
>
> After the recent series "OvmfPkg, ArmVirtQemu: leaner platform BDS
> policy for connecting devices", I'm picking up another earlier idea -- a
> direct kernel boot does not need devices such as disks and NICs to be
> bound by UEFI.
>
> I tested this series extensively on QEMU, in OVMF (IA32X64) and
> ArmVirtQemu (AARCH64), both with and without direct kernel boot. I
> compared the logs in all sensible relations within a given architecture.
>
> Rich, can you please test this on ARM64, with guestfish/libguestfs?
> Please attach a good number of disks at once on the command line, and
> compare the appliance's boot time between (e.g.) RHEL7's
> "/usr/share/AAVMF/AAVMF_CODE.fd" and the following binary (after
> decompression):
>
> https://people.redhat.com/lersek/kernel_before_bootdevs-991e2f2f-64cf-4566-b933-919928e2aa6b/QEMU_EFI.fd.padded.xz
I tested this on Fedora Rawhide (aarch64) with:
kernel-core-4.16.0-0.rc5.git1.2.fc29.aarch64 (host & guest)
qemu-2.11.0-5.fc29.aarch64
edk2-aarch64-20171011git92d07e4-2.fc28.noarch
libguestfs-1.39.1-1.fc29.aarch64
I used the /usr/bin/libguestfs-boot-benchmark tool from
libguestfs-benchmarking-1.39.1-1.fc29.aarch64
As a baseline, on my mid-range Intel i7 laptop (note that this number
is NOT comparable to the aarch64 numbers, it's just to give a flavour
of what is possible):
Result: 1384.5ms ±9.2ms
On aarch64 using edk2-aarch64 from Fedora:
Result: 8844.0ms ±30.7ms
On aarch64 using your supplied build of AAVMF:
Result: 4156.6ms ±1.3ms
I also confirmed (using libguestfs-test-tool) that it was working and
using the right AAVMF_CODE.fd file. Therefore:
Tested-by: Richard W.M. Jones <rjones@redhat.com>
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
next prev parent reply other threads:[~2018-03-16 8:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 19:02 [PATCH 0/5] ArmVirtPkg, OvmfPkg: improve firmware duration of direct kernel boot Laszlo Ersek
2018-03-15 19:02 ` [PATCH 1/5] ArmVirtPkg/PlatformBootManagerLib: return to "-kernel before boot devices" Laszlo Ersek
2018-03-16 9:58 ` Ard Biesheuvel
2018-03-16 13:40 ` Laszlo Ersek
2018-03-16 13:45 ` Ard Biesheuvel
2018-03-16 14:06 ` Laszlo Ersek
2018-03-15 19:02 ` [PATCH 2/5] OvmfPkg/PlatformBootManagerLib: wrap overlong lines in "BdsPlatform.c" Laszlo Ersek
2018-03-15 19:02 ` [PATCH 3/5] OvmfPkg/PlatformBootManagerLib: rejuvenate old-style function comments Laszlo Ersek
2018-03-15 19:02 ` [PATCH 4/5] OvmfPkg/PlatformBootManagerLib: hoist PciAcpiInitialization() Laszlo Ersek
2018-03-16 15:27 ` Gabriel L. Somlo
2018-03-15 19:02 ` [PATCH 5/5] OvmfPkg/PlatformBootManagerLib: process "-kernel" before boot devices Laszlo Ersek
2018-03-16 8:57 ` Richard W.M. Jones [this message]
2018-03-16 9:59 ` [PATCH 0/5] ArmVirtPkg, OvmfPkg: improve firmware duration of direct kernel boot Richard W.M. Jones
2018-03-16 14:02 ` Laszlo Ersek
2018-03-16 14:47 ` Richard W.M. Jones
2018-03-16 17:46 ` Laszlo Ersek
2018-03-16 14:08 ` Ard Biesheuvel
2018-03-16 15:29 ` Gabriel L. Somlo
2018-03-16 17:49 ` Laszlo Ersek
2018-03-16 19:02 ` 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=20180316085709.GX2787@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