From: Andrea Bolognani <abologna@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: wei@redhat.com, libvir-list@redhat.com,
Andrew Jones <drjones@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] ARM: add QMP command to query GIC version
Date: Mon, 29 Feb 2016 17:30:36 +0100 [thread overview]
Message-ID: <1456763436.3566.4.camel@redhat.com> (raw)
In-Reply-To: <20160222013521.GA14065@pxdev.xzpeter.org>
On Mon, 2016-02-22 at 09:35 +0800, Peter Xu wrote:
> On Fri, Feb 19, 2016 at 01:33:09PM +0100, Andrea Bolognani wrote:
> >
> > I didn't say it would be hard :)
> >
> > I just said that such compatibility code would have to be kept
> > around forever. We already support lots and lots of similar cases
> > in libvirt, the difference being that in this case we would add
> > support for a new command *knowing in advance* that it will become
> > obsolete as soon as a proper implementation is available.
> >
> > It might still be the right thing to do! I just want to make sure
> > everything's been properly considered and discussed beforehand.
>
> I totally agree with you to think more before doing. :)
So, anyone else willing to give their $0.2 on how to implement
this The Right Way™?
I just skimmed the whole thread again and it doesn't look to me
like any consensus has been reached.
Cheers.
--
Andrea Bolognani
Software Engineer - Virtualization Team
next prev parent reply other threads:[~2016-02-29 16:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 5:41 [Qemu-devel] [RFC PATCH 0/2] ARM: add QMP command to query GIC version Peter Xu
2016-02-14 5:41 ` [Qemu-devel] [RFC PATCH 1/2] arm: gic: add GICType Peter Xu
2016-02-14 5:41 ` [Qemu-devel] [RFC PATCH 2/2] arm: gic: add "query-gic-capability" interface Peter Xu
2016-02-15 6:54 ` [Qemu-devel] [RFC PATCH 0/2] ARM: add QMP command to query GIC version Wei Huang
2016-02-15 7:34 ` Peter Xu
2016-02-15 7:49 ` Fam Zheng
2016-02-15 9:35 ` [Qemu-devel] [libvirt] " Martin Kletzander
2016-02-15 9:41 ` Peter Maydell
2016-02-15 12:16 ` Andrew Jones
2016-02-15 12:27 ` Pavel Fedin
2016-02-15 10:09 ` Peter Xu
2016-02-15 9:52 ` [Qemu-devel] " Markus Armbruster
2016-02-15 10:34 ` Peter Xu
2016-02-15 15:08 ` Markus Armbruster
2016-02-15 15:21 ` Peter Maydell
2016-02-15 19:40 ` Markus Armbruster
2016-02-15 20:18 ` Andrew Jones
2016-02-15 20:32 ` Peter Maydell
2016-02-16 10:10 ` Markus Armbruster
2016-02-16 10:15 ` Daniel P. Berrange
2016-02-16 12:05 ` [Qemu-devel] [libvirt] " Andrea Bolognani
2016-02-16 12:09 ` Peter Maydell
2016-02-16 12:20 ` Andrea Bolognani
2016-02-16 12:15 ` Daniel P. Berrange
2016-02-16 12:27 ` Andrea Bolognani
2016-02-16 12:38 ` Daniel P. Berrange
2016-02-16 13:14 ` Andrea Bolognani
2016-02-15 15:22 ` [Qemu-devel] " Daniel P. Berrange
2016-02-18 4:40 ` Peter Xu
2016-02-18 16:52 ` Andrew Jones
2016-02-18 17:10 ` Andrea Bolognani
2016-02-19 1:55 ` Peter Xu
2016-02-19 12:33 ` Andrea Bolognani
2016-02-22 1:35 ` Peter Xu
2016-02-29 16:30 ` Andrea Bolognani [this message]
2016-03-01 2:19 ` Peter Xu
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=1456763436.3566.4.camel@redhat.com \
--to=abologna@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=libvir-list@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wei@redhat.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).