qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-ppc@nongnu.org
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
	"Daniel Henrique Barboza" <danielhb413@gmail.com>,
	"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
	"Fabiano Rosas" <farosas@suse.de>,
	"Laurent Vivier" <lvivier@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Coiby Xu" <Coiby.Xu@gmail.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Emanuele Giuseppe Esposito" <e.emanuelegiuseppe@gmail.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: [PATCH 0/4] tests/qtest: Enable spapr dma tests
Date: Thu, 17 Apr 2025 00:59:14 +1000	[thread overview]
Message-ID: <20250416145918.415674-1-npiggin@gmail.com> (raw)

I kept R-B tags from Fabiano and Phil despite a little change in
how patch 1 looks and splitting it, hope that is okay.

Since RFC:
- Split endian fix + invalid value assert into two paches.
- Changed the invalid message assertion in what is now patch 1 to
  use g_assert_cmphex so the failing value can be seen.
- Added patch 3 to factor duplicated code we just changed. Some
  patches I have for e1000e and xhci tests also want to use the
  same function...
- Fixed stray hunk from mis-rebase in the spapr patch.

Thanks,
Nick

Nicholas Piggin (4):
  tests/qtest: Enforce zero for the "un-fired" msix message value
  tests/qtest: Fix virtio msix message endianness
  tests/qtest: Add libqos function for testing msix interrupt status
  tests/qtest: Enable spapr dma with linear iommu map

 tests/qtest/libqos/pci.h               |  6 +--
 hw/ppc/spapr_iommu.c                   |  9 +++-
 tests/qtest/e1000e-test.c              | 21 ---------
 tests/qtest/igb-test.c                 | 21 ---------
 tests/qtest/libqos/generic-pcihost.c   |  1 -
 tests/qtest/libqos/pci-pc.c            |  3 --
 tests/qtest/libqos/pci-spapr.c         |  7 +--
 tests/qtest/libqos/pci.c               | 62 ++++++++++++++++++++------
 tests/qtest/libqos/virtio-pci-modern.c | 30 +++----------
 tests/qtest/libqos/virtio-pci.c        | 38 ++++------------
 tests/qtest/vhost-user-blk-test.c      |  6 ---
 tests/qtest/virtio-blk-test.c          | 12 -----
 12 files changed, 77 insertions(+), 139 deletions(-)

-- 
2.47.1



             reply	other threads:[~2025-04-16 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 14:59 Nicholas Piggin [this message]
2025-04-16 14:59 ` [PATCH 1/4] tests/qtest: Enforce zero for the "un-fired" msix message value Nicholas Piggin
2025-04-16 14:59 ` [PATCH 2/4] tests/qtest: Fix virtio msix message endianness Nicholas Piggin
2025-04-16 14:59 ` [PATCH 3/4] tests/qtest: Add libqos function for testing msix interrupt status Nicholas Piggin
2025-04-17  9:43   ` Philippe Mathieu-Daudé
2025-04-16 14:59 ` [PATCH 4/4] tests/qtest: Enable spapr dma with linear iommu map Nicholas Piggin
2025-04-17 16:18   ` Fabiano Rosas

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=20250416145918.415674-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=Coiby.Xu@gmail.com \
    --cc=danielhb413@gmail.com \
    --cc=e.emanuelegiuseppe@gmail.com \
    --cc=farosas@suse.de \
    --cc=harshpb@linux.ibm.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=stefanha@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 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).