From: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: mdroth@linux.vnet.ibm.com, ehabkost@redhat.com
Subject: [Qemu-devel] [PATCH] scripts/device-crash-test: vmcoreinfo in error_whitelist for ppc64
Date: Fri, 27 Oct 2017 16:17:40 -0200 [thread overview]
Message-ID: <20171027181740.32165-1-danielhb@linux.vnet.ibm.com> (raw)
The device vmcoreinfo depends on the fw_cfg device to work, a device
that isn't available in most ppc64 machines. This makes device-crash-test
spams the following error when running with qemu-system-ppc64:
"INFO: log: qemu-system-ppc64: -device vmcoreinfo: vmcoreinfo device
requires fw_cfg with DMA"
To fix it, this patch adds the following ppc64 machines into the
error_whitelist for the vmcoreinfo device:
- pseries.*
- 40p
- bamboo
- g3beige
- mac99
- mpc8544ds
- powernv
- ppce500
- prep
- virtex-ml507
After this patch, the only ppc64 machine that reports error on the
vmcoreinfo device is the 'none' type.
Signed-off-by: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
---
scripts/device-crash-test | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 043b24a4aa..fb8a43d679 100755
--- a/scripts/device-crash-test
+++ b/scripts/device-crash-test
@@ -163,6 +163,18 @@ ERROR_WHITELIST = [
# "spapr-cpu-core needs a pseries machine"
{'machine':'(?!pseries).*', 'device':'.*-spapr-cpu-core', 'expected':True},
+ # vmcoreinfo requires a fw_cfg device and will fail in these ppc64 machines
+ {'machine':'pseries.*', 'device':'vmcoreinfo', 'expected':True},
+ {'machine':'40p', 'device':'vmcoreinfo', 'expected':True},
+ {'machine':'bamboo', 'device':'vmcoreinfo', 'expected':True},
+ {'machine':'g3beige', 'device':'vmcoreinfo', 'expected':True},
+ {'machine':'mac99', 'device':'vmcoreinfo', 'expected':True},
+ {'machine':'mpc8544ds', 'device':'vmcoreinfo', 'expected':True},
+ {'machine':'powernv', 'device':'vmcoreinfo', 'expected':True},
+ {'machine':'ppce500', 'device':'vmcoreinfo', 'expected':True},
+ {'machine':'prep', 'device':'vmcoreinfo', 'expected':True},
+ {'machine':'virtex-ml507', 'device':'vmcoreinfo', 'expected':True},
+
# KVM-specific devices shouldn't be tried without accel=kvm:
{'accel':'(?!kvm).*', 'device':'kvmclock', 'expected':True},
{'accel':'(?!kvm).*', 'device':'kvm-pci-assign', 'expected':True},
--
2.13.6
next reply other threads:[~2017-10-27 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 18:17 Daniel Henrique Barboza [this message]
2017-11-03 11:49 ` [Qemu-devel] [PATCH] scripts/device-crash-test: vmcoreinfo in error_whitelist for ppc64 Marc-André Lureau
2017-11-03 12:01 ` Thomas Huth
2017-11-03 12:30 ` Marc-André Lureau
2017-11-03 12:52 ` Thomas Huth
2017-11-03 13:16 ` Daniel Henrique Barboza
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=20171027181740.32165-1-danielhb@linux.vnet.ibm.com \
--to=danielhb@linux.vnet.ibm.com \
--cc=ehabkost@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).