From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: assign-dev: Purpose of interrupt_work
Date: Mon, 12 Oct 2009 09:13:10 +0200
Message-ID: <20091012071310.GT16702@redhat.com>
References: <4AD2D4B6.7030203@web.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Avi Kivity <avi@redhat.com>, kvm-devel <kvm@vger.kernel.org>
To: Jan Kiszka <jan.kiszka@web.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:62402 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753905AbZJLHNi (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 12 Oct 2009 03:13:38 -0400
Content-Disposition: inline
In-Reply-To: <4AD2D4B6.7030203@web.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Mon, Oct 12, 2009 at 09:03:18AM +0200, Jan Kiszka wrote:
> 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?
> 
ioapic/pic path still has mutex. If MSIX is used (like it should) we can
drop work queue.

--
			Gleb.