On 21 March 2016 at 20:43, Markus Armbruster <arm...@redhat.com> wrote: > Major issues addressed by this series: > > * The specification document is incomplete and vague. Rewritten. > > * When a peer goes away, and its ID gets reused for another one, > interrupts don't work. > > * When configured for interrupts, we receive shared memory from the > server some time after realize(). This creates a (usually > short-lived) "no shared memory, yet" state. If the guest wins the > race, it is exposed to this state (known issue, if you count burying > in docs/specs/ as "known"). If migration wins the race, it fails or > corrupts memory. > > * Interrupts are unreliable in a (usually small) time window after the > destination peer connects. I believe fixing this will require > changing the client/server protocol, so just document it for now. > > * The device isn't capable to tell guest software whether it is > configured for interrupts. Fix that in a new, backwards-compatible > revision of the guest ABI, and bump the PCI revision. Deprecate the > old revision. > > * The device properties are a confusing mess and badly checked. > Clean that up. > > * Migration with interrupts relies on server behavior not guaranteed > by the specification. Tighten the specification. > > v2: > * PATCH 05: Include ivshmem-test only in configurations that include > the device > * PATCH 36: Fix ivshmem-plain not to assert its nonexistent INTx
Hi -- this appears to be missing the git URL to pull from? thanks -- PMM