From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@web.de>
Subject: assign-dev: Purpose of interrupt_work
Date: Mon, 12 Oct 2009 09:03:18 +0200
Message-ID: <4AD2D4B6.7030203@web.de>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig157D1AA826CE2B5F4FE83DEF"
Cc: kvm-devel <kvm@vger.kernel.org>
To: Gleb Natapov <gleb@redhat.com>, Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from fmmailgate03.web.de ([217.72.192.234]:59906 "EHLO
	fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753110AbZJLHKR (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 12 Oct 2009 03:10:17 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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

Hi,

I was starring at the IRQ delivery path of assigned devices for a while,
wondering why we have a work queue there. Now, after looking at some
prehistoric versions, I think the reason is that there once was a mutex
involved while we now use RCU. Am I right that we could actually drop
this indirection today?

Jan


--------------enig157D1AA826CE2B5F4FE83DEF
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

iEYEARECAAYFAkrS1LoACgkQitSsb3rl5xT2OQCglDg2PcywXhys0Mrfeqe+WjKU
dekAn027foMGnFhRt97CC05OZ/lUD68T
=9s7o
-----END PGP SIGNATURE-----

--------------enig157D1AA826CE2B5F4FE83DEF--