From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: check_timer cleanup
Date: Mon, 9 Feb 2009 11:38:29 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.1.10.0902091129150.12457@ftp.linux-mips.org> (raw)
In-Reply-To: <20090209081542.GF24420@elte.hu>
On Mon, 9 Feb 2009, Ingo Molnar wrote:
> > Impact: remove extra unmask, and pair disable/enable
> >
> > for edge trigger io-apic routing, already unmasked via setup_IO_APIC_irq,
> > so don't unmask it again.
> >
> > also do call local_irq_disable() between timer_irq_works(), between it does call
> > local_irq_enable() inside.
> > also remove not needed apic version reading for 64bit
> >
> > Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> >
> > ---
> > arch/x86/kernel/io_apic.c | 30 ++++++++++++++++++++++--------
> > 1 file changed, 22 insertions(+), 8 deletions(-)
>
> applied to tip/x86/apic, thanks Yinghai. Maybe this even solves some of the spurious
> detection troubles we had in this code.
I'll see if I can find time to look into it in details, but it looks
dodgy to me. The thing is setup_timer_IRQ0_pin() is special -- due to
line rerouting it may not necessarily be called for an input already set
up by setup_IO_APIC_irqs(). I recall keeping this mask set until ready
for a reason when doing the cleanup last year -- I think old code actually
used to do what the change now reintroduces. What's the reason of this
change?
And timer_irq_works() used to restore the local interrupt mask within
itself -- perhaps it should be brought back rather than cluttering code
with local_irq_disable() calls throughout?
What problems are you referring to, Ingo? Perhaps they should be looked
into specifically?
Maciej
next prev parent reply other threads:[~2009-02-09 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090206220716.GA15319@elte.hu>
[not found] ` <498D55A4.7000608@kernel.org>
[not found] ` <20090207165901.GA32116@elte.hu>
2009-02-08 5:14 ` [PATCH] x86: check_timer cleanup Yinghai Lu
2009-02-09 8:15 ` Ingo Molnar
2009-02-09 11:38 ` Maciej W. Rozycki [this message]
2009-02-09 11:45 ` Ingo Molnar
2009-02-09 12:34 ` Maciej W. Rozycki
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=alpine.LFD.1.10.0902091129150.12457@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.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