Hrm. This may not be correct. It looks like there is some interaction between
the primary and secondary here. vtpci_ops must be in shared memory. When I
initialize my secondary, it overwrites the primary's with its address. I just
checked, and without my patch, the secondary's vtpci_ops points t
I just ran into an issue trying to run the client server example application
using virito. Whenever the client (running as a secondary process) tried to
send packets, it would crash. I traced the issue to an invalid vtpci_ops
structure:
(gdb) p *vq->hw->vtpci_ops
$6 = {
read_dev_cfg = 0x756d2
2 matches
Mail list logo
