On (Sat) 30 Apr 2011 [11:23:42], Alon Levy wrote:
> On Fri, Apr 29, 2011 at 06:26:49PM +0530, Amit Shah wrote:
> > On (Fri) 29 Apr 2011 [14:25:06], Alon Levy wrote:
> > > Instead of calling flush_queued_data when unthrottling, schedule
> > > a bh. That way we can return immediately to the caller, a
On Fri, Apr 29, 2011 at 06:26:49PM +0530, Amit Shah wrote:
> On (Fri) 29 Apr 2011 [14:25:06], Alon Levy wrote:
> > Instead of calling flush_queued_data when unthrottling, schedule
> > a bh. That way we can return immediately to the caller, and the
> > flush uses the same call path as a have_data fo
On (Fri) 29 Apr 2011 [14:25:06], Alon Levy wrote:
> Instead of calling flush_queued_data when unthrottling, schedule
> a bh. That way we can return immediately to the caller, and the
> flush uses the same call path as a have_data for callbackee.
>
> No migration change is required because bh are c
On (Fri) 29 Apr 2011 [14:25:06], Alon Levy wrote:
> Instead of calling flush_queued_data when unthrottling, schedule
> a bh. That way we can return immediately to the caller, and the
> flush uses the same call path as a have_data for callbackee.
>
> No migration change is required because bh are c
Instead of calling flush_queued_data when unthrottling, schedule
a bh. That way we can return immediately to the caller, and the
flush uses the same call path as a have_data for callbackee.
No migration change is required because bh are called from vm_stop.
---
hw/virtio-serial-bus.c | 12 +
