RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
/*
|
|
|
|
* Inter-VM Shared Memory PCI device.
|
|
|
|
*
|
|
|
|
* Author:
|
|
|
|
* Cam Macdonell <cam@cs.ualberta.ca>
|
|
|
|
*
|
|
|
|
* Based On: cirrus_vga.c
|
|
|
|
* Copyright (c) 2004 Fabrice Bellard
|
|
|
|
* Copyright (c) 2004 Makoto Suzuki (suzu)
|
|
|
|
*
|
|
|
|
* and rtl8139.c
|
|
|
|
* Copyright (c) 2006 Igor Kovalenko
|
|
|
|
*
|
|
|
|
* This code is licensed under the GNU GPL v2.
|
2012-01-13 20:44:23 +04:00
|
|
|
*
|
|
|
|
* Contributions after 2012-01-13 are licensed under the terms of the
|
|
|
|
* GNU GPL, version 2 or (at your option) any later version.
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
*/
|
2019-05-23 17:35:07 +03:00
|
|
|
|
2016-01-26 21:17:17 +03:00
|
|
|
#include "qemu/osdep.h"
|
2018-06-25 15:41:59 +03:00
|
|
|
#include "qemu/units.h"
|
include/qemu/osdep.h: Don't include qapi/error.h
Commit 57cb38b included qapi/error.h into qemu/osdep.h to get the
Error typedef. Since then, we've moved to include qemu/osdep.h
everywhere. Its file comment explains: "To avoid getting into
possible circular include dependencies, this file should not include
any other QEMU headers, with the exceptions of config-host.h,
compiler.h, os-posix.h and os-win32.h, all of which are doing a
similar job to this file and are under similar constraints."
qapi/error.h doesn't do a similar job, and it doesn't adhere to
similar constraints: it includes qapi-types.h. That's in excess of
100KiB of crap most .c files don't actually need.
Add the typedef to qemu/typedefs.h, and include that instead of
qapi/error.h. Include qapi/error.h in .c files that need it and don't
get it now. Include qapi-types.h in qom/object.h for uint16List.
Update scripts/clean-includes accordingly. Update it further to match
reality: replace config.h by config-target.h, add sysemu/os-posix.h,
sysemu/os-win32.h. Update the list of includes in the qemu/osdep.h
comment quoted above similarly.
This reduces the number of objects depending on qapi/error.h from "all
of them" to less than a third. Unfortunately, the number depending on
qapi-types.h shrinks only a little. More work is needed for that one.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
[Fix compilation without the spice devel packages. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-03-14 11:01:28 +03:00
|
|
|
#include "qapi/error.h"
|
2016-03-20 20:16:19 +03:00
|
|
|
#include "qemu/cutils.h"
|
2013-02-04 18:40:22 +04:00
|
|
|
#include "hw/pci/pci.h"
|
2019-08-12 08:23:51 +03:00
|
|
|
#include "hw/qdev-properties.h"
|
2020-12-12 01:05:12 +03:00
|
|
|
#include "hw/qdev-properties-system.h"
|
2015-07-09 16:50:13 +03:00
|
|
|
#include "hw/pci/msi.h"
|
2013-02-04 18:40:22 +04:00
|
|
|
#include "hw/pci/msix.h"
|
2012-12-17 21:20:04 +04:00
|
|
|
#include "sysemu/kvm.h"
|
2017-04-06 13:00:28 +03:00
|
|
|
#include "migration/blocker.h"
|
2019-08-12 08:23:45 +03:00
|
|
|
#include "migration/vmstate.h"
|
2015-03-17 20:29:20 +03:00
|
|
|
#include "qemu/error-report.h"
|
2012-12-17 21:20:00 +04:00
|
|
|
#include "qemu/event_notifier.h"
|
2019-05-23 17:35:07 +03:00
|
|
|
#include "qemu/module.h"
|
2016-03-15 21:34:46 +03:00
|
|
|
#include "qom/object_interfaces.h"
|
2017-01-26 17:26:44 +03:00
|
|
|
#include "chardev/char-fe.h"
|
2015-06-30 01:10:16 +03:00
|
|
|
#include "sysemu/hostmem.h"
|
2016-03-15 21:34:51 +03:00
|
|
|
#include "sysemu/qtest.h"
|
2015-06-30 01:10:16 +03:00
|
|
|
#include "qapi/visitor.h"
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2015-06-16 18:43:34 +03:00
|
|
|
#include "hw/misc/ivshmem.h"
|
2020-09-03 23:43:22 +03:00
|
|
|
#include "qom/object.h"
|
2015-06-16 18:43:34 +03:00
|
|
|
|
2012-12-13 13:19:37 +04:00
|
|
|
#define PCI_VENDOR_ID_IVSHMEM PCI_VENDOR_ID_REDHAT_QUMRANET
|
|
|
|
#define PCI_DEVICE_ID_IVSHMEM 0x1110
|
|
|
|
|
2016-03-15 21:34:37 +03:00
|
|
|
#define IVSHMEM_MAX_PEERS UINT16_MAX
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
#define IVSHMEM_IOEVENTFD 0
|
|
|
|
#define IVSHMEM_MSI 1
|
|
|
|
|
|
|
|
#define IVSHMEM_REG_BAR_SIZE 0x100
|
|
|
|
|
2016-03-15 21:34:27 +03:00
|
|
|
#define IVSHMEM_DEBUG 0
|
|
|
|
#define IVSHMEM_DPRINTF(fmt, ...) \
|
|
|
|
do { \
|
|
|
|
if (IVSHMEM_DEBUG) { \
|
|
|
|
printf("IVSHMEM: " fmt, ## __VA_ARGS__); \
|
|
|
|
} \
|
|
|
|
} while (0)
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:51 +03:00
|
|
|
#define TYPE_IVSHMEM_COMMON "ivshmem-common"
|
2020-09-03 23:43:22 +03:00
|
|
|
typedef struct IVShmemState IVShmemState;
|
2020-09-01 00:07:33 +03:00
|
|
|
DECLARE_INSTANCE_CHECKER(IVShmemState, IVSHMEM_COMMON,
|
|
|
|
TYPE_IVSHMEM_COMMON)
|
2016-03-15 21:34:51 +03:00
|
|
|
|
|
|
|
#define TYPE_IVSHMEM_PLAIN "ivshmem-plain"
|
2020-09-01 00:07:33 +03:00
|
|
|
DECLARE_INSTANCE_CHECKER(IVShmemState, IVSHMEM_PLAIN,
|
|
|
|
TYPE_IVSHMEM_PLAIN)
|
2016-03-15 21:34:51 +03:00
|
|
|
|
|
|
|
#define TYPE_IVSHMEM_DOORBELL "ivshmem-doorbell"
|
2020-09-01 00:07:33 +03:00
|
|
|
DECLARE_INSTANCE_CHECKER(IVShmemState, IVSHMEM_DOORBELL,
|
|
|
|
TYPE_IVSHMEM_DOORBELL)
|
2016-03-15 21:34:51 +03:00
|
|
|
|
2013-06-24 10:59:29 +04:00
|
|
|
#define TYPE_IVSHMEM "ivshmem"
|
2020-09-01 00:07:33 +03:00
|
|
|
DECLARE_INSTANCE_CHECKER(IVShmemState, IVSHMEM,
|
|
|
|
TYPE_IVSHMEM)
|
2013-06-24 10:59:29 +04:00
|
|
|
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
typedef struct Peer {
|
|
|
|
int nb_eventfds;
|
2012-07-05 19:16:25 +04:00
|
|
|
EventNotifier *eventfds;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
} Peer;
|
|
|
|
|
2015-07-27 13:59:19 +03:00
|
|
|
typedef struct MSIVector {
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
PCIDevice *pdev;
|
2015-07-09 16:50:13 +03:00
|
|
|
int virq;
|
2017-12-11 10:21:08 +03:00
|
|
|
bool unmasked;
|
2015-07-27 13:59:19 +03:00
|
|
|
} MSIVector;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2020-09-03 23:43:22 +03:00
|
|
|
struct IVShmemState {
|
2013-06-30 17:15:15 +04:00
|
|
|
/*< private >*/
|
|
|
|
PCIDevice parent_obj;
|
|
|
|
/*< public >*/
|
|
|
|
|
2016-03-15 21:34:52 +03:00
|
|
|
uint32_t features;
|
|
|
|
|
|
|
|
/* exactly one of these two may be set */
|
|
|
|
HostMemoryBackend *hostmem; /* with interrupts */
|
2016-10-22 12:52:51 +03:00
|
|
|
CharBackend server_chr; /* without interrupts */
|
2016-03-15 21:34:52 +03:00
|
|
|
|
|
|
|
/* registers */
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
uint32_t intrmask;
|
|
|
|
uint32_t intrstatus;
|
2016-03-15 21:34:52 +03:00
|
|
|
int vm_id;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:52 +03:00
|
|
|
/* BARs */
|
|
|
|
MemoryRegion ivshmem_mmio; /* BAR 0 (registers) */
|
2016-03-15 21:34:47 +03:00
|
|
|
MemoryRegion *ivshmem_bar2; /* BAR 2 (shared memory) */
|
|
|
|
MemoryRegion server_bar2; /* used with server_chr */
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:52 +03:00
|
|
|
/* interrupt support */
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
Peer *peers;
|
2016-03-15 21:34:37 +03:00
|
|
|
int nb_peers; /* space in @peers[] */
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
uint32_t vectors;
|
2015-07-27 13:59:19 +03:00
|
|
|
MSIVector *msi_vectors;
|
2016-03-15 21:34:44 +03:00
|
|
|
uint64_t msg_buf; /* buffer for receiving server messages */
|
|
|
|
int msg_buffered_bytes; /* #bytes in @msg_buf */
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:52 +03:00
|
|
|
/* migration stuff */
|
2016-03-15 21:34:50 +03:00
|
|
|
OnOffAuto master;
|
2011-11-15 01:09:44 +04:00
|
|
|
Error *migration_blocker;
|
2020-09-03 23:43:22 +03:00
|
|
|
};
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
|
|
|
/* registers for the Inter-VM shared memory device */
|
|
|
|
enum ivshmem_registers {
|
|
|
|
INTRMASK = 0,
|
|
|
|
INTRSTATUS = 4,
|
|
|
|
IVPOSITION = 8,
|
|
|
|
DOORBELL = 12,
|
|
|
|
};
|
|
|
|
|
|
|
|
static inline uint32_t ivshmem_has_feature(IVShmemState *ivs,
|
|
|
|
unsigned int feature) {
|
|
|
|
return (ivs->features & (1 << feature));
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:50 +03:00
|
|
|
static inline bool ivshmem_is_master(IVShmemState *s)
|
|
|
|
{
|
|
|
|
assert(s->master != ON_OFF_AUTO_AUTO);
|
|
|
|
return s->master == ON_OFF_AUTO_ON;
|
|
|
|
}
|
|
|
|
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
static void ivshmem_IntrMask_write(IVShmemState *s, uint32_t val)
|
|
|
|
{
|
|
|
|
IVSHMEM_DPRINTF("IntrMask write(w) val = 0x%04x\n", val);
|
|
|
|
|
|
|
|
s->intrmask = val;
|
|
|
|
}
|
|
|
|
|
|
|
|
static uint32_t ivshmem_IntrMask_read(IVShmemState *s)
|
|
|
|
{
|
|
|
|
uint32_t ret = s->intrmask;
|
|
|
|
|
|
|
|
IVSHMEM_DPRINTF("intrmask read(w) val = 0x%04x\n", ret);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ivshmem_IntrStatus_write(IVShmemState *s, uint32_t val)
|
|
|
|
{
|
|
|
|
IVSHMEM_DPRINTF("IntrStatus write(w) val = 0x%04x\n", val);
|
|
|
|
|
|
|
|
s->intrstatus = val;
|
|
|
|
}
|
|
|
|
|
|
|
|
static uint32_t ivshmem_IntrStatus_read(IVShmemState *s)
|
|
|
|
{
|
|
|
|
uint32_t ret = s->intrstatus;
|
|
|
|
|
|
|
|
/* reading ISR clears all interrupts */
|
|
|
|
s->intrstatus = 0;
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2012-10-23 14:30:10 +04:00
|
|
|
static void ivshmem_io_write(void *opaque, hwaddr addr,
|
2011-08-08 17:09:12 +04:00
|
|
|
uint64_t val, unsigned size)
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
{
|
|
|
|
IVShmemState *s = opaque;
|
|
|
|
|
|
|
|
uint16_t dest = val >> 16;
|
|
|
|
uint16_t vector = val & 0xff;
|
|
|
|
|
|
|
|
addr &= 0xfc;
|
|
|
|
|
|
|
|
IVSHMEM_DPRINTF("writing to addr " TARGET_FMT_plx "\n", addr);
|
|
|
|
switch (addr)
|
|
|
|
{
|
|
|
|
case INTRMASK:
|
|
|
|
ivshmem_IntrMask_write(s, val);
|
|
|
|
break;
|
|
|
|
|
|
|
|
case INTRSTATUS:
|
|
|
|
ivshmem_IntrStatus_write(s, val);
|
|
|
|
break;
|
|
|
|
|
|
|
|
case DOORBELL:
|
|
|
|
/* check that dest VM ID is reasonable */
|
2015-06-19 13:17:26 +03:00
|
|
|
if (dest >= s->nb_peers) {
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
IVSHMEM_DPRINTF("Invalid destination VM ID (%d)\n", dest);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* check doorbell range */
|
2010-08-30 14:31:33 +04:00
|
|
|
if (vector < s->peers[dest].nb_eventfds) {
|
2012-07-05 19:16:25 +04:00
|
|
|
IVSHMEM_DPRINTF("Notifying VM %d on vector %d\n", dest, vector);
|
|
|
|
event_notifier_set(&s->peers[dest].eventfds[vector]);
|
2015-06-18 16:04:13 +03:00
|
|
|
} else {
|
|
|
|
IVSHMEM_DPRINTF("Invalid destination vector %d on VM %d\n",
|
|
|
|
vector, dest);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
break;
|
|
|
|
default:
|
2015-06-18 16:04:13 +03:00
|
|
|
IVSHMEM_DPRINTF("Unhandled write " TARGET_FMT_plx "\n", addr);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2012-10-23 14:30:10 +04:00
|
|
|
static uint64_t ivshmem_io_read(void *opaque, hwaddr addr,
|
2011-08-08 17:09:12 +04:00
|
|
|
unsigned size)
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
{
|
|
|
|
|
|
|
|
IVShmemState *s = opaque;
|
|
|
|
uint32_t ret;
|
|
|
|
|
|
|
|
switch (addr)
|
|
|
|
{
|
|
|
|
case INTRMASK:
|
|
|
|
ret = ivshmem_IntrMask_read(s);
|
|
|
|
break;
|
|
|
|
|
|
|
|
case INTRSTATUS:
|
|
|
|
ret = ivshmem_IntrStatus_read(s);
|
|
|
|
break;
|
|
|
|
|
|
|
|
case IVPOSITION:
|
2016-03-15 21:34:41 +03:00
|
|
|
ret = s->vm_id;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
break;
|
|
|
|
|
|
|
|
default:
|
|
|
|
IVSHMEM_DPRINTF("why are we reading " TARGET_FMT_plx "\n", addr);
|
|
|
|
ret = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2011-08-08 17:09:12 +04:00
|
|
|
static const MemoryRegionOps ivshmem_mmio_ops = {
|
|
|
|
.read = ivshmem_io_read,
|
|
|
|
.write = ivshmem_io_write,
|
|
|
|
.endianness = DEVICE_NATIVE_ENDIAN,
|
|
|
|
.impl = {
|
|
|
|
.min_access_size = 4,
|
|
|
|
.max_access_size = 4,
|
|
|
|
},
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
};
|
|
|
|
|
2015-12-21 14:10:13 +03:00
|
|
|
static void ivshmem_vector_notify(void *opaque)
|
|
|
|
{
|
2015-07-27 13:59:19 +03:00
|
|
|
MSIVector *entry = opaque;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
PCIDevice *pdev = entry->pdev;
|
2016-03-15 21:34:51 +03:00
|
|
|
IVShmemState *s = IVSHMEM_COMMON(pdev);
|
2015-07-27 13:59:19 +03:00
|
|
|
int vector = entry - s->msi_vectors;
|
2015-12-21 14:10:13 +03:00
|
|
|
EventNotifier *n = &s->peers[s->vm_id].eventfds[vector];
|
|
|
|
|
|
|
|
if (!event_notifier_test_and_clear(n)) {
|
|
|
|
return;
|
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2015-07-24 19:52:19 +03:00
|
|
|
IVSHMEM_DPRINTF("interrupt on vector %p %d\n", pdev, vector);
|
2015-12-21 14:10:13 +03:00
|
|
|
if (ivshmem_has_feature(s, IVSHMEM_MSI)) {
|
ivshmem: Clean up MSI-X conditions
There are three predicates related to MSI-X:
* ivshmem_has_feature(s, IVSHMEM_MSI) is true unless the non-MSI-X
variant of the device is selected with msi=off.
* msix_present() is true when the device has the PCI capability MSI-X.
It's initially false, and becomes true during successful realize of
the MSI-X variant of the device. Thus, it's the same as
ivshmem_has_feature(s, IVSHMEM_MSI) for realized devices.
* msix_enabled() is true when msix_present() is true and guest software
has enabled MSI-X.
Code that differs between the non-MSI-X and the MSI-X variant of the
device needs to be guarded by ivshmem_has_feature(s, IVSHMEM_MSI) or
by msix_present(), except the latter works only for realized devices.
Code that depends on whether MSI-X is in use needs to be guarded with
msix_enabled().
Code review led me to two minor messes:
* ivshmem_vector_notify() calls msix_notify() even when
!msix_enabled(), unlike most other MSI-X-capable devices. As far as
I can tell, msix_notify() does nothing when !msix_enabled(). Add
the guard anyway.
* Most callers of ivshmem_use_msix() guard it with
ivshmem_has_feature(s, IVSHMEM_MSI). Not necessary, because
ivshmem_use_msix() does nothing when !msix_present(). That's
ivshmem's only use of msix_present(), though. Guard it
consistently, and drop the now redundant msix_present() check.
While there, rename ivshmem_use_msix() to ivshmem_msix_vector_use().
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <1458066895-20632-20-git-send-email-armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2016-03-15 21:34:34 +03:00
|
|
|
if (msix_enabled(pdev)) {
|
|
|
|
msix_notify(pdev, vector);
|
|
|
|
}
|
2015-12-21 14:10:13 +03:00
|
|
|
} else {
|
|
|
|
ivshmem_IntrStatus_write(s, 1);
|
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2015-07-09 16:50:13 +03:00
|
|
|
static int ivshmem_vector_unmask(PCIDevice *dev, unsigned vector,
|
|
|
|
MSIMessage msg)
|
|
|
|
{
|
2016-03-15 21:34:51 +03:00
|
|
|
IVShmemState *s = IVSHMEM_COMMON(dev);
|
2015-07-09 16:50:13 +03:00
|
|
|
EventNotifier *n = &s->peers[s->vm_id].eventfds[vector];
|
|
|
|
MSIVector *v = &s->msi_vectors[vector];
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
IVSHMEM_DPRINTF("vector unmask %p %d\n", dev, vector);
|
ivshmem: Don't update non-existent MSI routes
As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
QEMU crashes with:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
if the ivshmem device is configured with more vectors than what the server
supports. This is caused by the ivshmem_vector_unmask() being called on
vectors that have not been initialized by ivshmem_add_kvm_msi_virq().
This commit fixes it by adding a simple check to the mask and unmask
callbacks.
Note that the opposite mismatch, if the server supplies more vectors than
what the device is configured for, is already handled and leads to output
like:
Too many eventfd received, device has 1 vectors
To reproduce the assert, run:
ivshmem-server -n 0
and QEMU with:
-device ivshmem-doorbell,chardev=iv
-chardev socket,path=/tmp/ivshmem_socket,id=iv
then load the Windows driver, at the time of writing available at:
https://github.com/virtio-win/kvm-guest-drivers-windows/tree/master/ivshmem
The issue is believed to have been masked by other guest drivers, notably
Linux ones, not enabling MSI-X on the device.
Fixes: 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications")
Signed-off-by: Ladi Prosek <lprosek@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20171211072110.9058-2-lprosek@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-12-11 10:21:07 +03:00
|
|
|
if (!v->pdev) {
|
|
|
|
error_report("ivshmem: vector %d route does not exist", vector);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
2017-12-11 10:21:08 +03:00
|
|
|
assert(!v->unmasked);
|
2015-07-09 16:50:13 +03:00
|
|
|
|
|
|
|
ret = kvm_irqchip_update_msi_route(kvm_state, v->virq, msg, dev);
|
|
|
|
if (ret < 0) {
|
|
|
|
return ret;
|
|
|
|
}
|
2016-07-14 08:56:33 +03:00
|
|
|
kvm_irqchip_commit_routes(kvm_state);
|
2015-07-09 16:50:13 +03:00
|
|
|
|
2017-12-11 10:21:08 +03:00
|
|
|
ret = kvm_irqchip_add_irqfd_notifier_gsi(kvm_state, n, NULL, v->virq);
|
|
|
|
if (ret < 0) {
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
v->unmasked = true;
|
|
|
|
|
|
|
|
return 0;
|
2015-07-09 16:50:13 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void ivshmem_vector_mask(PCIDevice *dev, unsigned vector)
|
|
|
|
{
|
2016-03-15 21:34:51 +03:00
|
|
|
IVShmemState *s = IVSHMEM_COMMON(dev);
|
2015-07-09 16:50:13 +03:00
|
|
|
EventNotifier *n = &s->peers[s->vm_id].eventfds[vector];
|
ivshmem: Don't update non-existent MSI routes
As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
QEMU crashes with:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
if the ivshmem device is configured with more vectors than what the server
supports. This is caused by the ivshmem_vector_unmask() being called on
vectors that have not been initialized by ivshmem_add_kvm_msi_virq().
This commit fixes it by adding a simple check to the mask and unmask
callbacks.
Note that the opposite mismatch, if the server supplies more vectors than
what the device is configured for, is already handled and leads to output
like:
Too many eventfd received, device has 1 vectors
To reproduce the assert, run:
ivshmem-server -n 0
and QEMU with:
-device ivshmem-doorbell,chardev=iv
-chardev socket,path=/tmp/ivshmem_socket,id=iv
then load the Windows driver, at the time of writing available at:
https://github.com/virtio-win/kvm-guest-drivers-windows/tree/master/ivshmem
The issue is believed to have been masked by other guest drivers, notably
Linux ones, not enabling MSI-X on the device.
Fixes: 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications")
Signed-off-by: Ladi Prosek <lprosek@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20171211072110.9058-2-lprosek@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-12-11 10:21:07 +03:00
|
|
|
MSIVector *v = &s->msi_vectors[vector];
|
2015-07-09 16:50:13 +03:00
|
|
|
int ret;
|
|
|
|
|
|
|
|
IVSHMEM_DPRINTF("vector mask %p %d\n", dev, vector);
|
ivshmem: Don't update non-existent MSI routes
As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
QEMU crashes with:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
if the ivshmem device is configured with more vectors than what the server
supports. This is caused by the ivshmem_vector_unmask() being called on
vectors that have not been initialized by ivshmem_add_kvm_msi_virq().
This commit fixes it by adding a simple check to the mask and unmask
callbacks.
Note that the opposite mismatch, if the server supplies more vectors than
what the device is configured for, is already handled and leads to output
like:
Too many eventfd received, device has 1 vectors
To reproduce the assert, run:
ivshmem-server -n 0
and QEMU with:
-device ivshmem-doorbell,chardev=iv
-chardev socket,path=/tmp/ivshmem_socket,id=iv
then load the Windows driver, at the time of writing available at:
https://github.com/virtio-win/kvm-guest-drivers-windows/tree/master/ivshmem
The issue is believed to have been masked by other guest drivers, notably
Linux ones, not enabling MSI-X on the device.
Fixes: 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications")
Signed-off-by: Ladi Prosek <lprosek@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20171211072110.9058-2-lprosek@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-12-11 10:21:07 +03:00
|
|
|
if (!v->pdev) {
|
|
|
|
error_report("ivshmem: vector %d route does not exist", vector);
|
|
|
|
return;
|
|
|
|
}
|
2017-12-11 10:21:08 +03:00
|
|
|
assert(v->unmasked);
|
2015-07-09 16:50:13 +03:00
|
|
|
|
ivshmem: Don't update non-existent MSI routes
As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
QEMU crashes with:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
if the ivshmem device is configured with more vectors than what the server
supports. This is caused by the ivshmem_vector_unmask() being called on
vectors that have not been initialized by ivshmem_add_kvm_msi_virq().
This commit fixes it by adding a simple check to the mask and unmask
callbacks.
Note that the opposite mismatch, if the server supplies more vectors than
what the device is configured for, is already handled and leads to output
like:
Too many eventfd received, device has 1 vectors
To reproduce the assert, run:
ivshmem-server -n 0
and QEMU with:
-device ivshmem-doorbell,chardev=iv
-chardev socket,path=/tmp/ivshmem_socket,id=iv
then load the Windows driver, at the time of writing available at:
https://github.com/virtio-win/kvm-guest-drivers-windows/tree/master/ivshmem
The issue is believed to have been masked by other guest drivers, notably
Linux ones, not enabling MSI-X on the device.
Fixes: 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications")
Signed-off-by: Ladi Prosek <lprosek@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20171211072110.9058-2-lprosek@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-12-11 10:21:07 +03:00
|
|
|
ret = kvm_irqchip_remove_irqfd_notifier_gsi(kvm_state, n, v->virq);
|
2017-12-11 10:21:08 +03:00
|
|
|
if (ret < 0) {
|
2015-07-09 16:50:13 +03:00
|
|
|
error_report("remove_irqfd_notifier_gsi failed");
|
2017-12-11 10:21:08 +03:00
|
|
|
return;
|
2015-07-09 16:50:13 +03:00
|
|
|
}
|
2017-12-11 10:21:08 +03:00
|
|
|
v->unmasked = false;
|
2015-07-09 16:50:13 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void ivshmem_vector_poll(PCIDevice *dev,
|
|
|
|
unsigned int vector_start,
|
|
|
|
unsigned int vector_end)
|
|
|
|
{
|
2016-03-15 21:34:51 +03:00
|
|
|
IVShmemState *s = IVSHMEM_COMMON(dev);
|
2015-07-09 16:50:13 +03:00
|
|
|
unsigned int vector;
|
|
|
|
|
|
|
|
IVSHMEM_DPRINTF("vector poll %p %d-%d\n", dev, vector_start, vector_end);
|
|
|
|
|
|
|
|
vector_end = MIN(vector_end, s->vectors);
|
|
|
|
|
|
|
|
for (vector = vector_start; vector < vector_end; vector++) {
|
|
|
|
EventNotifier *notifier = &s->peers[s->vm_id].eventfds[vector];
|
|
|
|
|
|
|
|
if (!msix_is_masked(dev, vector)) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (event_notifier_test_and_clear(notifier)) {
|
|
|
|
msix_set_pending(dev, vector);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-12-21 14:10:13 +03:00
|
|
|
static void watch_vector_notifier(IVShmemState *s, EventNotifier *n,
|
|
|
|
int vector)
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
{
|
2012-07-05 19:16:25 +04:00
|
|
|
int eventfd = event_notifier_get_fd(n);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:36 +03:00
|
|
|
assert(!s->msi_vectors[vector].pdev);
|
2015-12-21 14:10:13 +03:00
|
|
|
s->msi_vectors[vector].pdev = PCI_DEVICE(s);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2015-12-21 14:10:13 +03:00
|
|
|
qemu_set_fd_handler(eventfd, ivshmem_vector_notify,
|
|
|
|
NULL, &s->msi_vectors[vector]);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2012-07-05 19:16:25 +04:00
|
|
|
static void ivshmem_add_eventfd(IVShmemState *s, int posn, int i)
|
|
|
|
{
|
|
|
|
memory_region_add_eventfd(&s->ivshmem_mmio,
|
|
|
|
DOORBELL,
|
|
|
|
4,
|
|
|
|
true,
|
|
|
|
(posn << 16) | i,
|
2012-07-05 19:16:27 +04:00
|
|
|
&s->peers[posn].eventfds[i]);
|
2012-07-05 19:16:25 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
static void ivshmem_del_eventfd(IVShmemState *s, int posn, int i)
|
|
|
|
{
|
|
|
|
memory_region_del_eventfd(&s->ivshmem_mmio,
|
|
|
|
DOORBELL,
|
|
|
|
4,
|
|
|
|
true,
|
|
|
|
(posn << 16) | i,
|
2012-07-05 19:16:27 +04:00
|
|
|
&s->peers[posn].eventfds[i]);
|
2012-07-05 19:16:25 +04:00
|
|
|
}
|
|
|
|
|
2015-06-23 14:38:46 +03:00
|
|
|
static void close_peer_eventfds(IVShmemState *s, int posn)
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
{
|
2015-06-23 14:38:46 +03:00
|
|
|
int i, n;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
ivshmem: Plug leaks on unplug, fix peer disconnect
close_peer_eventfds() cleans up three things: ioeventfd triggers if
they exist, eventfds, and the array to store them.
Commit 98609cd (v1.2.0) fixed it not to clean up ioeventfd triggers
when they don't exist (property ioeventfd=off, which is the default).
Unfortunately, the fix also made it skip cleanup of the eventfds and
the array then. This is a memory and file descriptor leak on unplug.
Additionally, the reset of nb_eventfds is skipped. Doesn't matter on
unplug. On peer disconnect, however, this permanently wedges the
interrupt vectors used for that peer's ID. The eventfds stay behind,
but aren't connected to a peer anymore. When the ID gets recycled for
a new peer, the new peer's eventfds get assigned to vectors after the
old ones. Commonly, the device's number of vectors matches the
server's, so the new ones get dropped with a "Too many eventfd
received" message. Interrupts either don't work (common case) or go
to the wrong vector.
Fix by narrowing the conditional to just the ioeventfd trigger
cleanup.
While there, move the "invalid" peer check to the only caller where it
can actually happen, and tighten it to reject own ID.
Cc: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-25-git-send-email-armbru@redhat.com>
2016-03-15 21:34:39 +03:00
|
|
|
assert(posn >= 0 && posn < s->nb_peers);
|
2015-06-23 14:38:46 +03:00
|
|
|
n = s->peers[posn].nb_eventfds;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
ivshmem: Plug leaks on unplug, fix peer disconnect
close_peer_eventfds() cleans up three things: ioeventfd triggers if
they exist, eventfds, and the array to store them.
Commit 98609cd (v1.2.0) fixed it not to clean up ioeventfd triggers
when they don't exist (property ioeventfd=off, which is the default).
Unfortunately, the fix also made it skip cleanup of the eventfds and
the array then. This is a memory and file descriptor leak on unplug.
Additionally, the reset of nb_eventfds is skipped. Doesn't matter on
unplug. On peer disconnect, however, this permanently wedges the
interrupt vectors used for that peer's ID. The eventfds stay behind,
but aren't connected to a peer anymore. When the ID gets recycled for
a new peer, the new peer's eventfds get assigned to vectors after the
old ones. Commonly, the device's number of vectors matches the
server's, so the new ones get dropped with a "Too many eventfd
received" message. Interrupts either don't work (common case) or go
to the wrong vector.
Fix by narrowing the conditional to just the ioeventfd trigger
cleanup.
While there, move the "invalid" peer check to the only caller where it
can actually happen, and tighten it to reject own ID.
Cc: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-25-git-send-email-armbru@redhat.com>
2016-03-15 21:34:39 +03:00
|
|
|
if (ivshmem_has_feature(s, IVSHMEM_IOEVENTFD)) {
|
|
|
|
memory_region_transaction_begin();
|
|
|
|
for (i = 0; i < n; i++) {
|
|
|
|
ivshmem_del_eventfd(s, posn, i);
|
|
|
|
}
|
|
|
|
memory_region_transaction_commit();
|
2012-07-05 19:16:26 +04:00
|
|
|
}
|
ivshmem: Plug leaks on unplug, fix peer disconnect
close_peer_eventfds() cleans up three things: ioeventfd triggers if
they exist, eventfds, and the array to store them.
Commit 98609cd (v1.2.0) fixed it not to clean up ioeventfd triggers
when they don't exist (property ioeventfd=off, which is the default).
Unfortunately, the fix also made it skip cleanup of the eventfds and
the array then. This is a memory and file descriptor leak on unplug.
Additionally, the reset of nb_eventfds is skipped. Doesn't matter on
unplug. On peer disconnect, however, this permanently wedges the
interrupt vectors used for that peer's ID. The eventfds stay behind,
but aren't connected to a peer anymore. When the ID gets recycled for
a new peer, the new peer's eventfds get assigned to vectors after the
old ones. Commonly, the device's number of vectors matches the
server's, so the new ones get dropped with a "Too many eventfd
received" message. Interrupts either don't work (common case) or go
to the wrong vector.
Fix by narrowing the conditional to just the ioeventfd trigger
cleanup.
While there, move the "invalid" peer check to the only caller where it
can actually happen, and tighten it to reject own ID.
Cc: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-25-git-send-email-armbru@redhat.com>
2016-03-15 21:34:39 +03:00
|
|
|
|
2015-06-23 14:38:46 +03:00
|
|
|
for (i = 0; i < n; i++) {
|
2012-07-05 19:16:25 +04:00
|
|
|
event_notifier_cleanup(&s->peers[posn].eventfds[i]);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2011-08-21 07:09:37 +04:00
|
|
|
g_free(s->peers[posn].eventfds);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
s->peers[posn].nb_eventfds = 0;
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:37 +03:00
|
|
|
static void resize_peers(IVShmemState *s, int nb_peers)
|
2014-09-15 20:40:07 +04:00
|
|
|
{
|
2016-03-15 21:34:37 +03:00
|
|
|
int old_nb_peers = s->nb_peers;
|
|
|
|
int i;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:37 +03:00
|
|
|
assert(nb_peers > old_nb_peers);
|
|
|
|
IVSHMEM_DPRINTF("bumping storage to %d peers\n", nb_peers);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:37 +03:00
|
|
|
s->peers = g_realloc(s->peers, nb_peers * sizeof(Peer));
|
|
|
|
s->nb_peers = nb_peers;
|
2015-09-15 18:21:37 +03:00
|
|
|
|
2016-03-15 21:34:37 +03:00
|
|
|
for (i = old_nb_peers; i < nb_peers; i++) {
|
|
|
|
s->peers[i].eventfds = g_new0(EventNotifier, s->vectors);
|
|
|
|
s->peers[i].nb_eventfds = 0;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
static void ivshmem_add_kvm_msi_virq(IVShmemState *s, int vector,
|
|
|
|
Error **errp)
|
2015-07-09 16:50:13 +03:00
|
|
|
{
|
|
|
|
PCIDevice *pdev = PCI_DEVICE(s);
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
IVSHMEM_DPRINTF("ivshmem_add_kvm_msi_virq vector:%d\n", vector);
|
2016-03-15 21:34:36 +03:00
|
|
|
assert(!s->msi_vectors[vector].pdev);
|
2015-07-09 16:50:13 +03:00
|
|
|
|
2016-07-14 08:56:30 +03:00
|
|
|
ret = kvm_irqchip_add_msi_route(kvm_state, vector, pdev);
|
2015-07-09 16:50:13 +03:00
|
|
|
if (ret < 0) {
|
2016-03-15 21:34:41 +03:00
|
|
|
error_setg(errp, "kvm_irqchip_add_msi_route failed");
|
|
|
|
return;
|
2015-07-09 16:50:13 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
s->msi_vectors[vector].virq = ret;
|
|
|
|
s->msi_vectors[vector].pdev = pdev;
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
static void setup_interrupt(IVShmemState *s, int vector, Error **errp)
|
2015-07-09 16:50:13 +03:00
|
|
|
{
|
|
|
|
EventNotifier *n = &s->peers[s->vm_id].eventfds[vector];
|
|
|
|
bool with_irqfd = kvm_msi_via_irqfd_enabled() &&
|
|
|
|
ivshmem_has_feature(s, IVSHMEM_MSI);
|
|
|
|
PCIDevice *pdev = PCI_DEVICE(s);
|
2016-03-15 21:34:41 +03:00
|
|
|
Error *err = NULL;
|
2015-07-09 16:50:13 +03:00
|
|
|
|
|
|
|
IVSHMEM_DPRINTF("setting up interrupt for vector: %d\n", vector);
|
|
|
|
|
|
|
|
if (!with_irqfd) {
|
2016-03-15 21:34:26 +03:00
|
|
|
IVSHMEM_DPRINTF("with eventfd\n");
|
2015-12-21 14:10:13 +03:00
|
|
|
watch_vector_notifier(s, n, vector);
|
2015-07-09 16:50:13 +03:00
|
|
|
} else if (msix_enabled(pdev)) {
|
2016-03-15 21:34:26 +03:00
|
|
|
IVSHMEM_DPRINTF("with irqfd\n");
|
2016-03-15 21:34:41 +03:00
|
|
|
ivshmem_add_kvm_msi_virq(s, vector, &err);
|
|
|
|
if (err) {
|
|
|
|
error_propagate(errp, err);
|
2015-07-09 16:50:13 +03:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!msix_is_masked(pdev, vector)) {
|
|
|
|
kvm_irqchip_add_irqfd_notifier_gsi(kvm_state, n, NULL,
|
|
|
|
s->msi_vectors[vector].virq);
|
2016-03-15 21:34:41 +03:00
|
|
|
/* TODO handle error */
|
2015-07-09 16:50:13 +03:00
|
|
|
}
|
|
|
|
} else {
|
|
|
|
/* it will be delayed until msix is enabled, in write_config */
|
2016-03-15 21:34:26 +03:00
|
|
|
IVSHMEM_DPRINTF("with irqfd, delayed until msix enabled\n");
|
2015-07-09 16:50:13 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
static void process_msg_shmem(IVShmemState *s, int fd, Error **errp)
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
{
|
2017-06-02 17:12:25 +03:00
|
|
|
Error *local_err = NULL;
|
2016-03-15 21:34:48 +03:00
|
|
|
struct stat buf;
|
2016-03-15 21:34:51 +03:00
|
|
|
size_t size;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:47 +03:00
|
|
|
if (s->ivshmem_bar2) {
|
2016-03-15 21:34:41 +03:00
|
|
|
error_setg(errp, "server sent unexpected shared memory message");
|
2016-03-15 21:34:38 +03:00
|
|
|
close(fd);
|
2015-06-23 18:56:37 +03:00
|
|
|
return;
|
2014-09-15 20:40:05 +04:00
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:48 +03:00
|
|
|
if (fstat(fd, &buf) < 0) {
|
|
|
|
error_setg_errno(errp, errno,
|
|
|
|
"can't determine size of shared memory sent by server");
|
|
|
|
close(fd);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:51 +03:00
|
|
|
size = buf.st_size;
|
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
/* mmap the region and map into the BAR2 */
|
2017-06-02 17:12:25 +03:00
|
|
|
memory_region_init_ram_from_fd(&s->server_bar2, OBJECT(s),
|
2021-01-29 19:46:04 +03:00
|
|
|
"ivshmem.bar2", size, true, fd, 0,
|
|
|
|
&local_err);
|
2017-06-02 17:12:25 +03:00
|
|
|
if (local_err) {
|
|
|
|
error_propagate(errp, local_err);
|
2016-03-15 21:34:38 +03:00
|
|
|
return;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
2017-06-02 17:12:25 +03:00
|
|
|
|
2016-03-15 21:34:47 +03:00
|
|
|
s->ivshmem_bar2 = &s->server_bar2;
|
2016-03-15 21:34:38 +03:00
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
static void process_msg_disconnect(IVShmemState *s, uint16_t posn,
|
|
|
|
Error **errp)
|
2016-03-15 21:34:38 +03:00
|
|
|
{
|
|
|
|
IVSHMEM_DPRINTF("posn %d has gone away\n", posn);
|
ivshmem: Plug leaks on unplug, fix peer disconnect
close_peer_eventfds() cleans up three things: ioeventfd triggers if
they exist, eventfds, and the array to store them.
Commit 98609cd (v1.2.0) fixed it not to clean up ioeventfd triggers
when they don't exist (property ioeventfd=off, which is the default).
Unfortunately, the fix also made it skip cleanup of the eventfds and
the array then. This is a memory and file descriptor leak on unplug.
Additionally, the reset of nb_eventfds is skipped. Doesn't matter on
unplug. On peer disconnect, however, this permanently wedges the
interrupt vectors used for that peer's ID. The eventfds stay behind,
but aren't connected to a peer anymore. When the ID gets recycled for
a new peer, the new peer's eventfds get assigned to vectors after the
old ones. Commonly, the device's number of vectors matches the
server's, so the new ones get dropped with a "Too many eventfd
received" message. Interrupts either don't work (common case) or go
to the wrong vector.
Fix by narrowing the conditional to just the ioeventfd trigger
cleanup.
While there, move the "invalid" peer check to the only caller where it
can actually happen, and tighten it to reject own ID.
Cc: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-25-git-send-email-armbru@redhat.com>
2016-03-15 21:34:39 +03:00
|
|
|
if (posn >= s->nb_peers || posn == s->vm_id) {
|
2016-03-15 21:34:41 +03:00
|
|
|
error_setg(errp, "invalid peer %d", posn);
|
ivshmem: Plug leaks on unplug, fix peer disconnect
close_peer_eventfds() cleans up three things: ioeventfd triggers if
they exist, eventfds, and the array to store them.
Commit 98609cd (v1.2.0) fixed it not to clean up ioeventfd triggers
when they don't exist (property ioeventfd=off, which is the default).
Unfortunately, the fix also made it skip cleanup of the eventfds and
the array then. This is a memory and file descriptor leak on unplug.
Additionally, the reset of nb_eventfds is skipped. Doesn't matter on
unplug. On peer disconnect, however, this permanently wedges the
interrupt vectors used for that peer's ID. The eventfds stay behind,
but aren't connected to a peer anymore. When the ID gets recycled for
a new peer, the new peer's eventfds get assigned to vectors after the
old ones. Commonly, the device's number of vectors matches the
server's, so the new ones get dropped with a "Too many eventfd
received" message. Interrupts either don't work (common case) or go
to the wrong vector.
Fix by narrowing the conditional to just the ioeventfd trigger
cleanup.
While there, move the "invalid" peer check to the only caller where it
can actually happen, and tighten it to reject own ID.
Cc: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-25-git-send-email-armbru@redhat.com>
2016-03-15 21:34:39 +03:00
|
|
|
return;
|
|
|
|
}
|
2016-03-15 21:34:38 +03:00
|
|
|
close_peer_eventfds(s, posn);
|
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
static void process_msg_connect(IVShmemState *s, uint16_t posn, int fd,
|
|
|
|
Error **errp)
|
2016-03-15 21:34:38 +03:00
|
|
|
{
|
|
|
|
Peer *peer = &s->peers[posn];
|
|
|
|
int vector;
|
2015-06-19 13:19:55 +03:00
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
/*
|
|
|
|
* The N-th connect message for this peer comes with the file
|
|
|
|
* descriptor for vector N-1. Count messages to find the vector.
|
|
|
|
*/
|
|
|
|
if (peer->nb_eventfds >= s->vectors) {
|
2016-03-15 21:34:41 +03:00
|
|
|
error_setg(errp, "Too many eventfd received, device has %d vectors",
|
|
|
|
s->vectors);
|
2016-03-15 21:34:38 +03:00
|
|
|
close(fd);
|
2015-06-19 13:21:46 +03:00
|
|
|
return;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
2016-03-15 21:34:38 +03:00
|
|
|
vector = peer->nb_eventfds++;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
IVSHMEM_DPRINTF("eventfds[%d][%d] = %d\n", posn, vector, fd);
|
|
|
|
event_notifier_init_fd(&peer->eventfds[vector], fd);
|
|
|
|
fcntl_setfl(fd, O_NONBLOCK); /* msix/irqfd poll non block */
|
2015-06-23 13:55:41 +03:00
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
if (posn == s->vm_id) {
|
2016-03-15 21:34:41 +03:00
|
|
|
setup_interrupt(s, vector, errp);
|
|
|
|
/* TODO do we need to handle the error? */
|
2016-03-15 21:34:38 +03:00
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
if (ivshmem_has_feature(s, IVSHMEM_IOEVENTFD)) {
|
|
|
|
ivshmem_add_eventfd(s, posn, vector);
|
|
|
|
}
|
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
static void process_msg(IVShmemState *s, int64_t msg, int fd, Error **errp)
|
2016-03-15 21:34:38 +03:00
|
|
|
{
|
|
|
|
IVSHMEM_DPRINTF("posn is %" PRId64 ", fd is %d\n", msg, fd);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
if (msg < -1 || msg > IVSHMEM_MAX_PEERS) {
|
2016-03-15 21:34:41 +03:00
|
|
|
error_setg(errp, "server sent invalid message %" PRId64, msg);
|
2016-03-15 21:34:38 +03:00
|
|
|
close(fd);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
if (msg == -1) {
|
2016-03-15 21:34:41 +03:00
|
|
|
process_msg_shmem(s, fd, errp);
|
2015-06-23 15:07:11 +03:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
if (msg >= s->nb_peers) {
|
|
|
|
resize_peers(s, msg + 1);
|
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
if (fd >= 0) {
|
2016-03-15 21:34:41 +03:00
|
|
|
process_msg_connect(s, msg, fd, errp);
|
2016-03-15 21:34:38 +03:00
|
|
|
} else {
|
2016-03-15 21:34:41 +03:00
|
|
|
process_msg_disconnect(s, msg, errp);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
2016-03-15 21:34:38 +03:00
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2016-03-15 21:34:44 +03:00
|
|
|
static int ivshmem_can_receive(void *opaque)
|
|
|
|
{
|
|
|
|
IVShmemState *s = opaque;
|
|
|
|
|
|
|
|
assert(s->msg_buffered_bytes < sizeof(s->msg_buf));
|
|
|
|
return sizeof(s->msg_buf) - s->msg_buffered_bytes;
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:38 +03:00
|
|
|
static void ivshmem_read(void *opaque, const uint8_t *buf, int size)
|
|
|
|
{
|
|
|
|
IVShmemState *s = opaque;
|
2016-03-15 21:34:41 +03:00
|
|
|
Error *err = NULL;
|
2016-03-15 21:34:38 +03:00
|
|
|
int fd;
|
|
|
|
int64_t msg;
|
|
|
|
|
2016-03-15 21:34:44 +03:00
|
|
|
assert(size >= 0 && s->msg_buffered_bytes + size <= sizeof(s->msg_buf));
|
|
|
|
memcpy((unsigned char *)&s->msg_buf + s->msg_buffered_bytes, buf, size);
|
|
|
|
s->msg_buffered_bytes += size;
|
|
|
|
if (s->msg_buffered_bytes < sizeof(s->msg_buf)) {
|
2016-03-15 21:34:38 +03:00
|
|
|
return;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
2016-03-15 21:34:44 +03:00
|
|
|
msg = le64_to_cpu(s->msg_buf);
|
|
|
|
s->msg_buffered_bytes = 0;
|
2016-03-15 21:34:38 +03:00
|
|
|
|
2016-10-22 12:52:55 +03:00
|
|
|
fd = qemu_chr_fe_get_msgfd(&s->server_chr);
|
2016-03-15 21:34:38 +03:00
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
process_msg(s, msg, fd, &err);
|
|
|
|
if (err) {
|
|
|
|
error_report_err(err);
|
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
static int64_t ivshmem_recv_msg(IVShmemState *s, int *pfd, Error **errp)
|
2015-06-16 18:43:34 +03:00
|
|
|
{
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
int64_t msg;
|
|
|
|
int n, ret;
|
|
|
|
|
|
|
|
n = 0;
|
|
|
|
do {
|
2016-10-22 12:52:55 +03:00
|
|
|
ret = qemu_chr_fe_read_all(&s->server_chr, (uint8_t *)&msg + n,
|
|
|
|
sizeof(msg) - n);
|
2017-07-27 05:42:08 +03:00
|
|
|
if (ret < 0) {
|
|
|
|
if (ret == -EINTR) {
|
|
|
|
continue;
|
|
|
|
}
|
2016-03-15 21:34:41 +03:00
|
|
|
error_setg_errno(errp, -ret, "read from server failed");
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
return INT64_MIN;
|
|
|
|
}
|
|
|
|
n += ret;
|
|
|
|
} while (n < sizeof(msg));
|
2015-06-16 18:43:34 +03:00
|
|
|
|
2016-10-22 12:52:55 +03:00
|
|
|
*pfd = qemu_chr_fe_get_msgfd(&s->server_chr);
|
2017-08-30 16:39:03 +03:00
|
|
|
return le64_to_cpu(msg);
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
}
|
2015-06-16 18:43:34 +03:00
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
static void ivshmem_recv_setup(IVShmemState *s, Error **errp)
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
{
|
2016-03-15 21:34:41 +03:00
|
|
|
Error *err = NULL;
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
int64_t msg;
|
|
|
|
int fd;
|
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
msg = ivshmem_recv_msg(s, &fd, &err);
|
|
|
|
if (err) {
|
|
|
|
error_propagate(errp, err);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
if (msg != IVSHMEM_PROTOCOL_VERSION) {
|
|
|
|
error_setg(errp, "server sent version %" PRId64 ", expecting %d",
|
|
|
|
msg, IVSHMEM_PROTOCOL_VERSION);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
if (fd != -1) {
|
|
|
|
error_setg(errp, "server sent invalid version message");
|
2015-06-16 18:43:34 +03:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:42 +03:00
|
|
|
/*
|
|
|
|
* ivshmem-server sends the remaining initial messages in a fixed
|
|
|
|
* order, but the device has always accepted them in any order.
|
|
|
|
* Stay as compatible as practical, just in case people use
|
|
|
|
* servers that behave differently.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* ivshmem_device_spec.txt has always required the ID message
|
|
|
|
* right here, and ivshmem-server has always complied. However,
|
|
|
|
* older versions of the device accepted it out of order, but
|
|
|
|
* broke when an interrupt setup message arrived before it.
|
|
|
|
*/
|
|
|
|
msg = ivshmem_recv_msg(s, &fd, &err);
|
|
|
|
if (err) {
|
|
|
|
error_propagate(errp, err);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
if (fd != -1 || msg < 0 || msg > IVSHMEM_MAX_PEERS) {
|
|
|
|
error_setg(errp, "server sent invalid ID message");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
s->vm_id = msg;
|
|
|
|
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
/*
|
|
|
|
* Receive more messages until we got shared memory.
|
|
|
|
*/
|
|
|
|
do {
|
2016-03-15 21:34:41 +03:00
|
|
|
msg = ivshmem_recv_msg(s, &fd, &err);
|
|
|
|
if (err) {
|
|
|
|
error_propagate(errp, err);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
process_msg(s, msg, fd, &err);
|
|
|
|
if (err) {
|
|
|
|
error_propagate(errp, err);
|
|
|
|
return;
|
|
|
|
}
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
} while (msg != -1);
|
2016-03-15 21:34:41 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* This function must either map the shared memory or fail. The
|
|
|
|
* loop above ensures that: it terminates normally only after it
|
|
|
|
* successfully processed the server's shared memory message.
|
|
|
|
* Assert that actually mapped the shared memory:
|
|
|
|
*/
|
2016-03-15 21:34:47 +03:00
|
|
|
assert(s->ivshmem_bar2);
|
2015-06-16 18:43:34 +03:00
|
|
|
}
|
|
|
|
|
2011-12-05 23:48:43 +04:00
|
|
|
/* Select the MSI-X vectors used by device.
|
|
|
|
* ivshmem maps events to vectors statically, so
|
|
|
|
* we just enable all vectors on init and after reset. */
|
ivshmem: Clean up MSI-X conditions
There are three predicates related to MSI-X:
* ivshmem_has_feature(s, IVSHMEM_MSI) is true unless the non-MSI-X
variant of the device is selected with msi=off.
* msix_present() is true when the device has the PCI capability MSI-X.
It's initially false, and becomes true during successful realize of
the MSI-X variant of the device. Thus, it's the same as
ivshmem_has_feature(s, IVSHMEM_MSI) for realized devices.
* msix_enabled() is true when msix_present() is true and guest software
has enabled MSI-X.
Code that differs between the non-MSI-X and the MSI-X variant of the
device needs to be guarded by ivshmem_has_feature(s, IVSHMEM_MSI) or
by msix_present(), except the latter works only for realized devices.
Code that depends on whether MSI-X is in use needs to be guarded with
msix_enabled().
Code review led me to two minor messes:
* ivshmem_vector_notify() calls msix_notify() even when
!msix_enabled(), unlike most other MSI-X-capable devices. As far as
I can tell, msix_notify() does nothing when !msix_enabled(). Add
the guard anyway.
* Most callers of ivshmem_use_msix() guard it with
ivshmem_has_feature(s, IVSHMEM_MSI). Not necessary, because
ivshmem_use_msix() does nothing when !msix_present(). That's
ivshmem's only use of msix_present(), though. Guard it
consistently, and drop the now redundant msix_present() check.
While there, rename ivshmem_use_msix() to ivshmem_msix_vector_use().
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <1458066895-20632-20-git-send-email-armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2016-03-15 21:34:34 +03:00
|
|
|
static void ivshmem_msix_vector_use(IVShmemState *s)
|
2011-12-05 23:48:43 +04:00
|
|
|
{
|
2013-06-30 17:15:15 +04:00
|
|
|
PCIDevice *d = PCI_DEVICE(s);
|
2011-12-05 23:48:43 +04:00
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < s->vectors; i++) {
|
2013-06-30 17:15:15 +04:00
|
|
|
msix_vector_use(d, i);
|
2011-12-05 23:48:43 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-12-11 10:21:10 +03:00
|
|
|
static void ivshmem_disable_irqfd(IVShmemState *s);
|
|
|
|
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
static void ivshmem_reset(DeviceState *d)
|
|
|
|
{
|
2016-03-15 21:34:51 +03:00
|
|
|
IVShmemState *s = IVSHMEM_COMMON(d);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2017-12-11 10:21:10 +03:00
|
|
|
ivshmem_disable_irqfd(s);
|
|
|
|
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
s->intrstatus = 0;
|
2015-06-23 15:13:08 +03:00
|
|
|
s->intrmask = 0;
|
ivshmem: Clean up MSI-X conditions
There are three predicates related to MSI-X:
* ivshmem_has_feature(s, IVSHMEM_MSI) is true unless the non-MSI-X
variant of the device is selected with msi=off.
* msix_present() is true when the device has the PCI capability MSI-X.
It's initially false, and becomes true during successful realize of
the MSI-X variant of the device. Thus, it's the same as
ivshmem_has_feature(s, IVSHMEM_MSI) for realized devices.
* msix_enabled() is true when msix_present() is true and guest software
has enabled MSI-X.
Code that differs between the non-MSI-X and the MSI-X variant of the
device needs to be guarded by ivshmem_has_feature(s, IVSHMEM_MSI) or
by msix_present(), except the latter works only for realized devices.
Code that depends on whether MSI-X is in use needs to be guarded with
msix_enabled().
Code review led me to two minor messes:
* ivshmem_vector_notify() calls msix_notify() even when
!msix_enabled(), unlike most other MSI-X-capable devices. As far as
I can tell, msix_notify() does nothing when !msix_enabled(). Add
the guard anyway.
* Most callers of ivshmem_use_msix() guard it with
ivshmem_has_feature(s, IVSHMEM_MSI). Not necessary, because
ivshmem_use_msix() does nothing when !msix_present(). That's
ivshmem's only use of msix_present(), though. Guard it
consistently, and drop the now redundant msix_present() check.
While there, rename ivshmem_use_msix() to ivshmem_msix_vector_use().
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <1458066895-20632-20-git-send-email-armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2016-03-15 21:34:34 +03:00
|
|
|
if (ivshmem_has_feature(s, IVSHMEM_MSI)) {
|
|
|
|
ivshmem_msix_vector_use(s);
|
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2017-01-17 09:18:48 +03:00
|
|
|
static int ivshmem_setup_interrupts(IVShmemState *s, Error **errp)
|
2011-12-05 23:48:43 +04:00
|
|
|
{
|
2015-12-21 14:08:54 +03:00
|
|
|
/* allocate QEMU callback data for receiving interrupts */
|
|
|
|
s->msi_vectors = g_malloc0(s->vectors * sizeof(MSIVector));
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2015-12-21 14:08:54 +03:00
|
|
|
if (ivshmem_has_feature(s, IVSHMEM_MSI)) {
|
2017-01-17 09:18:48 +03:00
|
|
|
if (msix_init_exclusive_bar(PCI_DEVICE(s), s->vectors, 1, errp)) {
|
2015-12-21 14:08:54 +03:00
|
|
|
return -1;
|
|
|
|
}
|
2012-06-14 22:16:01 +04:00
|
|
|
|
2015-12-21 14:08:54 +03:00
|
|
|
IVSHMEM_DPRINTF("msix initialized (%d vectors)\n", s->vectors);
|
ivshmem: Clean up MSI-X conditions
There are three predicates related to MSI-X:
* ivshmem_has_feature(s, IVSHMEM_MSI) is true unless the non-MSI-X
variant of the device is selected with msi=off.
* msix_present() is true when the device has the PCI capability MSI-X.
It's initially false, and becomes true during successful realize of
the MSI-X variant of the device. Thus, it's the same as
ivshmem_has_feature(s, IVSHMEM_MSI) for realized devices.
* msix_enabled() is true when msix_present() is true and guest software
has enabled MSI-X.
Code that differs between the non-MSI-X and the MSI-X variant of the
device needs to be guarded by ivshmem_has_feature(s, IVSHMEM_MSI) or
by msix_present(), except the latter works only for realized devices.
Code that depends on whether MSI-X is in use needs to be guarded with
msix_enabled().
Code review led me to two minor messes:
* ivshmem_vector_notify() calls msix_notify() even when
!msix_enabled(), unlike most other MSI-X-capable devices. As far as
I can tell, msix_notify() does nothing when !msix_enabled(). Add
the guard anyway.
* Most callers of ivshmem_use_msix() guard it with
ivshmem_has_feature(s, IVSHMEM_MSI). Not necessary, because
ivshmem_use_msix() does nothing when !msix_present(). That's
ivshmem's only use of msix_present(), though. Guard it
consistently, and drop the now redundant msix_present() check.
While there, rename ivshmem_use_msix() to ivshmem_msix_vector_use().
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <1458066895-20632-20-git-send-email-armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2016-03-15 21:34:34 +03:00
|
|
|
ivshmem_msix_vector_use(s);
|
2015-12-21 14:08:54 +03:00
|
|
|
}
|
2011-12-05 23:48:43 +04:00
|
|
|
|
2015-06-18 15:59:28 +03:00
|
|
|
return 0;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2017-12-11 10:21:09 +03:00
|
|
|
static void ivshmem_remove_kvm_msi_virq(IVShmemState *s, int vector)
|
|
|
|
{
|
|
|
|
IVSHMEM_DPRINTF("ivshmem_remove_kvm_msi_virq vector:%d\n", vector);
|
|
|
|
|
|
|
|
if (s->msi_vectors[vector].pdev == NULL) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* it was cleaned when masked in the frontend. */
|
|
|
|
kvm_irqchip_release_virq(kvm_state, s->msi_vectors[vector].virq);
|
|
|
|
|
|
|
|
s->msi_vectors[vector].pdev = NULL;
|
|
|
|
}
|
|
|
|
|
2015-07-09 16:50:13 +03:00
|
|
|
static void ivshmem_enable_irqfd(IVShmemState *s)
|
|
|
|
{
|
|
|
|
PCIDevice *pdev = PCI_DEVICE(s);
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < s->peers[s->vm_id].nb_eventfds; i++) {
|
2016-03-15 21:34:41 +03:00
|
|
|
Error *err = NULL;
|
|
|
|
|
|
|
|
ivshmem_add_kvm_msi_virq(s, i, &err);
|
|
|
|
if (err) {
|
|
|
|
error_report_err(err);
|
2017-12-11 10:21:09 +03:00
|
|
|
goto undo;
|
2016-03-15 21:34:41 +03:00
|
|
|
}
|
2015-07-09 16:50:13 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
if (msix_set_vector_notifiers(pdev,
|
|
|
|
ivshmem_vector_unmask,
|
|
|
|
ivshmem_vector_mask,
|
|
|
|
ivshmem_vector_poll)) {
|
|
|
|
error_report("ivshmem: msix_set_vector_notifiers failed");
|
2017-12-11 10:21:09 +03:00
|
|
|
goto undo;
|
2015-07-09 16:50:13 +03:00
|
|
|
}
|
2017-12-11 10:21:09 +03:00
|
|
|
return;
|
2015-07-09 16:50:13 +03:00
|
|
|
|
2017-12-11 10:21:09 +03:00
|
|
|
undo:
|
|
|
|
while (--i >= 0) {
|
|
|
|
ivshmem_remove_kvm_msi_virq(s, i);
|
2015-07-09 16:50:13 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ivshmem_disable_irqfd(IVShmemState *s)
|
|
|
|
{
|
|
|
|
PCIDevice *pdev = PCI_DEVICE(s);
|
|
|
|
int i;
|
|
|
|
|
2017-12-11 10:21:09 +03:00
|
|
|
if (!pdev->msix_vector_use_notifier) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2017-12-11 10:21:08 +03:00
|
|
|
msix_unset_vector_notifiers(pdev);
|
|
|
|
|
2015-07-09 16:50:13 +03:00
|
|
|
for (i = 0; i < s->peers[s->vm_id].nb_eventfds; i++) {
|
2017-12-11 10:21:08 +03:00
|
|
|
/*
|
|
|
|
* MSI-X is already disabled here so msix_unset_vector_notifiers()
|
|
|
|
* didn't call our release notifier. Do it now to keep our masks and
|
|
|
|
* unmasks balanced.
|
|
|
|
*/
|
|
|
|
if (s->msi_vectors[i].unmasked) {
|
|
|
|
ivshmem_vector_mask(pdev, i);
|
|
|
|
}
|
2015-07-09 16:50:13 +03:00
|
|
|
ivshmem_remove_kvm_msi_virq(s, i);
|
|
|
|
}
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ivshmem_write_config(PCIDevice *pdev, uint32_t address,
|
2015-06-18 15:59:28 +03:00
|
|
|
uint32_t val, int len)
|
2011-12-05 23:48:43 +04:00
|
|
|
{
|
2016-03-15 21:34:51 +03:00
|
|
|
IVShmemState *s = IVSHMEM_COMMON(pdev);
|
2015-07-09 16:50:13 +03:00
|
|
|
int is_enabled, was_enabled = msix_enabled(pdev);
|
|
|
|
|
|
|
|
pci_default_write_config(pdev, address, val, len);
|
|
|
|
is_enabled = msix_enabled(pdev);
|
|
|
|
|
2016-03-15 21:34:41 +03:00
|
|
|
if (kvm_msi_via_irqfd_enabled()) {
|
2015-07-09 16:50:13 +03:00
|
|
|
if (!was_enabled && is_enabled) {
|
|
|
|
ivshmem_enable_irqfd(s);
|
|
|
|
} else if (was_enabled && !is_enabled) {
|
|
|
|
ivshmem_disable_irqfd(s);
|
|
|
|
}
|
|
|
|
}
|
2011-12-05 23:48:43 +04:00
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:51 +03:00
|
|
|
static void ivshmem_common_realize(PCIDevice *dev, Error **errp)
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
{
|
2016-03-15 21:34:51 +03:00
|
|
|
IVShmemState *s = IVSHMEM_COMMON(dev);
|
2016-03-15 21:34:32 +03:00
|
|
|
Error *err = NULL;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
uint8_t *pci_conf;
|
|
|
|
|
|
|
|
/* IRQFD requires MSI */
|
|
|
|
if (ivshmem_has_feature(s, IVSHMEM_IOEVENTFD) &&
|
|
|
|
!ivshmem_has_feature(s, IVSHMEM_MSI)) {
|
2015-06-18 15:59:28 +03:00
|
|
|
error_setg(errp, "ioeventfd/irqfd requires MSI");
|
|
|
|
return;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2013-06-30 17:15:15 +04:00
|
|
|
pci_conf = dev->config;
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
pci_conf[PCI_COMMAND] = PCI_COMMAND_IO | PCI_COMMAND_MEMORY;
|
|
|
|
|
2013-06-07 05:25:08 +04:00
|
|
|
memory_region_init_io(&s->ivshmem_mmio, OBJECT(s), &ivshmem_mmio_ops, s,
|
2011-08-08 17:09:12 +04:00
|
|
|
"ivshmem-mmio", IVSHMEM_REG_BAR_SIZE);
|
|
|
|
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
/* region for registers*/
|
2013-06-30 17:15:15 +04:00
|
|
|
pci_register_bar(dev, 0, PCI_BASE_ADDRESS_SPACE_MEMORY,
|
2011-08-08 17:09:31 +04:00
|
|
|
&s->ivshmem_mmio);
|
2011-08-08 17:09:12 +04:00
|
|
|
|
2015-06-30 01:10:16 +03:00
|
|
|
if (s->hostmem != NULL) {
|
|
|
|
IVSHMEM_DPRINTF("using hostmem\n");
|
|
|
|
|
2018-06-19 16:41:36 +03:00
|
|
|
s->ivshmem_bar2 = host_memory_backend_get_memory(s->hostmem);
|
2018-09-26 19:37:09 +03:00
|
|
|
host_memory_backend_set_mapped(s->hostmem, true);
|
2016-03-15 21:34:46 +03:00
|
|
|
} else {
|
2016-12-07 16:20:22 +03:00
|
|
|
Chardev *chr = qemu_chr_fe_get_driver(&s->server_chr);
|
2016-10-22 12:52:55 +03:00
|
|
|
assert(chr);
|
2016-04-12 16:33:10 +03:00
|
|
|
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
IVSHMEM_DPRINTF("using shared memory server (socket = %s)\n",
|
2016-10-22 12:52:55 +03:00
|
|
|
chr->filename);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
2015-06-23 14:38:46 +03:00
|
|
|
/* we allocate enough space for 16 peers and grow as needed */
|
2015-09-15 18:21:37 +03:00
|
|
|
resize_peers(s, 16);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
/*
|
|
|
|
* Receive setup messages from server synchronously.
|
|
|
|
* Older versions did it asynchronously, but that creates a
|
|
|
|
* number of entertaining race conditions.
|
|
|
|
*/
|
2016-03-15 21:34:41 +03:00
|
|
|
ivshmem_recv_setup(s, &err);
|
|
|
|
if (err) {
|
|
|
|
error_propagate(errp, err);
|
|
|
|
return;
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:54 +03:00
|
|
|
if (s->master == ON_OFF_AUTO_ON && s->vm_id != 0) {
|
|
|
|
error_setg(errp,
|
|
|
|
"master must connect to the server before any peers");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2016-10-22 12:52:55 +03:00
|
|
|
qemu_chr_fe_set_handlers(&s->server_chr, ivshmem_can_receive,
|
2017-07-06 15:08:49 +03:00
|
|
|
ivshmem_read, NULL, NULL, s, NULL, true);
|
2016-03-15 21:34:41 +03:00
|
|
|
|
2017-01-17 09:18:48 +03:00
|
|
|
if (ivshmem_setup_interrupts(s, errp) < 0) {
|
|
|
|
error_prepend(errp, "Failed to initialize interrupts: ");
|
ivshmem: Receive shared memory synchronously in realize()
When configured for interrupts (property "chardev" given), we receive
the shared memory from an ivshmem server. We do so asynchronously
after realize() completes, by setting up callbacks with
qemu_chr_add_handlers().
Keeping server I/O out of realize() that way avoids delays due to a
slow server. This is probably relevant only for hot plug.
However, this funny "no shared memory, yet" state of the device also
causes a raft of issues that are hard or impossible to work around:
* The guest is exposed to this state: when we enter and leave it its
shared memory contents is apruptly replaced, and device register
IVPosition changes.
This is a known issue. We document that guests should not access
the shared memory after device initialization until the IVPosition
register becomes non-negative.
For cold plug, the funny state is unlikely to be visible in
practice, because we normally receive the shared memory long before
the guest gets around to mess with the device.
For hot plug, the timing is tighter, but the relative slowness of
PCI device configuration has a good chance to hide the funny state.
In either case, guests complying with the documented procedure are
safe.
* Migration becomes racy.
If migration completes before the shared memory setup completes on
the source, shared memory contents is silently lost. Fortunately,
migration is rather unlikely to win this race.
If the shared memory's ramblock arrives at the destination before
shared memory setup completes, migration fails.
There is no known way for a management application to wait for
shared memory setup to complete.
All you can do is retry failed migration. You can improve your
chances by leaving more time between running the destination QEMU
and the migrate command.
To mitigate silent memory loss, you need to ensure the server
initializes shared memory exactly the same on source and
destination.
These issues are entirely undocumented so far.
I'd expect the server to be almost always fast enough to hide these
issues. But then rare catastrophic races are in a way the worst kind.
This is way more trouble than I'm willing to take from any device.
Kill the funny state by receiving shared memory synchronously in
realize(). If your hot plug hangs, go kill your ivshmem server.
For easier review, this commit only makes the receive synchronous, it
doesn't add the necessary error propagation. Without that, the funny
state persists. The next commit will do that, and kill it off for
real.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-26-git-send-email-armbru@redhat.com>
2016-03-15 21:34:40 +03:00
|
|
|
return;
|
|
|
|
}
|
2016-03-15 21:34:32 +03:00
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:50 +03:00
|
|
|
if (s->master == ON_OFF_AUTO_AUTO) {
|
|
|
|
s->master = s->vm_id == 0 ? ON_OFF_AUTO_ON : ON_OFF_AUTO_OFF;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!ivshmem_is_master(s)) {
|
2016-03-15 21:34:32 +03:00
|
|
|
error_setg(&s->migration_blocker,
|
|
|
|
"Migration is disabled when using feature 'peer mode' in device 'ivshmem'");
|
error: Avoid error_propagate() after migrate_add_blocker()
When migrate_add_blocker(blocker, &errp) is followed by
error_propagate(errp, err), we can often just as well do
migrate_add_blocker(..., errp).
Do that with this Coccinelle script:
@@
expression blocker, err, errp;
expression ret;
@@
- ret = migrate_add_blocker(blocker, &err);
- if (err) {
+ ret = migrate_add_blocker(blocker, errp);
+ if (ret < 0) {
... when != err;
- error_propagate(errp, err);
...
}
@@
expression blocker, err, errp;
@@
- migrate_add_blocker(blocker, &err);
- if (err) {
+ if (migrate_add_blocker(blocker, errp) < 0) {
... when != err;
- error_propagate(errp, err);
...
}
Double-check @err is not used afterwards. Dereferencing it would be
use after free, but checking whether it's null would be legitimate.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Message-Id: <20200707160613.848843-43-armbru@redhat.com>
2020-07-07 19:06:10 +03:00
|
|
|
if (migrate_add_blocker(s->migration_blocker, errp) < 0) {
|
2017-01-16 14:31:53 +03:00
|
|
|
error_free(s->migration_blocker);
|
|
|
|
return;
|
|
|
|
}
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
2017-01-16 14:31:53 +03:00
|
|
|
|
|
|
|
vmstate_register_ram(s->ivshmem_bar2, DEVICE(s));
|
2018-12-19 16:13:25 +03:00
|
|
|
pci_register_bar(PCI_DEVICE(s), 2,
|
|
|
|
PCI_BASE_ADDRESS_SPACE_MEMORY |
|
|
|
|
PCI_BASE_ADDRESS_MEM_PREFETCH |
|
|
|
|
PCI_BASE_ADDRESS_MEM_TYPE_64,
|
|
|
|
s->ivshmem_bar2);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:51 +03:00
|
|
|
static void ivshmem_exit(PCIDevice *dev)
|
|
|
|
{
|
|
|
|
IVShmemState *s = IVSHMEM_COMMON(dev);
|
2015-06-23 13:57:16 +03:00
|
|
|
int i;
|
|
|
|
|
2011-11-15 01:09:44 +04:00
|
|
|
if (s->migration_blocker) {
|
|
|
|
migrate_del_blocker(s->migration_blocker);
|
|
|
|
error_free(s->migration_blocker);
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:47 +03:00
|
|
|
if (memory_region_is_mapped(s->ivshmem_bar2)) {
|
2015-06-30 01:10:16 +03:00
|
|
|
if (!s->hostmem) {
|
2016-03-15 21:34:47 +03:00
|
|
|
void *addr = memory_region_get_ram_ptr(s->ivshmem_bar2);
|
2015-12-21 06:47:34 +03:00
|
|
|
int fd;
|
2015-06-30 01:10:16 +03:00
|
|
|
|
2016-03-15 21:34:51 +03:00
|
|
|
if (munmap(addr, memory_region_size(s->ivshmem_bar2) == -1)) {
|
2015-06-30 01:10:16 +03:00
|
|
|
error_report("Failed to munmap shared memory %s",
|
|
|
|
strerror(errno));
|
|
|
|
}
|
2015-12-21 06:47:34 +03:00
|
|
|
|
2016-03-25 14:30:16 +03:00
|
|
|
fd = memory_region_get_fd(s->ivshmem_bar2);
|
2016-03-15 21:34:47 +03:00
|
|
|
close(fd);
|
2015-06-30 01:10:16 +03:00
|
|
|
}
|
2015-06-23 13:57:16 +03:00
|
|
|
|
2016-03-15 21:34:47 +03:00
|
|
|
vmstate_unregister_ram(s->ivshmem_bar2, DEVICE(dev));
|
2015-06-23 13:57:16 +03:00
|
|
|
}
|
|
|
|
|
2018-09-26 19:37:09 +03:00
|
|
|
if (s->hostmem) {
|
|
|
|
host_memory_backend_set_mapped(s->hostmem, false);
|
|
|
|
}
|
|
|
|
|
2015-06-23 13:57:16 +03:00
|
|
|
if (s->peers) {
|
|
|
|
for (i = 0; i < s->nb_peers; i++) {
|
2015-06-23 14:38:46 +03:00
|
|
|
close_peer_eventfds(s, i);
|
2015-06-23 13:57:16 +03:00
|
|
|
}
|
|
|
|
g_free(s->peers);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ivshmem_has_feature(s, IVSHMEM_MSI)) {
|
|
|
|
msix_uninit_exclusive_bar(dev);
|
|
|
|
}
|
|
|
|
|
2015-07-27 13:59:19 +03:00
|
|
|
g_free(s->msi_vectors);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2015-06-18 15:05:46 +03:00
|
|
|
static int ivshmem_pre_load(void *opaque)
|
|
|
|
{
|
|
|
|
IVShmemState *s = opaque;
|
|
|
|
|
2016-03-15 21:34:50 +03:00
|
|
|
if (!ivshmem_is_master(s)) {
|
2015-06-18 15:05:46 +03:00
|
|
|
error_report("'peer' devices are not migratable");
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ivshmem_post_load(void *opaque, int version_id)
|
|
|
|
{
|
|
|
|
IVShmemState *s = opaque;
|
|
|
|
|
|
|
|
if (ivshmem_has_feature(s, IVSHMEM_MSI)) {
|
ivshmem: Clean up MSI-X conditions
There are three predicates related to MSI-X:
* ivshmem_has_feature(s, IVSHMEM_MSI) is true unless the non-MSI-X
variant of the device is selected with msi=off.
* msix_present() is true when the device has the PCI capability MSI-X.
It's initially false, and becomes true during successful realize of
the MSI-X variant of the device. Thus, it's the same as
ivshmem_has_feature(s, IVSHMEM_MSI) for realized devices.
* msix_enabled() is true when msix_present() is true and guest software
has enabled MSI-X.
Code that differs between the non-MSI-X and the MSI-X variant of the
device needs to be guarded by ivshmem_has_feature(s, IVSHMEM_MSI) or
by msix_present(), except the latter works only for realized devices.
Code that depends on whether MSI-X is in use needs to be guarded with
msix_enabled().
Code review led me to two minor messes:
* ivshmem_vector_notify() calls msix_notify() even when
!msix_enabled(), unlike most other MSI-X-capable devices. As far as
I can tell, msix_notify() does nothing when !msix_enabled(). Add
the guard anyway.
* Most callers of ivshmem_use_msix() guard it with
ivshmem_has_feature(s, IVSHMEM_MSI). Not necessary, because
ivshmem_use_msix() does nothing when !msix_present(). That's
ivshmem's only use of msix_present(), though. Guard it
consistently, and drop the now redundant msix_present() check.
While there, rename ivshmem_use_msix() to ivshmem_msix_vector_use().
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <1458066895-20632-20-git-send-email-armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2016-03-15 21:34:34 +03:00
|
|
|
ivshmem_msix_vector_use(s);
|
2015-06-18 15:05:46 +03:00
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:51 +03:00
|
|
|
static void ivshmem_common_class_init(ObjectClass *klass, void *data)
|
2011-12-04 22:22:06 +04:00
|
|
|
{
|
2011-12-08 07:34:16 +04:00
|
|
|
DeviceClass *dc = DEVICE_CLASS(klass);
|
2011-12-04 22:22:06 +04:00
|
|
|
PCIDeviceClass *k = PCI_DEVICE_CLASS(klass);
|
|
|
|
|
2016-03-15 21:34:51 +03:00
|
|
|
k->realize = ivshmem_common_realize;
|
|
|
|
k->exit = ivshmem_exit;
|
2015-06-18 15:59:28 +03:00
|
|
|
k->config_write = ivshmem_write_config;
|
2012-12-13 13:19:37 +04:00
|
|
|
k->vendor_id = PCI_VENDOR_ID_IVSHMEM;
|
|
|
|
k->device_id = PCI_DEVICE_ID_IVSHMEM;
|
2011-12-04 22:22:06 +04:00
|
|
|
k->class_id = PCI_CLASS_MEMORY_RAM;
|
2016-03-15 21:34:51 +03:00
|
|
|
k->revision = 1;
|
2011-12-08 07:34:16 +04:00
|
|
|
dc->reset = ivshmem_reset;
|
2013-07-29 18:17:45 +04:00
|
|
|
set_bit(DEVICE_CATEGORY_MISC, dc->categories);
|
2015-06-23 14:01:40 +03:00
|
|
|
dc->desc = "Inter-VM shared memory";
|
2011-12-04 22:22:06 +04:00
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:52 +03:00
|
|
|
static const TypeInfo ivshmem_common_info = {
|
|
|
|
.name = TYPE_IVSHMEM_COMMON,
|
|
|
|
.parent = TYPE_PCI_DEVICE,
|
|
|
|
.instance_size = sizeof(IVShmemState),
|
|
|
|
.abstract = true,
|
|
|
|
.class_init = ivshmem_common_class_init,
|
2017-09-27 22:56:34 +03:00
|
|
|
.interfaces = (InterfaceInfo[]) {
|
|
|
|
{ INTERFACE_CONVENTIONAL_PCI_DEVICE },
|
|
|
|
{ },
|
|
|
|
},
|
2016-03-15 21:34:52 +03:00
|
|
|
};
|
2016-03-15 21:34:51 +03:00
|
|
|
|
|
|
|
static const VMStateDescription ivshmem_plain_vmsd = {
|
|
|
|
.name = TYPE_IVSHMEM_PLAIN,
|
|
|
|
.version_id = 0,
|
|
|
|
.minimum_version_id = 0,
|
|
|
|
.pre_load = ivshmem_pre_load,
|
|
|
|
.post_load = ivshmem_post_load,
|
|
|
|
.fields = (VMStateField[]) {
|
|
|
|
VMSTATE_PCI_DEVICE(parent_obj, IVShmemState),
|
|
|
|
VMSTATE_UINT32(intrstatus, IVShmemState),
|
|
|
|
VMSTATE_UINT32(intrmask, IVShmemState),
|
|
|
|
VMSTATE_END_OF_LIST()
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
|
|
|
static Property ivshmem_plain_properties[] = {
|
|
|
|
DEFINE_PROP_ON_OFF_AUTO("master", IVShmemState, master, ON_OFF_AUTO_OFF),
|
2017-07-14 05:15:00 +03:00
|
|
|
DEFINE_PROP_LINK("memdev", IVShmemState, hostmem, TYPE_MEMORY_BACKEND,
|
|
|
|
HostMemoryBackend *),
|
2016-03-15 21:34:51 +03:00
|
|
|
DEFINE_PROP_END_OF_LIST(),
|
|
|
|
};
|
|
|
|
|
2016-04-12 16:33:10 +03:00
|
|
|
static void ivshmem_plain_realize(PCIDevice *dev, Error **errp)
|
|
|
|
{
|
|
|
|
IVShmemState *s = IVSHMEM_COMMON(dev);
|
|
|
|
|
|
|
|
if (!s->hostmem) {
|
|
|
|
error_setg(errp, "You must specify a 'memdev'");
|
|
|
|
return;
|
2017-07-14 05:15:00 +03:00
|
|
|
} else if (host_memory_backend_is_mapped(s->hostmem)) {
|
2020-07-14 19:02:00 +03:00
|
|
|
error_setg(errp, "can't use already busy memdev: %s",
|
|
|
|
object_get_canonical_path_component(OBJECT(s->hostmem)));
|
2017-07-14 05:15:00 +03:00
|
|
|
return;
|
2016-04-12 16:33:10 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
ivshmem_common_realize(dev, errp);
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:51 +03:00
|
|
|
static void ivshmem_plain_class_init(ObjectClass *klass, void *data)
|
|
|
|
{
|
|
|
|
DeviceClass *dc = DEVICE_CLASS(klass);
|
2016-04-12 16:33:10 +03:00
|
|
|
PCIDeviceClass *k = PCI_DEVICE_CLASS(klass);
|
2016-03-15 21:34:51 +03:00
|
|
|
|
2016-04-12 16:33:10 +03:00
|
|
|
k->realize = ivshmem_plain_realize;
|
2020-01-10 18:30:32 +03:00
|
|
|
device_class_set_props(dc, ivshmem_plain_properties);
|
2016-03-15 21:34:51 +03:00
|
|
|
dc->vmsd = &ivshmem_plain_vmsd;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const TypeInfo ivshmem_plain_info = {
|
|
|
|
.name = TYPE_IVSHMEM_PLAIN,
|
|
|
|
.parent = TYPE_IVSHMEM_COMMON,
|
|
|
|
.instance_size = sizeof(IVShmemState),
|
|
|
|
.class_init = ivshmem_plain_class_init,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const VMStateDescription ivshmem_doorbell_vmsd = {
|
|
|
|
.name = TYPE_IVSHMEM_DOORBELL,
|
|
|
|
.version_id = 0,
|
|
|
|
.minimum_version_id = 0,
|
|
|
|
.pre_load = ivshmem_pre_load,
|
|
|
|
.post_load = ivshmem_post_load,
|
|
|
|
.fields = (VMStateField[]) {
|
|
|
|
VMSTATE_PCI_DEVICE(parent_obj, IVShmemState),
|
|
|
|
VMSTATE_MSIX(parent_obj, IVShmemState),
|
|
|
|
VMSTATE_UINT32(intrstatus, IVShmemState),
|
|
|
|
VMSTATE_UINT32(intrmask, IVShmemState),
|
|
|
|
VMSTATE_END_OF_LIST()
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
|
|
|
static Property ivshmem_doorbell_properties[] = {
|
|
|
|
DEFINE_PROP_CHR("chardev", IVShmemState, server_chr),
|
|
|
|
DEFINE_PROP_UINT32("vectors", IVShmemState, vectors, 1),
|
|
|
|
DEFINE_PROP_BIT("ioeventfd", IVShmemState, features, IVSHMEM_IOEVENTFD,
|
|
|
|
true),
|
|
|
|
DEFINE_PROP_ON_OFF_AUTO("master", IVShmemState, master, ON_OFF_AUTO_OFF),
|
|
|
|
DEFINE_PROP_END_OF_LIST(),
|
|
|
|
};
|
|
|
|
|
|
|
|
static void ivshmem_doorbell_init(Object *obj)
|
|
|
|
{
|
|
|
|
IVShmemState *s = IVSHMEM_DOORBELL(obj);
|
|
|
|
|
|
|
|
s->features |= (1 << IVSHMEM_MSI);
|
|
|
|
}
|
|
|
|
|
2016-04-12 16:33:10 +03:00
|
|
|
static void ivshmem_doorbell_realize(PCIDevice *dev, Error **errp)
|
|
|
|
{
|
|
|
|
IVShmemState *s = IVSHMEM_COMMON(dev);
|
|
|
|
|
2017-07-06 15:08:52 +03:00
|
|
|
if (!qemu_chr_fe_backend_connected(&s->server_chr)) {
|
2016-04-12 16:33:10 +03:00
|
|
|
error_setg(errp, "You must specify a 'chardev'");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
ivshmem_common_realize(dev, errp);
|
|
|
|
}
|
|
|
|
|
2016-03-15 21:34:51 +03:00
|
|
|
static void ivshmem_doorbell_class_init(ObjectClass *klass, void *data)
|
|
|
|
{
|
|
|
|
DeviceClass *dc = DEVICE_CLASS(klass);
|
2016-04-12 16:33:10 +03:00
|
|
|
PCIDeviceClass *k = PCI_DEVICE_CLASS(klass);
|
2016-03-15 21:34:51 +03:00
|
|
|
|
2016-04-12 16:33:10 +03:00
|
|
|
k->realize = ivshmem_doorbell_realize;
|
2020-01-10 18:30:32 +03:00
|
|
|
device_class_set_props(dc, ivshmem_doorbell_properties);
|
2016-03-15 21:34:51 +03:00
|
|
|
dc->vmsd = &ivshmem_doorbell_vmsd;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const TypeInfo ivshmem_doorbell_info = {
|
|
|
|
.name = TYPE_IVSHMEM_DOORBELL,
|
|
|
|
.parent = TYPE_IVSHMEM_COMMON,
|
|
|
|
.instance_size = sizeof(IVShmemState),
|
|
|
|
.instance_init = ivshmem_doorbell_init,
|
|
|
|
.class_init = ivshmem_doorbell_class_init,
|
|
|
|
};
|
|
|
|
|
2012-02-09 18:20:55 +04:00
|
|
|
static void ivshmem_register_types(void)
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
{
|
2016-03-15 21:34:51 +03:00
|
|
|
type_register_static(&ivshmem_common_info);
|
|
|
|
type_register_static(&ivshmem_plain_info);
|
|
|
|
type_register_static(&ivshmem_doorbell_info);
|
RESEND: Inter-VM shared memory PCI device
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
Interrupts are supported between multiple VMs by using a shared memory server
by using a chardev socket.
-device ivshmem,size=<size in format accepted by -m>[,shm=<shm name>]
[,chardev=<id>][,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
-chardev socket,path=<path>,id=<id>
The shared memory server, sample programs and init scripts are in a git repo here:
www.gitorious.org/nahanni
Signed-off-by: Cam Macdonell <cam@cs.ualberta.ca>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-07-27 20:54:13 +04:00
|
|
|
}
|
|
|
|
|
2012-02-09 18:20:55 +04:00
|
|
|
type_init(ivshmem_register_types)
|