Cam Macdonell wrote:
I think there is value for static memory sharing. It can be used for
fast, simple synchronization and communication between guests (and the
host) that use need to share data that needs to be updated frequently
(such as a simple cache or notification system). It may not be a
common task, but I think static sharing has its place and that's what
this device is for at this point.
It would be good to detail a use case for reference.
Then you need a side channel to communicate the information to the
guest.
Couldn't one of the registers in BAR0 be used to store the actual
(non-power-of-two) size?
The PCI config space (where the BARs reside) is a good place for it.
Registers 0x40+ are device specific IIRC.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
