From: Peter Xu <peterx@redhat.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: kvm@vger.kernel.org, Thomas Huth <thuth@redhat.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: [kvm-unit-tests PATCH v7 12/13] pci: Add pci-testdev PCI bus test device
Date: Fri, 23 Sep 2016 15:25:42 +0800 [thread overview]
Message-ID: <20160923072542.GC15411@pxdev.xzpeter.org> (raw)
In-Reply-To: <15b9e7ffcf6f978c58e44e45502331949d61d19f.1471434672.git.agordeev@redhat.com>
Some nit-picks inline...
(btw, this looks more like a test case shared by platforms rather than
a library, so shall we move it outside of lib/? I don't know.)
On Wed, Aug 17, 2016 at 02:07:13PM +0200, Alexander Gordeev wrote:
[...]
> +static bool pci_testdev_one(struct pci_test_dev_hdr *test,
> + int test_nr,
> + struct pci_testdev_ops *ops)
> +{
> + u8 width;
> + u32 count, sig, off;
> + const int nr_writes = 16;
> + int i;
> +
> + ops->io_writeb(test_nr, &test->test);
> + count = ops->io_readl(&test->count);
> + if (count != 0)
> + return false;
> +
> + width = ops->io_readb(&test->width);
> + if (width != 1 && width != 2 && width != 4)
> + return false;
IIUC we only have 1?
> +
> + sig = ops->io_readl(&test->data);
> + off = ops->io_readl(&test->offset);
> +
> + for (i = 0; i < nr_writes; i++) {
> + switch (width) {
> + case 1: ops->io_writeb(sig, (void *)test + off); break;
> + case 2: ops->io_writew(sig, (void *)test + off); break;
> + case 4: ops->io_writel(sig, (void *)test + off); break;
Here as well. Could I ask why we are handling 2/4?
[...]
> +static int pci_testdev_all(struct pci_test_dev_hdr *test,
> + struct pci_testdev_ops *ops)
> +{
> + int i;
> +
> + for (i = 0;; i++) {
> + if (!pci_testdev_one(test, i, ops))
> + break;
Since we have defined PCI_TESTDEV_NUM_TESTS, shall we use it here to
stop the loop rather than depending on a failure code from
pci_testdev_one()?
[...]
> +int pci_testdev(void)
> +{
> + phys_addr_t addr;
> + void __iomem *mem, *io;
> + pcidevaddr_t dev;
> + int nr_tests = 0;
> + bool ret;
> +
> + dev = pci_find_dev(PCI_VENDOR_ID_REDHAT, PCI_DEVICE_ID_REDHAT_TEST);
> + if (dev == PCIDEVADDR_INVALID) {
> + printf("'pci-testdev' device is not found, "
> + "check QEMU '-device pci-testdev' parameter\n");
> + return -1;
> + }
> +
> + ret = pci_bar_is_valid(dev, 0) && pci_bar_is_valid(dev, 1);
> + assert(ret);
> +
> + addr = pci_bar_get_addr(dev, 0);
> + mem = ioremap(addr, PAGE_SIZE);
> +
> + addr = pci_bar_get_addr(dev, 1);
> + io = (void *)(unsigned long)addr;
x86/vmexit.c is using pci-testdev as well. Maybe we can generalize the
init part and share it? (Actually there is patch in my local tree for
this, but haven't posted :)
Thanks!
-- peterx
next prev parent reply other threads:[~2016-09-23 7:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 12:07 [kvm-unit-tests PATCH v7 00/13] PCI bus support Alexander Gordeev
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 01/13] pci: Fix coding style in generic PCI files Alexander Gordeev
2016-08-18 11:37 ` Thomas Huth
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 02/13] pci: x86: Rename pci_config_read() to pci_config_readl() Alexander Gordeev
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 03/13] pci: Add 'extern' to public function declarations Alexander Gordeev
2016-08-17 13:49 ` Andrew Jones
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 04/13] pci: x86: Add remaining PCI configuration space accessors Alexander Gordeev
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 05/13] pci: Factor out pci_bar_get() Alexander Gordeev
2016-08-18 11:39 ` Thomas Huth
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 06/13] pci: Rework pci_bar_addr() Alexander Gordeev
2016-09-23 7:14 ` Peter Xu
2016-09-23 8:51 ` Andrew Jones
2016-09-23 8:58 ` Peter Xu
2016-10-12 14:37 ` Alexander Gordeev
2016-10-13 6:40 ` Peter Xu
2016-10-13 14:16 ` Alexander Gordeev
2016-10-14 6:23 ` Peter Xu
2016-10-14 6:55 ` Andrew Jones
2016-10-14 9:09 ` Peter Xu
2016-10-14 12:37 ` Alexander Gordeev
2016-10-19 3:46 ` Peter Xu
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 07/13] pci: Add pci_bar_set_addr() Alexander Gordeev
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 08/13] pci: Add pci_dev_exists() Alexander Gordeev
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 09/13] pci: Add pci_print() Alexander Gordeev
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 10/13] pci: Add generic ECAM host support Alexander Gordeev
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 11/13] arm/arm64: pci: Add PCI bus operation test Alexander Gordeev
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 12/13] pci: Add pci-testdev PCI bus test device Alexander Gordeev
2016-08-17 14:03 ` Andrew Jones
2016-09-23 7:25 ` Peter Xu [this message]
2016-09-23 8:55 ` Andrew Jones
2016-10-12 16:54 ` Alexander Gordeev
2016-10-13 6:52 ` Peter Xu
2016-10-13 13:16 ` Alexander Gordeev
2016-10-14 5:01 ` Peter Xu
2016-10-14 7:07 ` Andrew Jones
2016-10-14 9:14 ` Peter Xu
2016-08-17 12:07 ` [kvm-unit-tests PATCH v7 13/13] arm/arm64: pci: Add pci-testdev PCI device operation test Alexander Gordeev
2016-08-17 14:26 ` [kvm-unit-tests PATCH v7 00/13] PCI bus support Andrew Jones
2016-08-23 18:28 ` Alexander Gordeev
2016-09-22 11:10 ` Andrew Jones
2016-09-28 6:33 ` Peter Xu
2016-10-12 8:00 ` Alexander Gordeev
2016-10-12 10:59 ` Peter Xu
2016-10-12 14:35 ` Alexander Gordeev
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=20160923072542.GC15411@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=agordeev@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=thuth@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).