From: Ingo Molnar <mingo@elte.hu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: tglx@linutronix.de,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch, -rc5-mm1] genirq: add chip->eoi(), fastack -> fasteoi
Date: Wed, 31 May 2006 23:30:02 +0200 [thread overview]
Message-ID: <20060531213002.GB3174@elte.hu> (raw)
In-Reply-To: <1149110637.29764.9.camel@localhost.localdomain>
* Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> Hrm... ok. Not sure I agree with adding one more callback but it
> doesn't matter much.
>
> Thing is, end() isn't used anymore at all now. Thus it's just
> basically renaming end() to eoi() except that end() is still there for
> whoever uses __do_IRQ() and ... handle_percpu_irq(). Doesn't make that
> much sense to me. So I suppose you should also change
> handle_percpu_irq() to use eoi() then and consider end() to be
> "legacy" (to be used only by __do_IRQ) ?
ok, that works with me. I did not want to reuse ->end() just to have a
clean migration path. ->eoi() is in fact quite descriptive as well, so
i'm not worried about the name.
> > sounds like a plan? The patch below works fine for me.
>
> The patch is _almost_ right to me :) I don't need the
>
> if (unlikely(desc->status & IRQ_DISABLED))
> desc->chip->mask(irq);
>
> At all. I suppose it won't harm, but it shouldn't be necessary for me
> and I'm not sure why it's necessary on IO_APIC neither (but then I
> don't know those very well).
hm, i dont think it's necessary either. I'll run a few experiments.
Thomas, do you remember why we have that masking there?
Ingo
next prev parent reply other threads:[~2006-05-31 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 1:52 genirq vs. fastack Benjamin Herrenschmidt
2006-05-31 8:38 ` Thomas Gleixner
2006-05-31 9:11 ` Benjamin Herrenschmidt
2006-05-31 10:19 ` [patch, -rc5-mm1] genirq: add chip->eoi(), fastack -> fasteoi Ingo Molnar
2006-05-31 21:23 ` Benjamin Herrenschmidt
2006-05-31 21:30 ` Ingo Molnar [this message]
2006-05-31 21:46 ` Benjamin Herrenschmidt
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=20060531213002.GB3174@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®