Branch: refs/heads/next
Home: https://github.com/siemens/jailhouse
Commit: 36f9988248fe5bc568f7577a455474a650a9a9b6
https://github.com/siemens/jailhouse/commit/36f9988248fe5bc568f7577a455474a650a9a9b6
Author: Jan Kiszka <[email protected]>
Date: 2016-12-05 (Mon, 05 Dec 2016)
Changed paths:
M hypervisor/ivshmem.c
Log Message:
-----------
core: ivshmem: Fix matching of peers
So far, we created another ivshmem_data structure in case two devices
matched by BDF but not by their shared memory regions. This did not make
sense (ivshmem_find only returns the first BDF match) and it could leak
the data structure when the device was destroyed again.
Change the policy so that we match on BDF but fail creating the second
device in case of region mismatch.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 4fc00369c6f20c83441e41160812a7521f7a5af5
https://github.com/siemens/jailhouse/commit/4fc00369c6f20c83441e41160812a7521f7a5af5
Author: Jan Kiszka <[email protected]>
Date: 2016-12-05 (Mon, 05 Dec 2016)
Changed paths:
M hypervisor/ivshmem.c
Log Message:
-----------
core: ivshmem: Keep BDF also in ivshmem_data structure
Cache the matching BDF of the peer in the ivshmem_data structure. This
will help us when we no longer require slot 0 to be in use.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 2b8e1fc8b0663bd1924395b677b2b59bf7f8ccb4
https://github.com/siemens/jailhouse/commit/2b8e1fc8b0663bd1924395b677b2b59bf7f8ccb4
Author: Jan Kiszka <[email protected]>
Date: 2016-12-05 (Mon, 05 Dec 2016)
Changed paths:
M hypervisor/ivshmem.c
Log Message:
-----------
core: ivshmem: Rework device creation and destruction
Moving device from slot 1 to slot 0 in case the first slot becomes free
had a bug: it didn't update the pointer from pci_device to the
ivshmem_endpoint.
Instead of fixing this, let's take the chance and redesign the
management: Thanks to earlier preparation steps, we can now keep the
device in its original slot. We just need to check during creation which
slot is free (device pointer is NULL) and use that. Now ivpos of an
endpoint always equals the array index in ivshmem_data.eps that the
endpoint uses.
Finally, we can significantly simplify the code by folding ivshmem_find
and ivshmem_connect/disconnect_cell into their callers.
Signed-off-by: Jan Kiszka <[email protected]>
Compare:
https://github.com/siemens/jailhouse/compare/0ce7b1c938f6...2b8e1fc8b066
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
