From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH 06/14] xen: events: refactor GSI pirq bindings functions
Date: Wed, 9 Mar 2011 23:00:42 -0500 [thread overview]
Message-ID: <20110310040042.GA7682@dumpdata.com> (raw)
In-Reply-To: <1299692486-28634-6-git-send-email-ian.campbell@citrix.com>
On Wed, Mar 09, 2011 at 05:41:18PM +0000, Ian Campbell wrote:
> Following the example set by xen_allocate_pirq_msi and
> xen_bind_pirq_msi_to_irq:
>
> xen_allocate_pirq becomes xen_allocate_pirq_gsi and now only allocates
> a pirq number and does not bind it.
>
> xen_map_pirq_gsi becomes xen_bind_pirq_gsi_to_irq and binds an
> existing pirq.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> ---
> arch/x86/pci/xen.c | 40 ++++++++++++++++++++++++++++------------
> drivers/xen/events.c | 7 ++++---
> include/xen/events.h | 10 +++++++---
> 3 files changed, 39 insertions(+), 18 deletions(-)
>
> diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c
> index 8c4085a..b0fb79d 100644
> --- a/arch/x86/pci/xen.c
> +++ b/arch/x86/pci/xen.c
> @@ -50,7 +50,7 @@ static int acpi_register_gsi_xen_hvm(struct device *dev, u32 gsi,
> name = "ioapic-level";
> }
>
> - irq = xen_map_pirq_gsi(map_irq.pirq, gsi, shareable, name);
> + irq = xen_bind_pirq_gsi_to_irq(gsi, map_irq.pirq, shareable, name);
>
> printk(KERN_DEBUG "xen: --> irq=%d, pirq=%d\n", irq, map_irq.pirq);
>
> @@ -237,6 +237,7 @@ static int xen_pcifront_enable_irq(struct pci_dev *dev)
> {
> int rc;
> int share = 1;
> + int pirq;
> u8 gsi;
>
> rc = pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &gsi);
> @@ -246,13 +247,21 @@ static int xen_pcifront_enable_irq(struct pci_dev *dev)
> return rc;
> }
>
> + rc = xen_allocate_pirq_gsi(gsi);
> + if (rc < 0) {
> + dev_warn(&dev->dev, "Xen PCI: failed to allocate a PIRQ for GSI%d: %d\n",
> + gsi, rc);
> + return rc;
> + }
> + pirq = rc;
> +
> if (gsi < NR_IRQS_LEGACY)
> share = 0;
>
> - rc = xen_allocate_pirq(gsi, share, "pcifront");
> + rc = xen_bind_pirq_gsi_to_irq(gsi, pirq, share, "pcifront");
> if (rc < 0) {
> - dev_warn(&dev->dev, "Xen PCI: failed to register GSI%d: %d\n",
> - gsi, rc);
> + dev_warn(&dev->dev, "Xen PCI: failed to bind GSI%d (PIRQ%d) to IRQ: %d\n",
> + gsi, pirq, rc);
> return rc;
> }
>
> @@ -309,7 +318,7 @@ int __init pci_xen_hvm_init(void)
> #ifdef CONFIG_XEN_DOM0
> static int xen_register_pirq(u32 gsi, int triggering)
> {
> - int rc, irq;
> + int rc, pirq, irq = -1;
> struct physdev_map_pirq map_irq;
> int shareable = 0;
> char *name;
> @@ -325,17 +334,20 @@ static int xen_register_pirq(u32 gsi, int triggering)
> name = "ioapic-level";
> }
>
> - irq = xen_allocate_pirq(gsi, shareable, name);
> -
> - printk(KERN_DEBUG "xen: --> irq=%d\n", irq);
> + pirq = xen_allocate_pirq_gsi(gsi);
> + if (pirq < 0)
> + goto out;
>
> + irq = xen_bind_pirq_gsi_to_irq(gsi, pirq, shareable, name);
> if (irq < 0)
> goto out;
>
> + printk(KERN_DEBUG "xen: --> pirq=%d -> irq=%d\n", pirq, irq);
> +
> map_irq.domid = DOMID_SELF;
> map_irq.type = MAP_PIRQ_TYPE_GSI;
> map_irq.index = gsi;
> - map_irq.pirq = irq;
> + map_irq.pirq = pirq;
>
> rc = HYPERVISOR_physdev_op(PHYSDEVOP_map_pirq, &map_irq);
> if (rc) {
> @@ -422,13 +434,17 @@ static int __init pci_xen_initial_domain(void)
>
> void __init xen_setup_pirqs(void)
> {
> - int irq;
> + int pirq, irq;
>
> pci_xen_initial_domain();
>
> if (0 == nr_ioapics) {
> - for (irq = 0; irq < NR_IRQS_LEGACY; irq++)
> - xen_allocate_pirq(irq, 0, "xt-pic");
> + for (irq = 0; irq < NR_IRQS_LEGACY; irq++) {
> + pirq = xen_allocate_pirq_gsi(irq);
> + if (pirq < 0)
> + break;
Would it make sense to print a warning here?
next prev parent reply other threads:[~2011-03-10 4:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 17:40 [GIT PATCH 0/14] xen: events: cleanups + ween off nr_irqs Ian Campbell
2011-03-09 17:41 ` [PATCH 01/14] xen: events: separate two unrelated halves of if condition Ian Campbell
2011-03-09 17:41 ` [PATCH 02/14] xen: events: fix xen_map_pirq_gsi error return Ian Campbell
2011-03-09 17:41 ` [PATCH 03/14] xen: events: simplify comment Ian Campbell
2011-03-09 17:41 ` [PATCH 04/14] xen: events: remove unused public functions Ian Campbell
2011-03-09 17:41 ` [PATCH 05/14] xen: events: rename restore_cpu_pirqs -> restore_pirqs Ian Campbell
2011-03-09 17:41 ` [PATCH 06/14] xen: events: refactor GSI pirq bindings functions Ian Campbell
2011-03-10 4:00 ` Konrad Rzeszutek Wilk [this message]
2011-03-10 8:37 ` [Xen-devel] " Ian Campbell
2011-03-09 17:41 ` [PATCH 07/14] xen: events: use per-cpu variable for cpu_evtchn_mask Ian Campbell
2011-03-09 17:41 ` [PATCH 08/14] xen: events: turn irq_info constructors into initialiser functions Ian Campbell
2011-03-09 17:41 ` [PATCH 09/14] xen: events: push setup of irq<->{evtchn,ipi,virq,pirq} maps into irq_info init functions Ian Campbell
2011-03-10 4:56 ` Konrad Rzeszutek Wilk
2011-03-10 8:42 ` Ian Campbell
2011-03-09 17:41 ` [PATCH 10/14] xen: events: maintain a list of Xen interrupts Ian Campbell
2011-03-10 5:22 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-03-10 8:43 ` Ian Campbell
2011-03-09 17:41 ` [PATCH 11/14] xen: events: dynamically allocate irq info structures Ian Campbell
2011-03-10 5:27 ` Konrad Rzeszutek Wilk
2011-03-10 8:51 ` Ian Campbell
2011-03-09 17:41 ` [PATCH 12/14] xen: events: remove use of nr_irqs as upper bound on number of pirqs Ian Campbell
2011-03-10 5:33 ` Konrad Rzeszutek Wilk
2011-03-10 8:57 ` Ian Campbell
2011-03-09 17:41 ` [PATCH 13/14] xen: events: do not workaround too-small nr_irqs Ian Campbell
2011-03-10 5:40 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-03-10 9:02 ` Ian Campbell
2011-03-09 17:41 ` [PATCH 14/14] xen: events: propagate irq allocation failure instead of panicking Ian Campbell
2011-03-10 5:38 ` Konrad Rzeszutek Wilk
2011-03-10 8:58 ` Ian Campbell
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=20110310040042.GA7682@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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