From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, berrange@redhat.com, ehabkost@redhat.com
Subject: Re: [PATCH not-for-merge 0/5] Instrumentation for "Fixes around device realization"
Date: Wed, 20 May 2020 14:13:24 +0200 [thread overview]
Message-ID: <60a1b3d3-354f-ab11-31f4-dbbbbf8a9270@redhat.com> (raw)
In-Reply-To: <20200518051945.8621-1-armbru@redhat.com>
On 5/18/20 7:19 AM, Markus Armbruster wrote:
> This is the instrumentation mentioned in "[PATCH 00/24] Fixes around
> device realization".
>
> PATCH 2/5 might have value on its own. You tell me.
I'd like to have 2/3 merged normally because as you described, having
reproducible output makes testing simpler. Can you repost them with
proper syntax/style?
I have similar hacks than 1/4/5.
What about having the warnings always displayed with warn_report() while
running QTests? Simply checking qtest_enabled().
>
> Shell script to smoke-test all machines:
>
> #!/bin/sh
> success=0
> fail=0
> ulimit -c 0
> git-describe --dirty --match v\*
> git-log --oneline -1
> for i in bld/*-softmmu
> do
> t=${i%-softmmu}
> t=${t##*/}
> q=$i/qemu-system-$t
> echo "= $t ="
>
> for m in `$q -M help | sed -n '/(alias of/d;2,$s/ .*//p'`
> do
> echo "== $m =="
> echo -e 'info qom-tree\ninfo qtree\nq' | $q -S -accel qtest -display none -L smoke-mon-roms -M $m -monitor stdio
> if [ $? -eq 0 ]
> then echo "*** Success: $m ***"; let success++
> else echo "*** Fail: $m"; let fail++
> fi
> done
> done
> echo $success succeeded, $fail failed
>
>
> Markus Armbruster (5):
> qom: Instrument to detect missed realize
> qom: Make "info qom-tree" show children sorted
> qdev: Make "info qtree" show child devices sorted by QOM path
> qdev: Instrument to detect missed QOM parenting
> qdev: Instrument to detect bus mismatch
>
> hw/core/qdev.c | 17 ++++++++++++++++
> qdev-monitor.c | 32 ++++++++++++++++++++++++++++-
> qom/qom-hmp-cmds.c | 51 +++++++++++++++++++++++++++++++++++++++++++++-
> 3 files changed, 98 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2020-05-20 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 5:19 [PATCH not-for-merge 0/5] Instrumentation for "Fixes around device realization" Markus Armbruster
2020-05-18 5:19 ` [PATCH not-for-merge 1/5] qom: Instrument to detect missed realize Markus Armbruster
2020-05-18 5:19 ` [PATCH not-for-merge 2/5] qom: Make "info qom-tree" show children sorted Markus Armbruster
2020-05-18 21:04 ` Eric Blake
2020-05-19 6:43 ` Markus Armbruster
2020-05-18 5:19 ` [PATCH not-for-merge 3/5] qdev: Make "info qtree" show child devices sorted by QOM path Markus Armbruster
2020-05-18 5:19 ` [PATCH not-for-merge 4/5] qdev: Instrument to detect missed QOM parenting Markus Armbruster
2020-05-18 5:19 ` [PATCH not-for-merge 5/5] qdev: Instrument to detect bus mismatch Markus Armbruster
2020-05-18 6:54 ` [PATCH not-for-merge 0/5] Instrumentation for "Fixes around device realization" no-reply
2020-05-18 7:08 ` no-reply
2020-05-18 7:27 ` no-reply
2020-05-18 20:56 ` Mark Cave-Ayland
2020-05-19 6:50 ` Markus Armbruster
2020-05-20 12:13 ` Philippe Mathieu-Daudé [this message]
2020-05-20 14:18 ` Markus Armbruster
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=60a1b3d3-354f-ab11-31f4-dbbbbf8a9270@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--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 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).