From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Anthony Liguori" <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qom: helper macro for adding read-only properties
Date: Mon, 16 Sep 2013 19:03:36 +0200 [thread overview]
Message-ID: <523739E8.9060204@redhat.com> (raw)
In-Reply-To: <20130916165150.GB4386@redhat.com>
Il 16/09/2013 18:51, Michael S. Tsirkin ha scritto:
>> >
>> > We can have "make check" run QEMU once for each board, which would trap
>> > things that will always break at runtime such as a misspelled property.
>> > Similarly, we could have tests that try to instantiate every device,
>> > even if they do not do anything with the guest-visible device. Such
>> > dummy tests can catch bugs in interface changes.
> They won't catch bugs for properties that
> 1. change after device is instanciated
> 2. are accessed after device is instanciated
True, but I don't think there are any at this time if you
s/instantiated/realized/.
Paolo
next prev parent reply other threads:[~2013-09-16 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 17:23 [Qemu-devel] [PATCH] qom: helper macro for adding read-only properties Michael S. Tsirkin
2013-09-15 17:54 ` Peter Maydell
2013-09-15 20:06 ` Michael S. Tsirkin
2013-09-16 6:32 ` Andreas Färber
2013-09-16 12:33 ` Michael S. Tsirkin
2013-09-16 15:24 ` Andreas Färber
2013-09-16 15:41 ` Paolo Bonzini
2013-09-16 15:48 ` Michael S. Tsirkin
2013-09-16 15:56 ` Paolo Bonzini
2013-09-16 16:01 ` Michael S. Tsirkin
2013-09-16 16:07 ` Paolo Bonzini
2013-09-16 16:51 ` Michael S. Tsirkin
2013-09-16 17:03 ` Paolo Bonzini [this message]
2013-09-16 16:07 ` Michael S. Tsirkin
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=523739E8.9060204@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).