From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@web.de>
Subject: qemu_cond_wait polling
Date: Tue, 28 Jul 2009 09:16:03 +0200
Message-ID: <4A6EA5B3.6090500@web.de>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig764A1D8982B8ABC8FECAEDA2"
To: qemu-devel <qemu-devel@nongnu.org>, kvm-devel <kvm@vger.kernel.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from fmmailgate01.web.de ([217.72.192.221]:42582 "EHLO
	fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753435AbZG1HQI (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 28 Jul 2009 03:16:08 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig764A1D8982B8ABC8FECAEDA2
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Hi,

why do we wait on condition variables with silly timeouts (both in
upstream as in qemu-kvm)? There used to be some qemu_aio_poll in
qemu-kvm, but it's no longer there, and upstream never had (unless I
missed something). Is this polling legacy now? Remove it?

Jan


--------------enig764A1D8982B8ABC8FECAEDA2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkpupbcACgkQniDOoMHTA+nwcQCdGK5Y4dbOX7/qqm/QvoX/eq0G
GhIAnRXBEplTbukYWNs+HMEkVSbmydwe
=VQF5
-----END PGP SIGNATURE-----

--------------enig764A1D8982B8ABC8FECAEDA2--