From: "wanglimin" <wanglimin@xfusion.com>
To: "ardb@kernel.org" <ardb@kernel.org>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] EDK2 UpdateVariable very slow for the first defined VM on aarch64 with preempt-rt kernel
Date: Tue, 17 Dec 2024 10:37:07 +0000 [thread overview]
Message-ID: <c073b311ca8646c4b5b939d637771b88@xfusion.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
Hi Ard,
I notice that you had ever worked on VirtNorFlashDxe, and maybe can help me on the following trouble.
I am trying to boot kvm VM on aarch64(arm-v8) with preempt-rt kernel host,
the UpdateVariable is very very slow, and the uefi boot take about ~80s to get to phase,
while it takes only about ~15s on a normal linux kernel or on x86 hardware.
This only happen when the VM is first defined, or redefine the VM:
virsh destroy VM;
virsh undefine VM --nvram
virsh define VM.xml ;
virsh start VM
It seems the most time spending when VirtNorFlash write operation at MmioWrite32();
On X64 platform,it seems use EmuVariableFvbRuntimeDxe driver,not really write the NorFlash device,
Is it possible for arm to use the similar way as X64 ?
Could you give any suggestion?
Best Regards.
Limin Wang
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120927): https://edk2.groups.io/g/devel/message/120927
Mute This Topic: https://groups.io/mt/110222787/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 5661 bytes --]
reply other threads:[~2024-12-20 23:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c073b311ca8646c4b5b939d637771b88@xfusion.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