From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ishizaki Kou <kou.ishizaki@toshiba.co.jp>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 5/19] powerpc: add IRQ remapping hook
Date: Thu, 14 Dec 2006 15:58:36 +1100 [thread overview]
Message-ID: <1166072316.11914.284.camel@localhost.localdomain> (raw)
In-Reply-To: <200612140227.kBE2R3jR012071@toshiba.co.jp>
On Thu, 2006-12-14 at 11:27 +0900, Ishizaki Kou wrote:
> This patch adds irq remapping hook. On interrupt mechanism on Beat,
> when an irq outlet who has an id which is formerly used is created,
> remapping the irq is required.
Today paulus asked me what that was for and I must admit that despite
your earlier explanations, I was a bit at a loss justifying it.
Can you explain us again the exact cicrumstances in which this is
necessary ? It seems to us that if an interrupt outlet<->plug linkage is
removed in the hypervisor itself, it should be also removed in linux
using irq_dispose_mapping().
What are the cases where the HV might require a linkage to be
re-established by that remap function that the kernel couldn't have done
the cleanup itself beforehand ?
Regards,
Ben.
> Signed-off-by: Kou Ishizaki <kou.ishizaki@toshiba.co.jp>
> Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> Index: linux-powerpc-git/include/asm-powerpc/irq.h
> diff -u linux-powerpc-git/include/asm-powerpc/irq.h:1.1.1.1 linux-powerpc-git/include/asm-powerpc/irq.h:1.2
> --- linux-powerpc-git/include/asm-powerpc/irq.h:1.1.1.1 Wed Dec 6 08:24:04 2006
> +++ linux-powerpc-git/include/asm-powerpc/irq.h Wed Dec 6 08:43:16 2006
> @@ -89,6 +89,9 @@
> /* Dispose of such a mapping */
> void (*unmap)(struct irq_host *h, unsigned int virq);
>
> + /* Update of such a mapping */
> + void (*remap)(struct irq_host *h, unsigned int virq, irq_hw_number_t hw);
> +
> /* Translate device-tree interrupt specifier from raw format coming
> * from the firmware to a irq_hw_number_t (interrupt line number) and
> * type (sense) that can be passed to set_irq_type(). In the absence
> Index: linux-powerpc-git/arch/powerpc/kernel/irq.c
> diff -u linux-powerpc-git/arch/powerpc/kernel/irq.c:1.1.1.1 linux-powerpc-git/arch/powerpc/kernel/irq.c:1.2
> --- linux-powerpc-git/arch/powerpc/kernel/irq.c:1.1.1.1 Wed Dec 6 08:25:43 2006
> +++ linux-powerpc-git/arch/powerpc/kernel/irq.c Wed Dec 6 08:43:14 2006
> @@ -604,6 +604,8 @@
> */
> virq = irq_find_mapping(host, hwirq);
> if (virq != IRQ_NONE) {
> + if (host->ops->remap)
> + host->ops->remap(host, virq, hwirq);
> pr_debug("irq: -> existing mapping on virq %d\n", virq);
> return virq;
> }
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2006-12-14 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 2:27 [PATCH 5/19] powerpc: add IRQ remapping hook Ishizaki Kou
2006-12-14 4:58 ` Benjamin Herrenschmidt [this message]
2006-12-15 4:59 ` Akira Iguchi
-- strict thread matches above, loose matches on Subject: below --
2007-01-12 0:58 Ishizaki Kou
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=1166072316.11914.284.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=kou.ishizaki@toshiba.co.jp \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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