Eric Blake <ebl...@redhat.com> writes: > On 09/25/2015 08:00 AM, Markus Armbruster wrote: >> VSERPORT_CHANGE is emitted when the guest opens or closes a >> virtio-serial port. The event's member "id" identifies the port. >> >> When several events arrive quickly, throttling drops all but the last >> of them. Because of that, a QMP client must assume that *any* port >> may have changed state when it receives a VSERPORT_CHANGE event and >> throttling may have happened. >> >> Make the event more useful by throttling it for each port separately. >> >> Signed-off-by: Markus Armbruster <arm...@redhat.com> >> --- >> monitor.c | 18 ++++++++++++++++-- >> 1 file changed, 16 insertions(+), 2 deletions(-) >> > > All future differentiation would be added as additional special cases > within the hash functions, but I like this approach for keeping the rest > of the algorithm independent from what the hashing considers as equivalent.
Should that ever become unwieldy, we can easily add indirections right there. > Reviewed-by: Eric Blake <ebl...@redhat.com> Thanks!
