From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v3.14] Report IRQ injection status to userspace. Date: Thu, 19 Feb 2009 15:48:57 +0000 Message-ID: <499D7F69.5040405@redhat.com> References: <20090204152814.GK30234@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Gleb Natapov Return-path: Received: from mx2.redhat.com ([66.187.237.31]:56738 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751265AbZBSPs3 (ORCPT ); Thu, 19 Feb 2009 10:48:29 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n1JFmTsd024219 for ; Thu, 19 Feb 2009 10:48:29 -0500 In-Reply-To: <20090204152814.GK30234@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Gleb Natapov wrote: > IRQ injection status is either -1 (if there was no CPU found > that should except the interrupt because IRQ was masked or > ioapic was misconfigured or ...) or >= 0 in that case the > number indicates to how many CPUs interrupt was injected. > If the value is 0 it means that the interrupt was coalesced > and probably should be reinjected. > Applied, thanks. I hacked kvm_set_msi() to return 1 always, please follow up with a fix to that. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.