From: "Daniel P. Berrange" <berrange@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Shlomo Pongratz' <shlomo.pongratz@huawei.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Add virt-v3 machine that uses GIC-500
Date: Tue, 12 May 2015 10:20:15 +0100 [thread overview]
Message-ID: <20150512092015.GF18200@redhat.com> (raw)
In-Reply-To: <00c901d08990$2763c410$762b4c30$@samsung.com>
On Fri, May 08, 2015 at 04:09:01PM +0300, Pavel Fedin wrote:
> I would like to offer this, slightly improved implementation. The key thing is a new
> kernel_irqchip_type member in Machine class. Currently it it used only by virt machine for
> its internal purposes, however in future it is to be passed to KVM in
> kvm_irqchip_create(). The variable is defined as int in order to be architecture agnostic,
> for potential future users.
>
> Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
> ---
> hw/arm/virt.c | 155 +++++++++++++++++++++++++++++++++++++++++++---------
> include/hw/boards.h | 1 +
> 2 files changed, 130 insertions(+), 26 deletions(-)
> +#define TYPE_VIRTV3_MACHINE "virt-v3"
[snip]
> +static const TypeInfo machvirtv3_info = {
> + .name = TYPE_VIRTV3_MACHINE,
> + .parent = TYPE_VIRT_MACHINE,
> + .instance_size = sizeof(VirtMachineState),
> + .instance_init = virtv3_instance_init,
> + .class_size = sizeof(VirtMachineClass),
> + .class_init = virtv3_class_init,
> +};
> +
> static void machvirt_machine_init(void)
> {
> type_register_static(&machvirt_info);
> + type_register_static(&machvirtv3_info);
> }
If we're going to start adding new machine types for aarch64 with
version numbers, then I think we should we be using a versioning
scheme that matches what we do on x86. ie, define versioned
machine types based on the QEMU release numbers
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2015-05-12 9:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 13:09 [Qemu-devel] [PATCH v2] Add virt-v3 machine that uses GIC-500 Pavel Fedin
2015-05-11 11:30 ` Shlomo Pongratz
2015-05-12 9:05 ` Pavel Fedin
2015-05-12 11:29 ` Shlomo Pongratz
2015-05-12 12:33 ` Pavel Fedin
2015-05-13 10:34 ` Shlomo Pongratz
2015-05-13 13:57 ` Pavel Fedin
2015-05-14 12:01 ` Shlomo Pongratz
2015-05-14 15:27 ` Pavel Fedin
2015-05-12 9:11 ` Pavel Fedin
2015-05-12 9:20 ` Daniel P. Berrange [this message]
2015-05-12 9:32 ` Pavel Fedin
2015-05-12 9:56 ` Peter Maydell
2015-05-12 11:15 ` Pavel Fedin
2015-05-12 11:20 ` Daniel P. Berrange
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=20150512092015.GF18200@redhat.com \
--to=berrange@redhat.com \
--cc=p.fedin@samsung.com \
--cc=qemu-devel@nongnu.org \
--cc=shlomo.pongratz@huawei.com \
/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).