From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, armbru@redhat.com, aliguori@amazon.com,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] scripts: Add qom-tree script as modern equivalent of info qtree
Date: Fri, 07 Feb 2014 12:21:21 +0100 [thread overview]
Message-ID: <52F4C1B1.302@redhat.com> (raw)
In-Reply-To: <52F4BEEA.5060606@suse.de>
Il 07/02/2014 12:09, Andreas Färber ha scritto:
>> No matter how much I like QOM (I do), I would rather say that the all
>> QOM grand plan has been "inconclusive". 99% in-tree uses of QOM are
>> just a glorified qdev, buses and all. You shouldn't be surprised if
>> people still care about the "legacy" qdev tree.
>
> I am not offended about people caring about legacy devices. I am
> offended that people are trying to revert good QOM changes so that they
> match their expectations from legacy concepts.
I object to calling any change good if it causes a segfault anywhere
else in the code, even if it may be good from a QOM-only point of view.
After a month the change hasn't been reverted yet, so I don't think
people are trying too hard. But reverting is always one of the possible
solutions. Reapplying a reverted patch is easy.
> I have stated at two KVM Forums already that qdev is dead.
Define "qdev", please.
> qdev.c to device.c? That's pretty easy to do if it solves these qdev
> discussions...
Let's stop talking about theory and let's look at the actual ccode, please.
next prev parent reply other threads:[~2014-02-07 11:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 17:35 [Qemu-devel] [PATCH] scripts: Add qom-tree script as modern equivalent of info qtree Andreas Färber
2014-02-05 17:48 ` Paolo Bonzini
2014-02-05 17:51 ` Andreas Färber
2014-02-05 17:55 ` Paolo Bonzini
2014-02-05 18:01 ` Andreas Färber
2014-02-07 7:13 ` Paolo Bonzini
2014-02-07 11:09 ` Andreas Färber
2014-02-07 11:21 ` Paolo Bonzini [this message]
2014-02-07 12:44 ` Andreas Färber
2014-02-07 13:06 ` Paolo Bonzini
2014-02-07 13:48 ` Andreas Färber
2014-02-07 14:18 ` Paolo Bonzini
2014-02-07 15:00 ` Markus Armbruster
2014-02-07 12:49 ` Andreas Färber
2014-02-07 13:16 ` Paolo Bonzini
2014-02-05 17:56 ` Andreas Färber
2014-02-05 17:58 ` Paolo Bonzini
2014-02-05 18:08 ` Andreas Färber
2014-02-07 10:41 ` Paolo Bonzini
2014-02-07 11:00 ` Andreas Färber
2014-02-07 11:10 ` Paolo Bonzini
2014-02-05 18:24 ` Eric Blake
2014-02-05 18:39 ` Andreas Färber
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=52F4C1B1.302@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.