From: "Daniel P. Berrange" <berrange@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
'QEMU Developers' <qemu-devel@nongnu.org>,
'Shlomo Pongratz' <shlomo.pongratz@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v2] Add virt-v3 machine that uses GIC-500
Date: Tue, 12 May 2015 12:20:19 +0100 [thread overview]
Message-ID: <20150512112019.GI18200@redhat.com> (raw)
In-Reply-To: <039401d08ca4$ff1cd830$fd568890$@samsung.com>
On Tue, May 12, 2015 at 02:15:46PM +0300, Pavel Fedin wrote:
> Hello!
>
> > We are not. Support for GICv2 vs v3 should be dealt with
> > by suitable machine properties
>
> I don't remember whether i clearly wrote about it... First i added a
> property, like -machine virt,gicv3=on. But then i decided to stick back
> to different machine name because libvirt does not have mechanism for
> passing machine options.
Actually there was a enhancement done to libvirt a week or two ago to
support enablment of the GIC and choice of versions.
<domain type='kvm'>
....
<features>
<gic version='3'/>
</features>
...
</domain>
commit 921c52b0db3ac898d5cc4eda19fb861ad58d9a9e
Author: Michal Privoznik <mprivozn@redhat.com>
Date: Mon Apr 27 14:03:19 2015 +0200
Introduce GIC feature
Some platforms, like aarch64, don't have APIC but GIC. So there's
no reason to have <apic/> feature turned on. However, we are
still missing <gic/> feature. This commit introduces the feature
to XML parser and formatter, adds documentation and updates RNG
schema.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
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 :|
prev parent reply other threads:[~2015-05-12 11: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
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 [this message]
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=20150512112019.GI18200@redhat.com \
--to=berrange@redhat.com \
--cc=p.fedin@samsung.com \
--cc=peter.maydell@linaro.org \
--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).