From: Marcel Apfelbaum <marcel.a@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: peter.crosthwaite@xilinx.com, stefanha@redhat.com,
sw@weilnetz.de, jasowang@redhat.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
dkoch@verizon.com, alex.williamson@redhat.com,
paul@codesourcery.com, anthony@codemonkey.ws,
pbonzini@redhat.com, afaerber@suse.de, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] hw: set irq without selecting INTx pin
Date: Mon, 30 Sep 2013 11:14:56 +0300 [thread overview]
Message-ID: <1380528896.3439.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20130929150613.GA19383@redhat.com>
On Sun, 2013-09-29 at 18:06 +0300, Michael S. Tsirkin wrote:
> On Sun, Sep 29, 2013 at 05:40:54PM +0300, Marcel Apfelbaum wrote:
> > Interrupt pin is selected and saved into PCI_INTERRUPT_PIN
> > register during device initialization. Devices should not call
> > directly qemu_set_irq and specify the INTx pin.
> >
> > Replaced the call to qemu_set_irq with a new wrapper
> > pci_set_irq which triggers the irq based on PCI_INTERRUPT_PIN.
>
> Looks good overall.
> 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?
Thanks,
Marcel
>
> This way we know no one is using it directly ...
>
> > Marcel Apfelbaum (3):
> > hw/pci: set irq without selecting INTx pin
> > hw/pci-bridge: set PCI_INTERRUPT_PIN register before shpc init
> > hw: assert/deassert interrupts using pci_set_irq wrapper
> >
> > hw/audio/ac97.c | 4 ++--
> > hw/audio/es1370.c | 2 +-
> > hw/audio/intel-hda.c | 2 +-
> > hw/char/serial-pci.c | 2 +-
> > hw/char/tpci200.c | 4 ++--
> > hw/display/qxl.c | 2 +-
> > hw/ide/cmd646.c | 2 +-
> > hw/isa/vt82c686.c | 2 +-
> > hw/misc/ivshmem.c | 2 +-
> > hw/net/e1000.c | 2 +-
> > hw/net/rtl8139.c | 2 +-
> > hw/pci-bridge/pci_bridge_dev.c | 2 +-
> > hw/pci/pci.c | 6 +++---
> > hw/pci/shpc.c | 2 +-
> > hw/scsi/lsi53c895a.c | 2 +-
> > hw/scsi/vmw_pvscsi.c | 2 +-
> > hw/virtio/virtio-pci.c | 4 ++--
> > include/hw/pci/pci.h | 7 +++++++
> > 18 files changed, 29 insertions(+), 22 deletions(-)
> >
> > --
> > 1.8.3.1
next prev parent reply other threads:[~2013-09-30 8:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 14:40 [Qemu-devel] [PATCH 0/3] hw: set irq without selecting INTx pin Marcel Apfelbaum
2013-09-29 14:40 ` [Qemu-devel] [PATCH 1/3] hw/pci: " Marcel Apfelbaum
2013-09-29 14:40 ` [Qemu-devel] [PATCH 2/3] hw/pci-bridge: set PCI_INTERRUPT_PIN register before shpc init Marcel Apfelbaum
2013-09-29 14:40 ` [Qemu-devel] [PATCH 3/3] hw: assert/deassert interrupts using pci_set_irq wrapper Marcel Apfelbaum
2013-09-29 15:06 ` [Qemu-devel] [PATCH 0/3] hw: set irq without selecting INTx pin Michael S. Tsirkin
2013-09-29 15:24 ` Marcel Apfelbaum
2013-09-29 15:31 ` Michael S. Tsirkin
2013-09-30 8:14 ` Marcel Apfelbaum [this message]
2013-09-30 8:58 ` Michael S. Tsirkin
2013-09-30 9:02 ` Paolo Bonzini
2013-09-30 9:14 ` Michael S. Tsirkin
2013-09-30 9:43 ` Marcel Apfelbaum
2013-09-30 10:10 ` Michael S. Tsirkin
2013-09-30 10:39 ` Marcel Apfelbaum
2013-09-30 10:58 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1380528896.3439.2.camel@localhost.localdomain \
--to=marcel.a@redhat.com \
--cc=afaerber@suse.de \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=dkoch@verizon.com \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=paul@codesourcery.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.