From: Christoph Hellwig <hch@infradead.org>
To: Kishon Vijay Abraham I <kvijayab@amd.com>
Cc: "Shunsuke Mie" <mie@igel.co.jp>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
vaishnav.a@ti.com, "Paolo Bonzini" <pbonzini@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
qemu-devel@nongnu.org, "Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, "Krzysztof Wilczyński" <kw@linux.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>
Subject: Re: [RFC] Proposal of QEMU PCI Endpoint test environment
Date: Tue, 26 Sep 2023 00:26:00 -0700 [thread overview]
Message-ID: <ZRKHiE9iFuHGUkHV@infradead.org> (raw)
In-Reply-To: <d096e88e-aec5-9920-8d5a-bd8200560c2c@amd.com>
On Thu, Sep 21, 2023 at 02:41:54PM +0530, Kishon Vijay Abraham I wrote:
> > PCI Endpoint function driver is implemented using the PCIe Endpoint
> > framework, but it requires physical boards for testing, and it is difficult
> > to test sufficiently. In order to find bugs and hardware-dependent
> > implementations early, continuous testing is required. Since it is
> > difficult to automate tests that require hardware, this RFC proposes a
> > virtual environment for testing PCI endpoint function drivers.
>
> This would be quite useful and thank you for attempting it! I would like to
> compare other mechanisms available in-addition to QEMU before going with the
> QEMU approach.
Well, the point of PCIe endpoint subsystem in vhost or similar is that
you can use one and the same endpoint implementation. So you can debug
it using qemu and the use it with a physical port, which would be really
amazing.
next prev parent reply other threads:[~2023-09-26 7:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 13:46 [RFC] Proposal of QEMU PCI Endpoint test environment Shunsuke Mie
2023-08-23 6:09 ` Manivannan Sadhasivam
2023-08-25 8:56 ` Shunsuke Mie
2023-09-21 9:11 ` Kishon Vijay Abraham I
2023-09-26 7:26 ` Christoph Hellwig [this message]
2023-09-26 9:47 ` Shunsuke Mie
2023-09-26 12:40 ` Vaishnav Achath
2023-10-03 4:56 ` Shunsuke Mie
2023-10-03 14:31 ` Jiri Kastner
-- strict thread matches above, loose matches on Subject: below --
2023-10-04 7:36 Mattias Nissler
2023-10-05 1:31 ` Shunsuke Mie
2023-10-05 7:02 ` Mattias Nissler
2023-10-06 11:51 ` Shunsuke Mie
2023-10-06 12:00 ` Mattias Nissler
2023-10-06 12:07 ` Thanos Makatos
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=ZRKHiE9iFuHGUkHV@infradead.org \
--to=hch@infradead.org \
--cc=bhelgaas@google.com \
--cc=kishon@kernel.org \
--cc=kvijayab@amd.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mie@igel.co.jp \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robh@kernel.org \
--cc=vaishnav.a@ti.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).