Also, those only happen when using the browser in the guest; leave it on a
single webpage, and get these long timeouts. We are using slirp.
On Tue, Oct 23, 2018 at 8:02 AM Frank Yang wrote:
> We don't yet have visibility into that, but is there a way to enumerate
> what callbacks are running? We
We don't yet have visibility into that, but is there a way to enumerate
what callbacks are running? We see that sometimes, actually qemu_poll_ns
takes much, much longer than the specified timeout to return:
qemu_mutex_unlock_iothread();
replay_mutex_unlock();
struct timeval tv;
ge
On 17/10/2018 17:44, Frank Yang wrote:
>
> we are not seeing hangs in flatview_do_translate, but are still getting
> hangs in main-loop:
>
> qemu_mutex_unlock_iothread();
> replay_mutex_unlock();
>
> ret = qemu_poll_ns((GPollFD *)gpollfds->data, gpollfds->len,
> timeout); <--
Hi all,
After quite some backports, such as
https://android.googlesource.com/platform/external/qemu/+/a8da859b1b011e509056f03cbcb73df27afe4337
we are not seeing hangs in flatview_do_translate, but are still getting
hangs in main-loop:
qemu_mutex_unlock_iothread();
replay_mutex_unlock();
