Difference between revisions of "Virtual I/O Internals"
Jump to navigation
Jump to search
(Grammatical changes.) |
|||
| Line 11: | Line 11: | ||
==RPC Mode== | ==RPC Mode== | ||
RPC Mode moves instruction information across a virtual function interface (VF) using [https://infogalactic.com/info/Remote_procedure_call Remote Procedure Calls] generally by way of [https://infogalactic.com/info/Interrupt soft interrupt] (IOCTLs). | RPC Mode moves instruction information across a virtual function interface (VF) using [https://infogalactic.com/info/Remote_procedure_call Remote Procedure Calls] generally by way of [https://infogalactic.com/info/Interrupt soft interrupt] (IOCTLs). | ||
[[File:Mediated Device Access.png|thumb|A slide from Neo Gia's presentation at KVM forum.]] | |||
==SR-IOV Mode== | ==SR-IOV Mode== | ||
SR-IOV Mode involves the communication of instructions from a virtual function (VF) though direct communication to the [https://infogalactic.com/info/PCI_configuration_space PCI BAR]. | SR-IOV Mode involves the communication of instructions from a virtual function (VF) though direct communication to the [https://infogalactic.com/info/PCI_configuration_space PCI BAR]. | ||
Revision as of 20:21, 21 April 2022
The following document will attempt to detail the internals of a Virtual Function IO (VFIO) driven Mediated Device (Mdev).
Requirements:
Sensitive Instruction List.
Instruction Shim/Binary Translator.
HPA<->GPA Boundary Enforcement.
RPC Mode
RPC Mode moves instruction information across a virtual function interface (VF) using Remote Procedure Calls generally by way of soft interrupt (IOCTLs).
File:Mediated Device Access.png
A slide from Neo Gia's presentation at KVM forum.
SR-IOV Mode
SR-IOV Mode involves the communication of instructions from a virtual function (VF) though direct communication to the PCI BAR.