From: chris@basementcode.com (Christopher Harvey)
To: kernelnewbies@lists.kernelnewbies.org
Subject: system timer interrupt targets for SMP platforms with local timer support
Date: Tue, 17 May 2011 19:56:54 -0400 [thread overview]
Message-ID: <4DD30B46.9050209@basementcode.com> (raw)
In-Reply-To: <BANLkTikPNbwNTooG8adNGoC231NkS4_8LQ@mail.gmail.com>
On 05/17/11 18:28, Mulyadi Santosa wrote:
> Hi Chris....
>
> On Wed, May 18, 2011 at 03:11, Christopher Harvey
> <chris@basementcode.com> wrote:
>> I'm having a hard time finding out by reading documentation and source
>> code if a system timer IRQ is supposed to be directed at all cores of a
>> processor or if just interrupting one core is enough.
>
> my take is if we don't use local timer interrupt, then logically
> (global timer) should interrupt all cores.
>
> I came to this understanding after recalling a fact that timer is a
> way to trigger rescheduling after a time slice of a task is expired.
> SInce we can't assume anything on which core a task is currently
> running, then it would be easier if we just send interrupt to all
> cores.
>
> Not sure if you are agree with my deduction above....
>
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.
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?
Thanks
next prev parent reply other threads:[~2011-05-17 23:56 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 [this message]
2011-05-18 20:08 ` Mulyadi Santosa
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=4DD30B46.9050209@basementcode.com \
--to=chris@basementcode.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).