From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Hongbo Zhang <hongbo.zhang@linaro.org>,
peter.maydell@linaro.org, qemu-arm@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/arm: Add SBSA machine type
Date: Thu, 28 Jun 2018 11:22:16 +0100 [thread overview]
Message-ID: <20180628102216.GC3513@redhat.com> (raw)
In-Reply-To: <20180627123116.GB2424@work-vm>
On Wed, Jun 27, 2018 at 01:31:17PM +0100, Dr. David Alan Gilbert wrote:
> * Hongbo Zhang (hongbo.zhang@linaro.org) wrote:
> > This patch introduces a new Arm machine type 'SBSA' with features:
> > - Based on legacy 'virt' machine type.
The 'virt' machine type is absolutely *not* legacy. It is the preferred
modern, legacy-free machine type when running virtual machines. Since
aarch64 is greenfield, there is no compelling reason to emulate a
specific physical machine for VMs, hence the 'virt' machine type.
> > - Newly designed memory map.
> > - EL2 and EL3 are enabled by default.
> > - AHCI controller attached to system bus, and then CDROM and hard disc
> > can be added to it.
> > - EHCI controller attached to system bus, with USB mouse and key board
> > installed by default.
> > - E1000 ethernet card on PCIE bus.
> > - VGA display adaptor on PCIE bus.
> > - Default CPU type cortex-a57, 4 cores, and 1G bytes memory.
> > - No virtio functions enabled, since this is to emulate real hardware.
>
> I'm a bit confused; do you have real modern ARM hardware that has an
> e1000 on it? If I understand correctly, e1000 is the old PCI version
> and the e1000e is at least the more modern PCIe version which makes
> more sense if you're building on PCIe.
Indeed, it makes little sense to default to e1000 if the goal is to make
it legacy-free
> However, if you:
> a) Don't have real hardware with the e1000 on
> b) Do have PCIe
>
> then to my mind it makes sense to use virtio-net-pci rather than
> an e1000e.
If it does down the virtio-* route though, I fail to see any point in
adding the new machine type at all - 'virt' machine type is intended
to be used for guests where everything is paravirtualized, ignoring
physical hardware constraints.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-06-28 10:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 10:13 [Qemu-devel] [PATCH] hw/arm: Add SBSA machine type Hongbo Zhang
2018-06-27 12:31 ` Dr. David Alan Gilbert
2018-06-28 4:19 ` Hongbo Zhang
2018-06-28 8:12 ` Dr. David Alan Gilbert
2018-06-28 9:30 ` Hongbo Zhang
2018-06-28 9:28 ` [Qemu-devel] [Qemu-arm] " Alex Bennée
2018-06-28 10:23 ` Hongbo Zhang
2018-06-28 10:22 ` Daniel P. Berrangé [this message]
2018-06-28 10:47 ` [Qemu-devel] " Hongbo Zhang
2018-06-27 14:56 ` Igor Mammedov
2018-06-28 8:11 ` Hongbo Zhang
2018-06-28 9:04 ` Andrew Jones
2018-06-28 10:13 ` Hongbo Zhang
2018-06-28 11:36 ` Andrew Jones
2018-06-29 3:17 ` Hongbo Zhang
2018-06-28 9:31 ` Laszlo Ersek
2018-06-28 10:38 ` Hongbo Zhang
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-all 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=20180628102216.GC3513@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=hongbo.zhang@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).