On 12/14/08, Gleb Natapov <[email protected]> wrote: > There is a need for communication channel between host and various > agents that are running inside a VM guest. The channel will be used > for statistic gathering, logging, cut & paste, host screen resolution > changes notification, guest configuration etc.
Isn't this exactly what the firmware configuration device was supposed to be used for? In the list of use cases you gave, I don't see anything that could not be done with it. So, to avoid duplicated functionality, I'd add the missing pieces to the configuration device and if PCI compatibility is desired, the firmware configuration device IO port could be handled by a wrapper PCI device much like what you proposed. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
