diff options
| author | Markus Armbruster | 2016-03-15 19:34:54 +0100 |
|---|---|---|
| committer | Markus Armbruster | 2016-03-21 21:29:03 +0100 |
| commit | 62a830b688a93419baa89061b6b5faf8b5e10808 (patch) | |
| tree | 546264772d3bb4ca39b61aa14f13eac1d44eb016 /docs/specs/ivshmem-spec.txt | |
| parent | ivshmem: Drop ivshmem property x-memdev (diff) | |
| download | qemu-62a830b688a93419baa89061b6b5faf8b5e10808.tar.gz qemu-62a830b688a93419baa89061b6b5faf8b5e10808.tar.xz qemu-62a830b688a93419baa89061b6b5faf8b5e10808.zip | |
ivshmem: Require master to have ID zero
Migration with ivshmem needs to be carefully orchestrated to work.
Exactly one peer (the "master") migrates to the destination, all other
peers need to unplug (and disconnect), migrate, plug back (and
reconnect). This is sort of documented in qemu-doc.
If peers connect on the destination before migration completes, the
shared memory can get messed up. This isn't documented anywhere. Fix
that in qemu-doc.
To avoid messing up register IVPosition on migration, the server must
assign the same ID on source and destination. ivshmem-spec.txt leaves
ID assignment unspecified, however.
Amend ivshmem-spec.txt to require the first client to receive ID zero.
The example ivshmem-server complies: it always assigns the first
unused ID.
For a bit of additional safety, enforce ID zero for the master. This
does nothing when we're not using a server, because the ID is zero for
all peers then.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-40-git-send-email-armbru@redhat.com>
Diffstat (limited to 'docs/specs/ivshmem-spec.txt')
| -rw-r--r-- | docs/specs/ivshmem-spec.txt | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/specs/ivshmem-spec.txt b/docs/specs/ivshmem-spec.txt index f3912c0565..a1f5499796 100644 --- a/docs/specs/ivshmem-spec.txt +++ b/docs/specs/ivshmem-spec.txt @@ -164,6 +164,8 @@ For each new client that connects to the server, the server - sends interrupt setup messages to the new client (these contain file descriptors for receiving interrupts). +The first client to connect to the server receives ID zero. + When a client disconnects from the server, the server sends disconnect notifications to the other clients. |