From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel@lists.01.org, lersek@redhat.com
Subject: Re: [PATCH] ArmVirtPkg: implement KVM safe IoLib instance
Date: Tue, 5 Jun 2018 12:29:50 +0100 [thread overview]
Message-ID: <20180605112950.ta2jgg5ufy4zjeuj@bivouac.eciton.net> (raw)
In-Reply-To: <20180605110543.17663-1-ard.biesheuvel@linaro.org>
On Tue, Jun 05, 2018 at 01:05:43PM +0200, Ard Biesheuvel wrote:
> KVM on ARM refuses to decode load/store instructions used to perform
> I/O to emulated devices, and instead relies on the exception syndrome
> information to describe the operand register, access size, etc.
> This is only possible for instructions that have a single input/output
> register (as opposed to ones that increment the offset register, or
> load/store pair instructions, etc). Otherwise, QEMU crashes with the
> following error
>
> error: kvm run failed Function not implemented
> R00=01010101 R01=00000008 R02=00000048 R03=08000820
> R04=00000120 R05=7faaa0e0 R06=7faaa0dc R07=7faaa0e8
> R08=7faaa0ec R09=7faaa088 R10=000000ff R11=00000080
> R12=ff000000 R13=7fccfe08 R14=7faa835f R15=7faa887c
> PSR=800001f3 N--- T svc32
> QEMU: Terminated
>
> and KVM produces a warning such as the following in the kernel log
>
> kvm [17646]: load/store instruction decoding not implemented
>
> The IoLib implementation provided by MdePkg/Library/BaseIoLibIntrinsic
> is based on C code, and when LTO is in effect, the MMIO accesses could
> be merged with, e.g., manipulations of the loop counter, producing
> opcodes that KVM does not support for emulated MMIO.
>
> So instead, let's reimplement IoLib in a KVM safe manner.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> Yet another approach for the KVM MMIO emulation issue. Note that this one
> (as well as the MdePkg) affect both AArch64 and ARM. This is deliberate,
> given that there is no reason AArch64 should be immune to this: we simply
> haven't triggered the issue yet.
I'm happier with this version (at the same time as I'm sad we're
splitting this out).
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
> ArmVirtPkg/Library/ArmVirtIoLib/AArch64/ArmVirtMmio.S | 164 ++
> ArmVirtPkg/Library/ArmVirtIoLib/Arm/ArmVirtMmio.S | 154 ++
> ArmVirtPkg/Library/ArmVirtIoLib/Arm/ArmVirtMmio.asm | 165 ++
> ArmVirtPkg/Library/ArmVirtIoLib/ArmVirtIoLib.c | 589 +++++
> ArmVirtPkg/Library/ArmVirtIoLib/ArmVirtIoLib.h | 188 ++
> ArmVirtPkg/Library/ArmVirtIoLib/ArmVirtIoLib.inf | 49 +
> ArmVirtPkg/Library/ArmVirtIoLib/IoHighLevel.c | 2358 ++++++++++++++++++++
> ArmVirtPkg/Library/ArmVirtIoLib/IoLibMmioBuffer.c | 413 ++++
> 8 files changed, 4080 insertions(+)
next prev parent reply other threads:[~2018-06-05 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 11:05 [PATCH] ArmVirtPkg: implement KVM safe IoLib instance Ard Biesheuvel
2018-06-05 11:29 ` Leif Lindholm [this message]
2018-06-05 13:04 ` Laszlo Ersek
2018-06-07 10:44 ` Ard Biesheuvel
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=20180605112950.ta2jgg5ufy4zjeuj@bivouac.eciton.net \
--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