From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Role of qemu_fair_mutex Date: Mon, 03 Jan 2011 10:46:29 +0100 Message-ID: <4D219AF5.2030204@web.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE970BE8BC712C68D7019AC1C" Cc: kvm , Marcelo Tosatti To: qemu-devel Return-path: Received: from fmmailgate03.web.de ([217.72.192.234]:48282 "EHLO fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751972Ab1ACJqh (ORCPT ); Mon, 3 Jan 2011 04:46:37 -0500 Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE970BE8BC712C68D7019AC1C Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi, at least in kvm mode, the qemu_fair_mutex seems to have lost its function of balancing qemu_global_mutex access between the io-thread and vcpus. It's now only taken by the latter, isn't it? This and the fact that qemu-kvm does not use this kind of lock made me wonder what its role is and if it is still relevant in practice. I'd like to unify the execution models of qemu-kvm and qemu, and this lock is the most obvious difference (there are surely more subtle ones as well...). Jan --------------enigE970BE8BC712C68D7019AC1C 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.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk0hmvsACgkQitSsb3rl5xSQ0QCgsdWd7r86yalLmQhQZbQQqKv+ qJYAn3GFi6MEjmIdtb+ZE7briYMXqpFk =OOXU -----END PGP SIGNATURE----- --------------enigE970BE8BC712C68D7019AC1C--