All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
	QEMU Devel Mailing List <qemu-devel@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Valentine Sinitsyn <valentine.sinitsyn@gmail.com>,
	David kiarie <davidkiarie4@gmail.com>,
	John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] Question about qtest and IOMMU
Date: Wed, 29 Jun 2016 15:44:36 +0800	[thread overview]
Message-ID: <20160629074436.GA23084@pxdev.xzpeter.org> (raw)
In-Reply-To: <dd3bacb6-a5d4-92d6-9852-7560164a266e@redhat.com>

On Wed, Jun 29, 2016 at 09:08:29AM +0200, Paolo Bonzini wrote:
> 
> 
> On 29/06/2016 08:36, Jan Kiszka wrote:
> > 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).
> 
> qtest does have VCPUs, they just run a dummy loop.  You do have an APIC
> too, but reading it doesn't work because cpu_get_current_apic() returns
> NULL.

Right, thanks to point out.

> 
> You can use kvm-unit-tests if qtest is not flexible enough.  It's
> probably the simplest thing to do if you also want to test kernel LAPIC
> and split irqchip operation.

Will have a look. Thanks Paolo. :)

-- peterx

      reply	other threads:[~2016-06-29  7:44 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
2016-06-29  7:08   ` Paolo Bonzini
2016-06-29  7:44     ` Peter Xu [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=20160629074436.GA23084@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=davidkiarie4@gmail.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 \
    --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.