From: Jan Kiszka <jan.kiszka@web.de>
To: Peter Xu <peterx@redhat.com>,
QEMU Devel Mailing List <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
John Snow <jsnow@redhat.com>,
David kiarie <davidkiarie4@gmail.com>,
Valentine Sinitsyn <valentine.sinitsyn@gmail.com>
Subject: Re: [Qemu-devel] Question about qtest and IOMMU
Date: Wed, 29 Jun 2016 08:36:09 +0200 [thread overview]
Message-ID: <57736C59.8010503@web.de> (raw)
In-Reply-To: <20160629063221.GF16629@pxdev.xzpeter.org>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
On 2016-06-29 08:32, Peter Xu wrote:
> Hi, all,
>
> I am thinking about whether it's possible to write up a unit test
> program for emulated IOMMUs (of course, Intel IOMMU would be the first
> one). This can provide us the chance to do quick functional regression
> tests for IOMMU just like other devices, as well as customized test
> sequences which is hard to do in real guests (e.g., specific cache
> invalidations, error injections), etc..
>
> I see that current qtest framework cannot support well on testing
> IOMMUs. For DMA remapping, things would be quite smooth. The problem
> is that, we still do not have a complete test framework on the
> interrupts. E.g., currently qtest is still an acceleration type, in
> which we have no vCPUs, as well as interrupt chips like APICs (please
> correct me if I am wrong). It's even further if we want to test
> something like kernel irqchips with QEMU. Not sure whether it's
> possible to do test based on a much realistic VM (e.g., with KVM
> enabled, but just keep the CPUs stall?).
>
> I'd say that IOMMU is still experimental, and there are only limited
> number of patches for it (so maybe we do not need a unit test at all).
> Just want to post this idea out, to see:
>
> - Whether we need a IOMMU unit test after all?
>
> - Whether there is other potential consumer who has similar needs to
> IOMMU, so that we can see whether try to move qtest a step further
> if there are common requirements.
>
Adding David and Valentine as we were discussing this need in the
context of the AMD IOMMU as well: You cannot test errors with workload
(like Linux) that do not trigger them in normal conditions.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-06-29 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 6:32 [Qemu-devel] Question about qtest and IOMMU Peter Xu
2016-06-29 6:36 ` Jan Kiszka [this message]
2016-06-29 7:08 ` Paolo Bonzini
2016-06-29 7:44 ` Peter Xu
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=57736C59.8010503@web.de \
--to=jan.kiszka@web.de \
--cc=davidkiarie4@gmail.com \
--cc=jsnow@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=valentine.sinitsyn@gmail.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.