qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: QEMU Devel Mailing List <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jan Kiszka <jan.kiszka@web.de>,
	Peter Maydell <peter.maydell@linaro.org>,
	Peter Xu <peterx@redhat.com>, John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] Question about qtest and IOMMU
Date: Wed, 29 Jun 2016 14:32:21 +0800	[thread overview]
Message-ID: <20160629063221.GF16629@pxdev.xzpeter.org> (raw)

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.

Thanks.

-- peterx

             reply	other threads:[~2016-06-29  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  6:32 Peter Xu [this message]
2016-06-29  6:36 ` [Qemu-devel] Question about qtest and IOMMU Jan Kiszka
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=20160629063221.GF16629@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=jsnow@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).