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: [PATCH 09/14] xen: events: push setup of irq<->{evtchn,ipi,virq,pirq} maps into irq_info init functions
Date: Wed, 9 Mar 2011 23:56:47 -0500 [thread overview]
Message-ID: <20110310045647.GA10574@dumpdata.com> (raw)
In-Reply-To: <1299692486-28634-9-git-send-email-ian.campbell@citrix.com>
On Wed, Mar 09, 2011 at 05:41:21PM +0000, Ian Campbell wrote:
> Encapsulate setup of XXX_to_irq array in the relevant
> xen_irq_info_*_init function.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> ---
> drivers/xen/events.c | 42 +++++++++++++++++++++---------------------
> 1 files changed, 21 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/xen/events.c b/drivers/xen/events.c
> index 72725fa..cf372d4 100644
> --- a/drivers/xen/events.c
> +++ b/drivers/xen/events.c
> @@ -126,6 +126,7 @@ static struct irq_info *info_for_irq(unsigned irq)
>
> /* Constructors for packed IRQ information. */
> static void xen_irq_info_common_init(struct irq_info *info,
> + unsigned irq,
> enum xen_irq_type type,
> unsigned short evtchn,
> unsigned short cpu)
> @@ -136,6 +137,8 @@ static void xen_irq_info_common_init(struct irq_info *info,
> info->type = type;
> info->evtchn = evtchn;
> info->cpu = cpu;
> +
> + evtchn_to_irq[evtchn] = irq;
Is there any case where this would lead to an over-write? Should we
have an
WARN_ON(evtchn_to_irq[evtchn] != -1)
just to check?
> }
>
> static void xen_irq_info_evtchn_init(unsigned irq,
> @@ -143,29 +146,35 @@ static void xen_irq_info_evtchn_init(unsigned irq,
> {
> struct irq_info *info = info_for_irq(irq);
>
> - xen_irq_info_common_init(info, IRQT_EVTCHN, evtchn, 0);
> + xen_irq_info_common_init(info, irq, IRQT_EVTCHN, evtchn, 0);
> }
>
> -static void xen_irq_info_ipi_init(unsigned irq,
> +static void xen_irq_info_ipi_init(unsigned cpu,
> + unsigned irq,
> unsigned short evtchn,
> enum ipi_vector ipi)
> {
> struct irq_info *info = info_for_irq(irq);
>
> - xen_irq_info_common_init(info, IRQT_IPI, evtchn, 0);
> + xen_irq_info_common_init(info, irq, IRQT_IPI, evtchn, 0);
>
> info->u.ipi = ipi;
> +
> + per_cpu(ipi_to_irq, cpu)[ipi] = irq;
Ditto. Should we do a check first to see if we are overwritting anything
but the default value of -1?
> }
>
> -static void xen_irq_info_virq_init(unsigned irq,
> +static void xen_irq_info_virq_init(unsigned cpu,
> + unsigned irq,
> unsigned short evtchn,
> unsigned short virq)
> {
> struct irq_info *info = info_for_irq(irq);
>
> - xen_irq_info_common_init(info, IRQT_VIRQ, evtchn, 0);
> + xen_irq_info_common_init(info, irq, IRQT_VIRQ, evtchn, 0);
>
> info->u.virq = virq;
> +
> + per_cpu(virq_to_irq, cpu)[virq] = irq;
> }
>
> static void xen_irq_info_pirq_init(unsigned irq,
> @@ -177,12 +186,14 @@ static void xen_irq_info_pirq_init(unsigned irq,
> {
> struct irq_info *info = info_for_irq(irq);
>
> - xen_irq_info_common_init(info, IRQT_PIRQ, evtchn, 0);
> + xen_irq_info_common_init(info, irq, IRQT_PIRQ, evtchn, 0);
>
> info->u.pirq.pirq = pirq;
> info->u.pirq.gsi = gsi;
> info->u.pirq.vector = vector;
> info->u.pirq.flags = flags;
> +
> + pirq_to_irq[pirq] = irq;
> }
>
> /*
> @@ -644,7 +655,6 @@ int xen_bind_pirq_gsi_to_irq(unsigned gsi,
>
> xen_irq_info_pirq_init(irq, 0, pirq, gsi, irq_op.vector,
> shareable ? PIRQ_SHAREABLE : 0);
> - pirq_to_irq[pirq] = irq;
>
> out:
> spin_unlock(&irq_mapping_update_lock);
> @@ -682,7 +692,6 @@ int xen_bind_pirq_msi_to_irq(struct pci_dev *dev, struct msi_desc *msidesc,
> handle_level_irq, name);
>
> xen_irq_info_pirq_init(irq, 0, pirq, 0, vector, 0);
> - pirq_to_irq[pirq] = irq;
> ret = set_irq_msi(irq, msidesc);
> if (ret < 0)
> goto error_irq;
> @@ -746,7 +755,6 @@ int bind_evtchn_to_irq(unsigned int evtchn)
> set_irq_chip_and_handler_name(irq, &xen_dynamic_chip,
> handle_fasteoi_irq, "event");
>
> - evtchn_to_irq[evtchn] = irq;
> xen_irq_info_evtchn_init(irq, evtchn);
> }
>
> @@ -779,9 +787,7 @@ static int bind_ipi_to_irq(unsigned int ipi, unsigned int cpu)
> BUG();
> evtchn = bind_ipi.port;
>
> - evtchn_to_irq[evtchn] = irq;
> - xen_irq_info_ipi_init(irq, evtchn, ipi);
> - per_cpu(ipi_to_irq, cpu)[ipi] = irq;
> + xen_irq_info_ipi_init(cpu, irq, evtchn, ipi);
>
> bind_evtchn_to_cpu(evtchn, cpu);
> }
> @@ -814,10 +820,7 @@ int bind_virq_to_irq(unsigned int virq, unsigned int cpu)
> BUG();
> evtchn = bind_virq.port;
>
> - evtchn_to_irq[evtchn] = irq;
> - xen_irq_info_virq_init(irq, evtchn, virq);
> -
> - per_cpu(virq_to_irq, cpu)[virq] = irq;
> + xen_irq_info_virq_init(cpu, irq, evtchn, virq);
>
> bind_evtchn_to_cpu(evtchn, cpu);
> }
> @@ -1120,7 +1123,6 @@ void rebind_evtchn_irq(int evtchn, int irq)
> so there should be a proper type */
> BUG_ON(info->type == IRQT_UNBOUND);
>
> - evtchn_to_irq[evtchn] = irq;
> xen_irq_info_evtchn_init(irq, evtchn);
>
> spin_unlock(&irq_mapping_update_lock);
> @@ -1288,8 +1290,7 @@ static void restore_cpu_virqs(unsigned int cpu)
> evtchn = bind_virq.port;
>
> /* Record the new mapping. */
> - evtchn_to_irq[evtchn] = irq;
> - xen_irq_info_virq_init(irq, evtchn, virq);
> + xen_irq_info_virq_init(cpu, irq, evtchn, virq);
> bind_evtchn_to_cpu(evtchn, cpu);
> }
> }
> @@ -1313,8 +1314,7 @@ static void restore_cpu_ipis(unsigned int cpu)
> evtchn = bind_ipi.port;
>
> /* Record the new mapping. */
> - evtchn_to_irq[evtchn] = irq;
> - xen_irq_info_ipi_init(irq, evtchn, ipi);
> + xen_irq_info_ipi_init(cpu, irq, evtchn, ipi);
> bind_evtchn_to_cpu(evtchn, cpu);
> }
> }
> --
> 1.5.6.5
next prev parent reply other threads:[~2011-03-10 4:57 UTC|newest]
Thread overview: 30+ 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 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-03-10 8:37 ` 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-03-10 16:07 [GIT PATCH v2 0/14] xen: events: cleanups + ween off nr_irqs Ian Campbell
2011-03-10 16:08 ` [PATCH 09/14] xen: events: push setup of irq<->{evtchn,ipi,virq,pirq} maps into irq_info init functions 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=20110310045647.GA10574@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