public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Sami Mujawar <sami.mujawar@arm.com>, edk2-devel@lists.01.org
Cc: ruiyu.ni@intel.com, nd@arm.com, Stephanie.Hughes-Fitt@arm.com,
	star.zeng@intel.com, Drew Jones <drjones@redhat.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Eric Auger <eauger@redhat.com>
Subject: Re: [PATCH 0/6] Add kvmtool emulated platform support for ARM
Date: Sat, 13 Oct 2018 23:42:00 +0200	[thread overview]
Message-ID: <cd09718b-d51f-60b3-49be-9eff2d1de717@redhat.com> (raw)
In-Reply-To: <20181012144009.48732-1-sami.mujawar@arm.com>

On 10/12/18 16:40, Sami Mujawar wrote:
> Kvmtool is a virtual machine manager that enables hosting KVM
> guests. ARM is working to enhance kvmtool support to enable 
> launching of KVM guest with UEFI support.

Why is QEMU not good enough? (With or without KVM.)

Another platform I've recently learned about (for QEMU) is the SBSA
reference machine type. I'm concerned that this kind of divergence will
be hard to maintain in a common firmware package. Here's my understanding:

- ArmVirtQemu: supposed to run data center / cloud workloads
- SBSA reference machine: supposed to emulate physical machines as
  closely as possible; primarily intended as a development environment
  for physical machines
- firmware for the kvmtool platform: ?

> This patch series enables UEFI support for kvmtool's emulated ARM
> platform and is required to allow testing of kvmtool enhancements.
> 
> Note: 
> 1. These kvmtool platform support patches currently expose
>    the kvmtool provided DT to the OS. Support for ACPI is
>    planned, using Dynamic Tables Framework and should be
>    available in the near future.

The Dynamic ACPI Tables Framework is not useful under QEMU, because QEMU
generates its own set of tables.

The framework would be very useful (I think) on the SBSA reference
machine, given that the framework would be shipped (presumably) on
physical machines as well. Why is it useful for kvmtool?

> 2. This new platform port can only be used with the updated
>    kvmtool that is currently under development review.
> 
> The changes can be seen at https://github.com/samimujawar/edk2/tree/299_kvmtool_plat_support_v1

I think it's valid to develop and review both streams of patches in
parallel. Usually firmware maintainers ask for the hardware emulation
bits to be pushed first.

Thanks
Laszlo

> 
> Sami Mujawar (6):
>   PcAtChipsetPkg: Add MMIO Support to SerialIo Lib
>   PcAtChipsetPkg: Add MMIO Support to RTC driver
>   MdeModulePkg: Map persistent (NV) memory
>   ArmVirtPkg: Save DT base address from X0 in PCD
>   ArmVirtPkg: Add kvmtool platform driver
>   ArmVirtPkg: Support for kvmtool emulated platform
> 
>  ArmVirtPkg/ArmVirtKvmTool.dsc                                              | 390 ++++++++++++++++++++
>  ArmVirtPkg/ArmVirtKvmTool.fdf                                              | 297 +++++++++++++++
>  ArmVirtPkg/ArmVirtPkg.dec                                                  |  12 +-
>  ArmVirtPkg/KvmtoolPlatformDxe/KvmtoolPlatformDxe.c                         | 211 +++++++++++
>  ArmVirtPkg/KvmtoolPlatformDxe/KvmtoolPlatformDxe.inf                       |  60 +++
>  ArmVirtPkg/PrePi/AArch64/ModuleEntryPoint.S                                |   9 +-
>  MdeModulePkg/MdeModulePkg.dec                                              |   9 +
>  MdeModulePkg/Universal/Variable/EmuRuntimeDxe/EmuVariable.c                |  77 +++-
>  MdeModulePkg/Universal/Variable/EmuRuntimeDxe/EmuVariableRuntimeDxe.inf    |   6 +
>  PcAtChipsetPkg/Library/SerialIoLib/SerialIoLib.inf                         |   4 +
>  PcAtChipsetPkg/Library/SerialIoLib/SerialPortLib.c                         |  98 ++++-
>  PcAtChipsetPkg/PcAtChipsetPkg.dec                                          |   8 +
>  PcAtChipsetPkg/PcatRealTimeClockRuntimeDxe/PcRtc.c                         |  38 +-
>  PcAtChipsetPkg/PcatRealTimeClockRuntimeDxe/PcRtcEntry.c                    | 112 +++++-
>  PcAtChipsetPkg/PcatRealTimeClockRuntimeDxe/PcatRealTimeClockRuntimeDxe.inf |   8 +
>  15 files changed, 1309 insertions(+), 30 deletions(-)
>  create mode 100644 ArmVirtPkg/ArmVirtKvmTool.dsc
>  create mode 100644 ArmVirtPkg/ArmVirtKvmTool.fdf
>  create mode 100644 ArmVirtPkg/KvmtoolPlatformDxe/KvmtoolPlatformDxe.c
>  create mode 100644 ArmVirtPkg/KvmtoolPlatformDxe/KvmtoolPlatformDxe.inf
> 



  parent reply	other threads:[~2018-10-13 21:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 14:40 [PATCH 0/6] Add kvmtool emulated platform support for ARM Sami Mujawar
2018-10-12 14:40 ` [PATCH v1 1/6] PcAtChipsetPkg: Add MMIO Support to SerialIo Lib Sami Mujawar
2018-10-12 14:49   ` Ard Biesheuvel
2018-10-12 15:06     ` Sami Mujawar
2018-10-12 15:31       ` Kinney, Michael D
2018-10-12 15:33       ` Ard Biesheuvel
2018-10-15  2:38         ` Ni, Ruiyu
2018-10-12 14:40 ` [PATCH v1 2/6] PcAtChipsetPkg: Add MMIO Support to RTC driver Sami Mujawar
2018-10-13 10:51   ` Leif Lindholm
2018-10-12 14:40 ` [PATCH v1 3/6] MdeModulePkg: Map persistent (NV) memory Sami Mujawar
2018-10-13  9:09   ` Zeng, Star
2018-10-13 21:28   ` Laszlo Ersek
2018-10-12 14:40 ` [PATCH v1 4/6] ArmVirtPkg: Save DT base address from X0 in PCD Sami Mujawar
2018-10-13 21:35   ` Laszlo Ersek
2018-10-19 14:01     ` Ard Biesheuvel
2018-10-12 14:40 ` [PATCH v1 5/6] ArmVirtPkg: Add kvmtool platform driver Sami Mujawar
2018-10-13 21:54   ` Laszlo Ersek
2018-10-12 14:40 ` [PATCH v1 6/6] ArmVirtPkg: Support for kvmtool emulated platform Sami Mujawar
2018-10-13 21:57   ` Laszlo Ersek
2018-10-13 21:42 ` Laszlo Ersek [this message]
2018-10-16  3:00   ` [PATCH 0/6] Add kvmtool emulated platform support for ARM Leif Lindholm

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=cd09718b-d51f-60b3-49be-9eff2d1de717@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