Existing Linux endpoint only supports pci-epf-test for communication between RootComplex and EndPoint systems (Both running Linux). While pci-epf-test is good enough for "testing" communication between RootComplex and Endpoint, additional development based on pci-epf-test was required for implementing any real use-cases.
This paper proposes to use existing Virtio infrastructure in Kernel used for
1. Communication between HOST and GUEST systems in Virtualization context
2. Communication between different cores in an SoC
to be used for RC<->EP communication and for communication between HOSTS connected to NTB.
Using the proposed mechanism, existing Virtio based drivers like rpmsg, net, scsi, blk etc.. could be made to be used for RootComplex and Endpoint communication.
The same mechanism can also be extended to be used for communication between HOSTS connected to NTB. Here instead of existing ntb_transport, virtio transport should be used.
The first RFC  posted garnered quite a bit of interest among the community and various approaches for designing it was discussed.
In this paper, Kishon will provide high-level view of how virtio could be used for RC<->EP communication and also discuss the various design approaches, with pros and cons of each approach and accelerate getting the community alignment of the overall design.
 -> http://firstname.lastname@example.org
|I agree to abide by the anti-harassment policy||I agree|