From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka 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 , kvm-devel Return-path: 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 ); Tue, 28 Jul 2009 03:16:08 -0400 Sender: kvm-owner@vger.kernel.org List-ID: 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-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MVgv0-000795-Jc for qemu-devel@nongnu.org; Tue, 28 Jul 2009 03:16:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MVguw-00077g-3X for qemu-devel@nongnu.org; Tue, 28 Jul 2009 03:16:14 -0400 Received: from [199.232.76.173] (port=41029 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MVguv-00077W-Ne for qemu-devel@nongnu.org; Tue, 28 Jul 2009 03:16:09 -0400 Received: from mx20.gnu.org ([199.232.41.8]:22133) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MVguv-0005iY-Ey for qemu-devel@nongnu.org; Tue, 28 Jul 2009 03:16:09 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MVguu-0003l0-P7 for qemu-devel@nongnu.org; Tue, 28 Jul 2009 03:16:09 -0400 Message-ID: <4A6EA5B3.6090500@web.de> Date: Tue, 28 Jul 2009 09:16:03 +0200 From: Jan Kiszka MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig764A1D8982B8ABC8FECAEDA2" Sender: jan.kiszka@web.de Subject: [Qemu-devel] qemu_cond_wait polling List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel , kvm-devel 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--