diff options
| author | Thomas Huth | 2018-12-19 14:13:25 +0100 |
|---|---|---|
| committer | Michael S. Tsirkin | 2019-01-15 01:31:04 +0100 |
| commit | 5a0e75f0a9ad063ebaa7eb19b82104f00acb80a0 (patch) | |
| tree | 26ab49b0d60a6a8047ff68e3e82fc3e8e2f9ab91 /docs/specs/ivshmem-spec.txt | |
| parent | msix: make pba size math more uniform (diff) | |
| download | qemu-5a0e75f0a9ad063ebaa7eb19b82104f00acb80a0.tar.gz qemu-5a0e75f0a9ad063ebaa7eb19b82104f00acb80a0.tar.xz qemu-5a0e75f0a9ad063ebaa7eb19b82104f00acb80a0.zip | |
hw/misc/ivshmem: Remove deprecated "ivshmem" legacy device
It's been marked as deprecated in QEMU v2.6.0 already, so really nobody
should use the legacy "ivshmem" device anymore (but use ivshmem-plain or
ivshmem-doorbell instead). Time to remove the deprecated device now.
Belatedly also update a mention of the deprecated "ivshmem" in the file
docs/specs/ivshmem-spec.txt to "ivshmem-doorbell". Missed in commit
5400c02b90b ("ivshmem: Split ivshmem-plain, ivshmem-doorbell off ivshmem").
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'docs/specs/ivshmem-spec.txt')
| -rw-r--r-- | docs/specs/ivshmem-spec.txt | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/specs/ivshmem-spec.txt b/docs/specs/ivshmem-spec.txt index a1f5499796..042f7eae22 100644 --- a/docs/specs/ivshmem-spec.txt +++ b/docs/specs/ivshmem-spec.txt @@ -17,12 +17,16 @@ get interrupted by its peers. There are two basic configurations: -- Just shared memory: -device ivshmem-plain,memdev=HMB,... +- Just shared memory: + + -device ivshmem-plain,memdev=HMB,... This uses host memory backend HMB. It should have option "share" set. -- Shared memory plus interrupts: -device ivshmem,chardev=CHR,vectors=N,... +- Shared memory plus interrupts: + + -device ivshmem-doorbell,chardev=CHR,vectors=N,... An ivshmem server must already be running on the host. The device connects to the server's UNIX domain socket via character device |