From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48905) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VQasZ-0005rt-1e for qemu-devel@nongnu.org; Mon, 30 Sep 2013 06:39:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VQasT-0006OW-2r for qemu-devel@nongnu.org; Mon, 30 Sep 2013 06:39:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:16925) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VQasS-0006OS-Px for qemu-devel@nongnu.org; Mon, 30 Sep 2013 06:38:56 -0400 Message-ID: <1380537549.3439.15.camel@localhost.localdomain> From: Marcel Apfelbaum Date: Mon, 30 Sep 2013 13:39:09 +0300 In-Reply-To: <20130930101035.GB20445@redhat.com> References: <1380465657-22600-1-git-send-email-marcel.a@redhat.com> <20130929150613.GA19383@redhat.com> <1380528896.3439.2.camel@localhost.localdomain> <20130930085815.GA20291@redhat.com> <52493E0E.1060308@redhat.com> <20130930091457.GD20291@redhat.com> <1380534200.3439.8.camel@localhost.localdomain> <20130930101035.GB20445@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/3] hw: set irq without selecting INTx pin List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: peter.crosthwaite@xilinx.com, stefanha@redhat.com, sw@weilnetz.de, jasowang@redhat.com, "qemu-devel@nongnu.org" , dkoch@verizon.com, alex.williamson@redhat.com, kraxel@redhat.com, anthony@codemonkey.ws, Paolo Bonzini , afaerber@suse.de On Mon, 2013-09-30 at 13:10 +0300, Michael S. Tsirkin wrote: > On Mon, Sep 30, 2013 at 12:43:20PM +0300, Marcel Apfelbaum wrote: > > On Mon, 2013-09-30 at 12:14 +0300, Michael S. Tsirkin wrote: > > > On Mon, Sep 30, 2013 at 11:02:06AM +0200, Paolo Bonzini wrote: > > > > Il 30/09/2013 10:58, Michael S. Tsirkin ha scritto: > > > > >>> > > As a next step, can we make pci_set_irq non-inline and make > > > > >>> > > it call pci_irq_handler directly, and get rid of the irq field? > > > > >> > What irq field? > > > > > /* IRQ objects for the INTA-INTD pins. */ > > > > > qemu_irq *irq; > > > > > > > > > > > > > That's still used by devices that use common code for PCI and sysbus > > > > versions (e.g. USB OHCI and EHCI). > > > > > > > > Paolo > > > > > > Well this work wouldn't be complete without > > > addressing them anyway. > > > > > > These devices would have to create their own > > > irq in pci-specific code, along the lines of: > > > > This irq field is used also in places where pci_set_irq(PCIDevice dev, level) > > can't infer the INTx: > > - PCIExpress: qemu_set_irq(dev->irq[dev->exp.hpev_intx],dev->exp.hpev_notified); > > Well the spec says, explicitly: > 6.7.3.4. > Software Notification of Hot-Plug Events > ... > Note that all other interrupt sources within the same Function will > assert the same virtual INTx wire > when requesting service. > > I read this to mean that this is a bug, > and it should simply use pci_set_irq like all other > devices. Thanks! That means that hpev_intx is not necessary at all. By the way, aer_intx used by Advanced Error Reporting is also unnecessary. (6.2.4.1.2 has the same note) I will remove the above fields from PCIExpressDevice. Marcel > > - vmxnet3 device: qemu_set_irq(d->irq[int_idx], 1); > > > > What approach should be used here? > > > > Thanks, > > Marcel > > > - s->irq = dev->irq[3]; > > > + s->irq = qemu_allocate_irqs(pci_set_irq, dev, 1); > > > > > > > > > If there's more than one device like this, we should add > > > > > > /* Return an irq that calls pci_set_irq internally */ > > > qemu_irq *pci_allocate_irq(PCIDevice *); > > > > > > >