qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"mst@redhat.com" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] pci: Return PCI_INTX_DISABLED when no bus INTx routing support
Date: Wed, 17 Oct 2012 12:54:36 -0600	[thread overview]
Message-ID: <1350500076.2112.321.camel@bling.home> (raw)
In-Reply-To: <507EFB85.5030206@siemens.com>

On Wed, 2012-10-17 at 20:40 +0200, Jan Kiszka wrote:
> On 2012-10-17 20:25, Alex Williamson wrote:
> > Rather than assert, simply return PCI_INTX_DISABLED when we don't
> > have a pci_route_irq_fn.  PIIX already returns DISABLED for an
> > invalid pin, so users already deal with this state.  Users of this
> > interface should only be acting on an ENABLED or INVERTED return
> > value (though we really have no support for INVERTED).
> > 
> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> > ---
> > 
> > A compromise to the gridlock; defuse the assert, but don't add
> > a new state to the API.  Thanks,
> 
> But how do you tell "unsupported" apart from "disabled" in VFIO? If the
> chipset truly disabled the line, you must not provide it to the guest in

The downside to not being able to distinguish is that vfio can't tell
the user anything useful about whether it should work, but needs to be
implemented in the chipset or if it's just currently disabled.  Maybe an
error_report below would fix that, but yes, we do lose granularity we
had with NOROUTE.

Functionally, there's no direct kvm interrupt injection when this
returns DISABLED, so vfio routes the interrupt to qemu where we do
qemu_set_irq, and it can get dropped if it's really disabled.
pci-assign will just not program the interrupt to kvm and intx won't
work :-\  Thanks,

Alex


> >  hw/pci.c |    6 +++++-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/hw/pci.c b/hw/pci.c
> > index 83d262a..9525220 100644
> > --- a/hw/pci.c
> > +++ b/hw/pci.c
> > @@ -1094,7 +1094,11 @@ PCIINTxRoute pci_device_route_intx_to_irq(PCIDevice *dev, int pin)
> >           pin = bus->map_irq(dev, pin);
> >           dev = bus->parent_dev;
> >      } while (dev);
> > -    assert(bus->route_intx_to_irq);
> > +
> > +    if (!bus->route_intx_to_irq) {
> > +        return (PCIINTxRoute) { PCI_INTX_DISABLED, -1 };
> > +    }
> > +
> >      return bus->route_intx_to_irq(bus->irq_opaque, pin);
> >  }
> >  
> > 
> 

  reply	other threads:[~2012-10-17 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 18:25 [Qemu-devel] [PATCH] pci: Return PCI_INTX_DISABLED when no bus INTx routing support Alex Williamson
2012-10-17 18:40 ` Jan Kiszka
2012-10-17 18:54   ` Alex Williamson [this message]
2012-10-17 19:08     ` Michael S. Tsirkin
2012-10-17 19:48   ` Michael S. Tsirkin

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=1350500076.2112.321.camel@bling.home \
    --to=alex.williamson@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).