From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: Tickless/dyntick kernel, highres timer and general time crapectomy
Date: Thu, 07 Jun 2007 18:49:59 +0400 [thread overview]
Message-ID: <46681B17.2080207@ru.mvista.com> (raw)
In-Reply-To: <cda58cb80706070744v21e1bbf3sa28990b4477a8844@mail.gmail.com>
Hello.
Franck Bui-Huu wrote:
> [ weird, Gmail thought you were a spamer... ]
Well, I guess I should thank my ISP which indeed hosts many spammers. :-)
> Sergei Shtylyov wrote:
>> No, it doesn't. Even on dyntick kernels, interrupts do happen several
>> times a second. Dynticks have nothing to do with disabling timer
>> interrupts...
>>
>
> That's true however if your system has 2 clock devices. One is the r4k-hpt
> and the other one soemthing else with a higher rating. If you don't stop
> r4k-hpt interrupts, how does it work ?
The unwanted events just gets ignored by higher-level code, IIRC...
Classic PowerPC CPUs have the same problem (even worse, actually) -- one can't
disable the decrementer interrupt at all.
WBR, Sergei
next prev parent reply other threads:[~2007-06-07 14:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 18:54 Tickless/dyntick kernel, highres timer and general time crapectomy Ralf Baechle
2007-06-06 19:04 ` Sergei Shtylyov
2007-06-06 19:04 ` Ralf Baechle
2007-06-06 19:04 ` Ralf Baechle
2007-06-07 7:59 ` Franck Bui-Huu
2007-06-07 8:49 ` Atsushi Nemoto
2007-06-07 11:30 ` Ralf Baechle
2007-06-07 13:11 ` Franck Bui-Huu
2007-06-07 13:43 ` Sergei Shtylyov
2007-06-07 14:44 ` Franck Bui-Huu
2007-06-07 14:49 ` Sergei Shtylyov [this message]
2007-06-07 15:48 ` Ralf Baechle
2007-06-08 8:29 ` Franck Bui-Huu
2007-06-08 9:41 ` Ralf Baechle
2007-06-08 14:22 ` Atsushi Nemoto
2007-06-07 15:02 ` Ralf Baechle
2007-06-07 15:14 ` Ralf Baechle
2007-06-08 9:07 ` Franck Bui-Huu
2007-06-08 9:57 ` Ralf Baechle
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=46681B17.2080207@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=vagabon.xyz@gmail.com \
/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.