From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: system timer interrupt targets for SMP platforms with local timer support
Date: Thu, 19 May 2011 03:08:22 +0700 [thread overview]
Message-ID: <BANLkTin_NOALaSg9ybqMYDaTrusoWDNtQg@mail.gmail.com> (raw)
In-Reply-To: <4DD30B46.9050209@basementcode.com>
Hi...
On Wed, May 18, 2011 at 06:56, Christopher Harvey
<chris@basementcode.com> wrote:
> I half agree. The way I see it now, WITHOUT local timers a timer only needs
> to interrupt one core, and an IPI will interrupt the other.
based on my knowledge that registered timer handler (created by kernel
function, not the one that handle PIT for example) are kept as per CPU
list, then I am fairly sure local timer just need to interrupt its
core and IPI is not really needed.
> My question is:
> Does a global timer need to send an interrupt to both cores when local
> timers are enabled or is a a global timer interrupt on one core combined
> with the local timers enough?
my take is: if local timer (i.e by using LAPIC) is enabled and active,
then global timer is practically not needed. After all, I guess they
would be just overlapping...
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-05-18 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 20:11 system timer interrupt targets for SMP platforms with local timer support Christopher Harvey
2011-05-17 22:28 ` Mulyadi Santosa
2011-05-17 23:56 ` Christopher Harvey
2011-05-18 20:08 ` Mulyadi Santosa [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=BANLkTin_NOALaSg9ybqMYDaTrusoWDNtQg@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).