From: Shunsuke Mie <mie@igel.co.jp>
To: Kishon Vijay Abraham I <kvijayab@amd.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
vaishnav.a@ti.com
Cc: "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 18:47:50 +0900 [thread overview]
Message-ID: <fe309259-01f0-871f-4620-3a4bdc56a186@igel.co.jp> (raw)
In-Reply-To: <d096e88e-aec5-9920-8d5a-bd8200560c2c@amd.com>
On 2023/09/21 18:11, Kishon Vijay Abraham I wrote:
> +Vaishnav
>
> Hi Shunsuke,
>
> On 8/18/2023 7:16 PM, Shunsuke Mie wrote:
>> Hi all,
>>
>> We are proposing to add a new test syste to Linux for PCIe Endpoint.
>> That
>> can be run on QEMU without real hardware. At present, partially we have
>> confirmed that pci-epf-test is working, but it is not yet complete.
>> However, we would appreciate your comments on the architecture design.
>>
>> # Background
>> The background is as follows.
>>
>> 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.
I got it. I'll make a table to compare some methods that includes
greybus to realize this emulation environment.
Best,
Shunsuke
> Though I don't understand this fully, Looking at
> https://osseu2023.sched.com/event/1OGk8/emulating-devices-in-linux-using-greybus-subsystem-vaishnav-mohandas-achath-texas-instruments,
> Vaishnav seems to solve the same problem using greybus for multiple
> type s of devices.
>
> Vaishnav, we'd wait for your OSS presentation but do you have any
> initial thoughts on how greybus could be used to test PCIe endpoint
> drivers?
>
> Thanks,
> Kishon
>
>>
>> # Architecture
>> The overview of the architecture is as follows.
>>
>> Guest 1 Guest 2
>> +-------------------------+ +----------------------------+
>> | Linux kernel | | Linux kernel |
>> | | | |
>> | PCI EP function driver | | |
>> | (e.g. pci-epf-test) | | |
>> |-------------------------| | PCI Device Driver |
>> | (2) QEMU EPC Driver | | (e.g. pci_endpoint_test) |
>> +-------------------------+ +----------------------------+
>> +-------------------------+ +----------------------------+
>> | QEMU | | QEMU |
>> |-------------------------| |----------------------------|
>> | (1) QEMU PCI EPC Device *----* (3) QEMU EPF Bridge Device |
>> +-------------------------+ +----------------------------+
>>
>> At present, it is designed to work guests only on the same host, and
>> communication is done through Unix domain sockets.
>>
>> The three parts shown in the figure were introduced this time.
>>
>> (1) QEMU PCI Endpoint Controller(EPC) Device
>> PCI Endpoint Controller implemented as QEMU PCI device.
>> (2) QEMU PCI Endpoint Controller(EPC) Driver
>> Linux kernel driver that drives the device (1). It registers a epc
>> device
>> to linux kernel and handling each operations for the epc device.
>> (3) QEMU PCI Endpoint function(EPF) Bridge Device
>> QEMU PCI device that cooperates with (1) and performs accesses to pci
>> configuration space, BAR and memory space to communicate each guests,
>> and
>> generates interruptions to the guest 1.
>>
>> Each projects are:
>> (1), (3) https://github.com/ShunsukeMie/qemu/tree/epf-bridge/v1
>> <https://github.com/ShunsukeMie/qemu/tree/epf-bridge/v1>
>> files: hw/misc/{qemu-epc.{c,h}, epf-bridge.c}
>> (2) https://github.com/ShunsukeMie/linux-virtio-rdma/tree/qemu-epc
>> <https://github.com/ShunsukeMie/linux-virtio-rdma/tree/qemu-epc>
>> files: drivers/pci/controller/pcie-qemu-ep.c
>>
>> # Protocol
>>
>> PCI, PCIe has a layer structure that includes Physical, Data Lane and
>> Transaction. The communicates between the bridge(3) and controller (1)
>> mimic the Transaction. Specifically, a protocol is implemented for
>> exchanging fd for communication protocol version check and
>> communication,
>> in addition to the interaction equivalent to PCIe Transaction Layer
>> Packet
>> (Read and Write of I/O, Memory, Configuration space and Message). In my
>> mind, we need to discuss the communication mor.
>>
>> We also are planning to post the patch set after the code is
>> organized and
>> the protocol discussion is matured.
>>
>> Best regards,
>> Shunsuke
next prev parent reply other threads:[~2023-09-26 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANXvt5oKt=AKdqv24LT079e+6URnfqJcfTJh0ajGA17paJUEKw@mail.gmail.com>
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
2023-09-26 9:47 ` Shunsuke Mie [this message]
2023-09-26 12:40 ` Vaishnav Achath
2023-10-03 4:56 ` Shunsuke Mie
2023-10-03 14:31 ` Jiri Kastner
[not found] <CAGNS4TbhS3XnCFAEi378+cSmJvGMdjN2oTv=tES36vbV4CaDuA@mail.gmail.com>
[not found] ` <CANXvt5qKxfU3p1eSK4fkzRFRBXHSVvSkJrnQRLKPkQjhsMGNzQ@mail.gmail.com>
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=fe309259-01f0-871f-4620-3a4bdc56a186@igel.co.jp \
--to=mie@igel.co.jp \
--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=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
all inboxes | Powered by JetHome®