From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Fritsch <sf@sfritsch.de>
Subject: Re: [PATCH RFC] virtio-pci: share config interrupt between virtio devices
Date: Thu, 18 Sep 2014 21:18:37 +0200
Message-ID: <11860049.kd4R4PIiz4@k>
References: <1409550114-8186-1-git-send-email-akong@redhat.com> <20140901063730.GB20186@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: virtualization@lists.linux-foundation.org, rusty@rustcorp.com.au,
	kvm@vger.kernel.org, jasowang@redhat.com
To: "Michael S. Tsirkin" <mst@redhat.com>, Amos Kong <akong@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from eru.sfritsch.de ([188.40.99.202]:51997 "EHLO eru.sfritsch.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751253AbaIRTgt (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 18 Sep 2014 15:36:49 -0400
In-Reply-To: <20140901063730.GB20186@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Monday 01 September 2014 09:37:30, Michael S. Tsirkin wrote:
> Why do we need INT#x?
> How about setting IRQF_SHARED for the config interrupt
> while using MSI-X? You'd have to read ISR to check that the
> interrupt was intended for your device.

The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I 
don't think that you can depend on the device to set the configuration 
changed bit.

The virtio 1.0 spec seems to have fixed that.