From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-discuss@nongnu.org, "Cleber Rosa" <crosa@redhat.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: QEMU 5.1: Can we require each new device/machine to provided a test?
Date: Fri, 15 May 2020 13:24:13 +0200 [thread overview]
Message-ID: <7b23e643-925e-105e-f7a3-886a21be422e@redhat.com> (raw)
In-Reply-To: <20200515105118.zbslitc64hvjuhlt@sirius.home.kraxel.org>
On 15/05/20 12:51, Gerd Hoffmann wrote:
>> If a qtest is feasible, yes, I think we should require one for new
>> devices.
> qtest is not feasible, at least not for all kinds of devices. You can't
> talk to usb devices for example, and changing that effectively requires
> writing uhci/ohci/ehci/xhci drivers so one can submit usb transfers in
> qtest.
Yes, but that's just because no one has written a test for a USB device.
It would be completely feasible to plug USB into qgraph, the code for
USB in SeaBIOS is 4.5 kLOC so that's more or less the ballpark of what
you'd need. You can then stimulate keyboard or mouse devices via
chardev (-serial msmouse), or run SCSI tests for MSD and UAS.
Paolo
prev parent reply other threads:[~2020-05-15 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 10:59 QEMU 5.1: Can we require each new device/machine to provided a test? Philippe Mathieu-Daudé
2020-05-15 10:11 ` Thomas Huth
2020-05-15 10:23 ` Daniel P. Berrangé
2020-05-18 19:56 ` John Snow
2020-05-19 9:04 ` Daniel P. Berrangé
2020-05-19 23:06 ` John Snow
2020-05-20 6:13 ` Thomas Huth
2020-05-20 9:02 ` Daniel P. Berrangé
2020-05-20 14:53 ` John Snow
2020-05-20 8:57 ` Daniel P. Berrangé
2020-05-15 10:51 ` Gerd Hoffmann
2020-05-15 11:24 ` Paolo Bonzini [this message]
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=7b23e643-925e-105e-f7a3-886a21be422e@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--cc=thuth@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 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.