From: "Daniel P. Berrange" <berrange@redhat.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Shlomo Pongratz <shlomopongratz@gmail.com>,
Pavel Fedin <p.fedin@samsung.com>,
qemu-devel@nongnu.org, Ashok Kumar <ashoks@broadcom.com>,
Eric Auger <eric.auger@linaro.org>
Subject: Re: [Qemu-devel] [PATCH RFC 0/4] vGICv3 support
Date: Wed, 1 Jul 2015 11:26:56 +0100 [thread overview]
Message-ID: <20150701102656.GE16822@redhat.com> (raw)
In-Reply-To: <20150701102112.GE16763@cbox>
On Wed, Jul 01, 2015 at 12:21:12PM +0200, Christoffer Dall wrote:
> On Fri, May 22, 2015 at 01:58:40PM +0300, Pavel Fedin wrote:
> > This is my alternative to Ashok's vGICv3 patch
> > (https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg03021.html), which
> > i am currently working on. It addresses vGIC capability verification issue
> > (kvm_irqchip_create() / kvm_arch_irqchip_create()), as well as offers better
> > code structure (v3 code separated from v2).
> > This patchset applies on top of this:
> > https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg00943.html. Note that
> > GIC type selection still relies on machine name (virt-v3 vs virt), and not on
> > machine option. Since libvirt has recently introduced support for extra options,
> > i have absolutely nothing against Ashok's approach. I just did not change this
> > yet because it would affect my testing environment. The aim of this RFC is to
> > focus on vGICv3 implementation and related changes. And yes, i agree that v2 and
> > v3 now have some copypasted code, and this is TBD.
>
> This cover letter is not really helpful as it only describes the history
> and circumstances of how this patch came to be.
>
> It would be helpful if the beginning of this cover letter focuses on
> what the patch series does and which design decisions have been taken to
> shape the patches the way they are.
>
> I don't understand the whole background thing about libvirt and I don't
I replied to the earlier posting of the patch series that the quoted
libvirt limitation does not exist any longer, so that really should
not be mentioned as a problem/rationale for the machine type approach
anymore. I agree with Peter GICv3 should be selected based on properties
not new machine types.
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-07-01 10:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 10:58 [Qemu-devel] [PATCH RFC 0/4] vGICv3 support Pavel Fedin
2015-05-22 10:58 ` [Qemu-devel] [PATCH RFC 1/4] Add virt-v3 machine that uses GIC-500 Pavel Fedin
2015-05-25 14:07 ` Eric Auger
2015-05-25 14:51 ` Pavel Fedin
2015-07-01 10:11 ` Christoffer Dall
2015-05-22 10:58 ` [Qemu-devel] [PATCH RFC 2/4] Set kernel_irqchip_type for other ARM boards which use GIC Pavel Fedin
2015-05-25 14:07 ` Eric Auger
2015-05-25 14:43 ` Pavel Fedin
2015-07-01 10:11 ` Christoffer Dall
2015-05-22 10:58 ` [Qemu-devel] [PATCH RFC 3/4] First bits of vGICv3 support: Pavel Fedin
2015-05-25 14:07 ` Eric Auger
2015-07-01 10:13 ` Christoffer Dall
2015-05-22 10:58 ` [Qemu-devel] [PATCH RFC 4/4] Initial implementation of vGICv3 Pavel Fedin
2015-05-22 15:17 ` Eric Auger
2015-05-22 16:57 ` Pavel Fedin
2015-07-01 10:19 ` Christoffer Dall
2015-07-01 10:21 ` [Qemu-devel] [PATCH RFC 0/4] vGICv3 support Christoffer Dall
2015-07-01 10:26 ` Daniel P. Berrange [this message]
2015-07-01 11:14 ` Pavel Fedin
2015-07-01 11:28 ` Christoffer Dall
2015-07-01 12:31 ` Pavel Fedin
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=20150701102656.GE16822@redhat.com \
--to=berrange@redhat.com \
--cc=ashoks@broadcom.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=p.fedin@samsung.com \
--cc=qemu-devel@nongnu.org \
--cc=shlomopongratz@gmail.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).