public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	anthony@codemonkey.ws, Alex Graf <agraf@suse.de>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [RFC PATCH] qemu spapr-pci: added IRQ list to PCIBus
Date: Mon, 14 May 2012 11:58:30 +1000	[thread overview]
Message-ID: <20120514015830.GC30229@truffala.fritz.box> (raw)
In-Reply-To: <4FAE1171.1010806@ozlabs.ru>

On Sat, May 12, 2012 at 05:29:53PM +1000, Alexey Kardashevskiy wrote:
> There is a need for a mechanism to obtain an IRQ line number to
> initialize End-Of-Interrupt handler.
> 
> There is another proposed solution (commit
> b7790763828b732059ad24ba0e64ce327563fe1a "pci: Add callbacks
> to support retrieving and updating interrupts") which adds pci_get_irq
> callback to every PCI bus to allow an external caller to calculate
> IRQ number from IRQ line (ABDD).
> 
> However it seems to be too complicated as it affects all PCI buses
> while the only user of it is VFIO-PCI so this could be done simpler
> by an array of 4 IRQs (lines A, B, C, D) in struct PCIBus which
> every platform would initialize in its own way.

I think you need to pin down the definition of what's going on here a
bit better.  Not all platforms have a concept of global IRQ number,
and the usual qemu_irq model supports that.  So for this function who
is it that is defining the number space in which pci_get_irq() is
returning values.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2012-05-14  1:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12  7:29 [RFC PATCH] qemu spapr-pci: added IRQ list to PCIBus Alexey Kardashevskiy
2012-05-14  1:58 ` David Gibson [this message]
2012-05-14  4:21   ` Alexey Kardashevskiy
2012-05-16 20:39     ` Alex Williamson
2012-05-17  2:16       ` Alexey Kardashevskiy
2012-05-17  3:00         ` Benjamin Herrenschmidt
2012-05-17  3:38           ` Alex Williamson
2012-05-17  3:39           ` Alexey Kardashevskiy

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=20120514015830.GC30229@truffala.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=benh@kernel.crashing.org \
    --cc=kvm@vger.kernel.org \
    --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