From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:47635) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T45wQ-0007VE-Sm for qemu-devel@nongnu.org; Wed, 22 Aug 2012 04:05:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T45wO-0001MI-DE for qemu-devel@nongnu.org; Wed, 22 Aug 2012 04:05:30 -0400 Received: from mout.web.de ([212.227.15.4]:55490) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T45wO-0001M9-3Y for qemu-devel@nongnu.org; Wed, 22 Aug 2012 04:05:28 -0400 Message-ID: <503492C4.6080207@web.de> Date: Wed, 22 Aug 2012 10:05:24 +0200 From: Jan Kiszka MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1E5A59EC09DAC8035072803C" Subject: Re: [Qemu-devel] ivshmem assertion failure with EventNotifier List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cam Macdonell Cc: Paolo Bonzini , Avi Kivity , "qemu-devel@nongnu.org Developers" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1E5A59EC09DAC8035072803C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2012-08-22 06:29, Cam Macdonell wrote: > Hi Paolo, >=20 > I've noticed an assertion error when sending interrupts via ivshmem. > I bisected to this patch. >=20 > commit 563027cc0c94aa4846c18f9d665a4c90f8c42ba8 > Author: Paolo Bonzini > Date: Thu Jul 5 17:16:25 2012 +0200 >=20 > ivshmem: use EventNotifier and memory API >=20 > All of ivshmem's usage of eventfd now has a corresponding API in > EventNotifier. Simplify the code by using it, and also use the > memory API consistently to set up and tear down the ioeventfds. >=20 > Signed-off-by: Paolo Bonzini > Signed-off-by: Avi Kivity >=20 > qemu-system-x86_64: /home/cam/src/git/qemu/memory.c:1244: memory_region= _del_even > tfd: Assertion `i !=3D mr->ioeventfd_nb' failed. This assertion failur= e > occurs when the eventfd is triggered. >=20 > I'll continue to dig around, but can you explain what this assertion > is catching. Is there an initialization that might be missing? Possibly a double-release of the eventfd. The assertion checks if the parameters provided on del_eventfd match an existing one. Or that matching is broken. Jan --------------enig1E5A59EC09DAC8035072803C 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.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlA0ksQACgkQitSsb3rl5xTGigCgq2JdNiLNdoFifkpmjVg+kpqL 0VQAoKdhNGFUBv34/x777YXOHMr4h1Ek =2OV+ -----END PGP SIGNATURE----- --------------enig1E5A59EC09DAC8035072803C--