All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, marcel@redhat.com
Subject: Re: [Qemu-devel] [PATCH] pci-testdev: enhance to support new testcases
Date: Tue, 27 Sep 2016 14:37:44 +0800	[thread overview]
Message-ID: <20160927063744.GC10363@pxdev.xzpeter.org> (raw)
In-Reply-To: <20160922182305.hulm7yfx24gor5fg@redhat.com>

On Thu, Sep 22, 2016 at 09:23:05PM +0300, Michael S. Tsirkin wrote:
> On Thu, Sep 22, 2016 at 02:15:08PM +0800, Peter Xu wrote:
> > pci-testdev is used mostly in kvm-unit-test for some eventfd tests.
> > However I see it a good framework for other tests as well (e.g., the
> > IOMMU unit test in the future). So enhanced it to support more
> > testcases.
> > 
> > The original memory handlers and protocol are strict and not easy to
> > change (we need to keep the old behavior of pci-testdev).
> > So I added a
> > new parameter for the device, and memory ops will be dynamically handled
> > depending on what testcase it is configured. To specify a new test case
> > for pci-testdev, we use:
> > 
> >   -device pci-testdev,testcase=XXX
> > 
> > The default will be "eventfd", which is the original behavior for
> > pci-testdev. In the future, we can just add new testcase for pci-testdev
> > to achieve different goals.
> 
> Instead of a parameter, how about creating a subregion
> of the BAR and adding new tests at an offset?

Yeah, I can do that as well.

> 
> All you need for compatibility is add a 0-filled
> entry after existing tests.

Could you help explain why we need zero-filled entry? it'll work as
long as tests are using different regions of memory (no overlap),
right?

Thanks,

-- peterx

  reply	other threads:[~2016-09-27  6:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  6:15 [Qemu-devel] [PATCH] pci-testdev: enhance to support new testcases Peter Xu
2016-09-22 11:18 ` Andrew Jones
2016-09-23  3:37   ` Peter Xu
2016-09-22 18:23 ` Michael S. Tsirkin
2016-09-27  6:37   ` Peter Xu [this message]
2016-09-27  8:38     ` Peter Xu
2016-09-27 10:13       ` Paolo Bonzini
2016-09-28  3:04         ` 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=20160927063744.GC10363@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.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 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.