From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: amit.shah@redhat.com, peter.crosthwaite@xilinx.com,
qemu-devel@nongnu.org, gson@gson.org
Subject: Re: [Qemu-devel] [PATCH] qemu-char: eliminate busy waiting on can_read returning zero
Date: Fri, 05 Apr 2013 15:01:20 +0200 [thread overview]
Message-ID: <515ECB20.2020203@redhat.com> (raw)
In-Reply-To: <87ip41f88g.fsf@codemonkey.ws>
Il 05/04/2013 14:54, Anthony Liguori ha scritto:
> I guess this works with migration because we assume that after migration
> the main loop will do a complete run?
Yes, migration will terminate in an fd handler, and the next round of
the main loop will re-evaluate chr_read.
> Is this a safe assumption or does
> there need to be a qemu_notify_event() somewhere after migration to make
> sure this doesn't cause a hang?
There could be a qemu_chr_accept_input() for all character devices after
migration. I think that would be a separate patch.
Regarding the need or not for Peter's patch: the patch might be needed
this kind of busy-wait fix was required often. As far as I recall, this
is the first we ever had, and it came after an almost-complete rewrite.
It seems rare enough, that it's much better to fix the root causes when
they appear---not the symptoms.
Paolo
next prev parent reply other threads:[~2013-04-05 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 7:40 [Qemu-devel] [PATCH] qemu-char: eliminate busy waiting on can_read returning zero Paolo Bonzini
2013-04-05 12:34 ` Anthony Liguori
2013-04-05 12:54 ` Anthony Liguori
2013-04-05 13:01 ` Paolo Bonzini [this message]
2013-04-05 13:46 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=515ECB20.2020203@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=gson@gson.org \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.