From: Grant Likely <grant.likely@secretlab.ca>
To: Mike <qiudayu@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
benh@kernel.crashing.org
Subject: Re: [PATCH] No need to call irq_domain_legacy_revmap() for twice
Date: Wed, 05 Jun 2013 23:46:40 +0100 [thread overview]
Message-ID: <20130605224640.7F60F3E10E4@localhost> (raw)
In-Reply-To: <1366181299.2439.1.camel@localhost>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3406 bytes --]
On Wed, 17 Apr 2013 14:48:19 +0800, Mike <qiudayu@linux.vnet.ibm.com> wrote:
> 在 2012-12-11二的 08:30 +0000,Grant Likely写道:
> > On Tue, 27 Nov 2012 09:41:46 +0800, Mike <qiudayu@linux.vnet.ibm.com> wrote:
> > > 在 2012-11-26一的 20:17 +0000,Grant Likely写道:
> > > > On Mon, 24 Sep 2012 17:37:55 +0800, Mike Qiu <qiudayu@linux.vnet.ibm.com> wrote:
> > > > > Function irq_create_mapping() calls irq_find_mapping(). The later
> > > > > function has checked if the indicated IRQ domain has hw IRQ mapped to
> > > > > virtual IRQ through legacy mode or not and return the value of the
> > > > > legacy irq number by call irq_domain_legacy_revmap(). We needn't
> > > > > to call irq_domain_legacy_revmap() to do same check in
> > > > > irq_create_mapping() again.
> > > > >
> > > > > The patch removes the duplicate call.
> > > > >
> > > > > Signed-off-by: Mike Qiu <qiudayu@linux.vnet.ibm.com>
> > > > > ---
> > > > > kernel/irq/irqdomain.c | 7 +++++--
> > > > > 1 files changed, 5 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> > > > > index 49a7772..286d672 100644
> > > > > --- a/kernel/irq/irqdomain.c
> > > > > +++ b/kernel/irq/irqdomain.c
> > > > > @@ -547,9 +547,12 @@ unsigned int irq_create_mapping(struct irq_domain *domain,
> > > > > return virq;
> > > > > }
> > > > >
> > > > > - /* Get a virtual interrupt number */
> > > > > + /*
> > > > > + * For IRQ domain with type of IRQ_DOMAIN_MAP_LEGACY, we needn't
> > > > > + * create the IRQ mapping for non-existing one, so just return 0.
> > > > > + */
> > > > > if (domain->revmap_type == IRQ_DOMAIN_MAP_LEGACY)
> > > > > - return irq_domain_legacy_revmap(domain, hwirq);
> > > > > + return 0;
> > > >
> > > > But it does need to return the virq assigned to the hwirq. That is why
> > > > it has to call the revmap function.
> > > >
> > > Yes, thanks
> > >
> > > this judgment has been done in
> > > /*Check if mapping already exists*/
> > > virq = irq_find_mapping(domain, hwirq);
> > >
> > > if the virq equals none zero, the func irq_create_mapping will
> > > return the virq value directly(already exists).
> > >
> > > otherwise, that means virq equals zero, this has two meanings, one is
> > > haven't find the already exist mapping, the other one is in
> > > irq_find_mapping()
> > > case IRQ_DOMAIN_MAP_LEGACY:
> > > return irq_domain_legacy_revmap(domain, hwirq);
> > > this may return zero.
> > >
> > > So, when we check if it is a IRQ_DOMAIN_MAP_LEGACY, we just return zero
> > > is OK. because if it is none zero, it will be return after check if
> > > mapping already exists, and never come here. also we never try to assign
> > > the virq for the legacy map.
> > >
> > > I don't know if you have understand my explanation.
> >
> > Yes, your explanation makes sense and you are correct. I'm not going to
> > apply this for v3.8 (I've left it too late before the merge window), but
> > I'll look again after the merge window closes.
> >
> Hi Grant
>
> I don't know if you forget this patch ...
>
> I haven't see this patch in 3.9-rc7
>
> just for a reminder
After taking another look at it, I'm not going to apply this patch. It
isn't actively dangerous for the revmap to get called twice, and I've
got a patch pending that removes the legacy map entirely and replaces it
with a pre-populated linear map.
g.
prev parent reply other threads:[~2013-06-05 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 9:37 [PATCH] No need to call irq_domain_legacy_revmap() for twice Mike Qiu
2012-10-10 5:41 ` Mike
2012-11-26 20:17 ` Grant Likely
2012-11-27 1:41 ` Mike
2012-12-11 8:30 ` Grant Likely
2012-12-11 8:50 ` Mike
2013-04-17 6:48 ` Mike
2013-06-05 22:46 ` Grant Likely [this message]
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=20130605224640.7F60F3E10E4@localhost \
--to=grant.likely@secretlab.ca \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiudayu@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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