From: Christoffer Dall <christoffer.dall@linaro.org>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
'Shlomo Pongratz' <shlomopongratz@gmail.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 13:28:24 +0200 [thread overview]
Message-ID: <20150701112824.GA17890@cbox> (raw)
In-Reply-To: <01d001d0b3ef$299a2d30$7cce8790$@samsung.com>
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
next prev parent reply other threads:[~2015-07-01 11:28 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
2015-07-01 11:14 ` Pavel Fedin
2015-07-01 11:28 ` Christoffer Dall [this message]
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=20150701112824.GA17890@cbox \
--to=christoffer.dall@linaro.org \
--cc=ashoks@broadcom.com \
--cc=eric.auger@linaro.org \
--cc=p.fedin@samsung.com \
--cc=peter.maydell@linaro.org \
--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).