From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] Timer interrupt cleanups [0/3]
Date: Sun, 05 Jan 2003 18:32:09 -0800 [thread overview]
Message-ID: <194400000.1041820329@titus> (raw)
Well, I tested these on the NUMA-Q and they seem to work.
Basically (as discussed previously) they rename the stuff off
the global timer to global_timer_* and the stuff off the
local timer to local_timer_*. Then I tried to clean up the
cross-calling ifdef madness. There are various corner cases,
so it's possible I screwed something up, but I think it's OK.
Original calling graph looked like this, I'll update this for
each patch to show what happens. Feel free to flame me, everyone.
--------------------
Assuming we're SMP with a local apic timer all firing away:
timer_interrupt
do_timer_interrupt
{ack the interrupt}
do_timer_interrupt_hook
do_timer
jiffies_64++;
update_times
{update CMOS clock} (In the interrupt still ??!!)
apic_timer_interrupt
smp_apic_timer_interrupt
{ack the interrupt}
smp_local_timer_interrupt
x86_do_profile
update_process_times
--------------------
On UP with local apic timer:
timer_interrupt
do_timer_interrupt
{ack the interrupt}
do_timer_interrupt_hook
do_timer
jiffies_64++;
update_process_times
update_times
{update CMOS clock} (In the interrupt still ??!!)
apic_timer_interrupt
smp_apic_timer_interrupt
{ack the interrupt}
smp_local_timer_interrupt
x86_do_profile
--------------------
On a UP 386 with stale crusty breadcrumbs, and no local timer:
timer_interrupt
do_timer_interrupt
{ack the interrupt}
do_timer_interrupt_hook
do_timer
jiffies_64++;
update_process_times
update_times
x86_do_profile()
{update CMOS clock} (In the interrupt still ??!!)
--------------------
next reply other threads:[~2003-01-06 2:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 2:32 Martin J. Bligh [this message]
2003-01-06 6:38 ` [PATCH] Timer interrupt cleanups [0/3] Martin J. Bligh
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=194400000.1041820329@titus \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.