On 21.05.20 20:18, Michael S. Tsirkin wrote: > On Thu, May 21, 2020 at 05:53:31PM +0100, Alex Bennée wrote: >> >> Jan Kiszka <jan.kis...@siemens.com> writes: >> >>> From: Jan Kiszka <jan.kis...@siemens.com> >>> >>> This imports the ivshmem v2 specification draft from Jailhouse where the >>> implementation is about to be merged now. The final home of the spec is >>> to be decided, this shall just simplify the review process at this >>> stage. >>> >>> Signed-off-by: Jan Kiszka <jan.kis...@siemens.com> >>> --- >>> docs/specs/ivshmem-2-device-spec.md | 376 >>> ++++++++++++++++++++++++++++++++++++ >>> 1 file changed, 376 insertions(+) >>> create mode 100644 docs/specs/ivshmem-2-device-spec.md >>> >>> diff --git a/docs/specs/ivshmem-2-device-spec.md >>> b/docs/specs/ivshmem-2-device-spec.md >>> new file mode 100644 >>> index 0000000000..d93cb22b04 >>> --- /dev/null >>> +++ b/docs/specs/ivshmem-2-device-spec.md >>> @@ -0,0 +1,376 @@ >>> +IVSHMEM Device Specification >>> +============================ >>> + >>> +** NOTE: THIS IS WORK-IN-PROGRESS, NOT YET A STABLE INTERFACE >>> SPECIFICATION! ** >> >> Has there been any proposal to the OASIS virtio spec to use this as a >> transport for VirtIO? >>
Not yet, primarily because the second half - virtio over generic shared memory or even ivshmem2 in particular - has not been written yet. It only exists as prototypes. Lacking time. >> -- >> Alex Bennée > > > I think intergrating this in the virtio spec needs not gate the > implementation, but I'd like to see the current spec copied to > virtio-comments list to possibly get comments from that community. > > Will do. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux