qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH RFC 0/4] vGICv3 support


From: Christoffer Dall
Subject: Re: [Qemu-devel] [PATCH RFC 0/4] vGICv3 support
Date: Wed, 1 Jul 2015 13:28:24 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Jul 01, 2015 at 02:14:55PM +0300, Pavel Fedin wrote:
>  Hello!
> 
> > I think it would be good if you could re-spin this series based on
> > Eric's comments on the code, my comments on the patch style, and Peter's
> > advise on using machine properties for GICv3.
> 
> There was a discussion about this, and i tried to add a machine property 
> instead. This gave bad
> results: https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg04842.html
> 
> > Do you have cycles to continue working on this?
> 
>  Yes, i do. And i wish to work on this, since upstreaming this is a goal of 
> my project.
>  I know that descriptions were bad, and actually they were parts of ongoing 
> discussions. Actually i
> am waiting for integration of Shlomo Pongratz' series:
> http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg01512.html. Posted 
> as standalone, my
> series collide with Shlomo's series (it actually relies on some parts from 
> there), so i prefer to
> respin on top of something clean.

I thought the general sense here was that since emulating the full
device is much more complicated than driving the KVM part, the
integration with the virt board should go in via this series, and the
emulation should build on top of that?

Of course, if the full emulation series is almost ready to be merged
that's a different story.

It just felt like both patch series have stalled somehow, and I would
like to see what we can do to get this stuff moving again.

>  The first patch from the mentioned series is already in master; Peter told 
> me that he doesn't want
> to add the complete GICv3 before qemu 2.4 is released:
> https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg04171.html
>  So waiting...
> 
Fair enough.

-Christoffer



reply via email to

[Prev in Thread] Current Thread [Next in Thread]