On 08/01/2011 10:53 PM, Michael S. Tsirkin wrote:
>
>
> Just because a memory region becomes visible to the cpu is no reason
> to have a callback. From the device perspective, it can't tell that
> it happened.
BTW this is what qxl does, too, conceptually: on config writes, it peeks
at the bar to detect whether that got unmapped.
Can you elaborate? why? what does it do?
--
error compiling committee.c: too many arguments to function
--
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
