From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: assigned dev msi int handling
Date: Thu, 26 Feb 2009 20:59:27 -0300
Message-ID: <20090226235927.GA4270@amt.cnet>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm-devel <kvm@vger.kernel.org>
To: "Yang, Sheng" <sheng.yang@intel.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:57683 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755202AbZB0AAS (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 26 Feb 2009 19:00:18 -0500
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi Sheng,

So for guest INTX interrupts the host interrupt is reenabled on ack from
the guest, which is nice. Now for guest MSI interrupts it keeps reenabling
the interrupt as fast as the work handler can run.

Can you explain why it works this way? Why not disable interrupts 
on the host in all cases and only reenable on ack?

Thanks