From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Manuel Lauss <manuel.lauss@fh-hagenberg.at>, linux-mips@linux-mips.org
Subject: Re: [PATCH 0/2] Alchemy: fix interrupt routing
Date: Wed, 05 Dec 2007 22:22:20 +0300 [thread overview]
Message-ID: <4756FA6C.6040807@ru.mvista.com> (raw)
In-Reply-To: <20071205191208.GA12547@linux-mips.org>
Ralf Baechle wrote:
>> It works:
>>41 total events, 5.109 events/sec
> That's the expected behaviour, good.
> One of the remaining problems on some platforms with tickless kernels is
> that not all clocksource / clockevent driver combinations are playing
> nicely with each other. You can switch the clocksource driver manually
> at runtime. First let's see what clocksource we have:
>
> # cd /sys/devices/system/clocksource/clocksource0/
> # cat available_clocksource
> MIPS pit jiffies
I only have MIPS and jiffies of course. :-)
> # cat current_clocksource
> MIPS
> MIPS is the CP0 count register. pit is the i8259 and jiffies simply counts
> interrupts like in the old days so has problems with lost timer interrupts
> and generally not such a great idea for tickless. You should be able to
> switch between all these drivers by something like:
> # echo jiffies > current_clocksource
> Time: jiffies clocksource has been installed.
> #
> Try switching between all the available clocksources a few times to see if
> that's working right also.
It died after I selected jiffies.
> Ralf
WBR, Sergei
prev parent reply other threads:[~2007-12-05 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 16:08 [PATCH 0/2] Alchemy: fix interrupt routing Sergei Shtylyov
2007-12-05 16:39 ` Manuel Lauss
2007-12-05 18:23 ` Ralf Baechle
2007-12-05 18:29 ` Sergei Shtylyov
2007-12-05 18:57 ` Sergei Shtylyov
2007-12-05 19:12 ` Ralf Baechle
2007-12-05 19:22 ` Sergei Shtylyov [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=4756FA6C.6040807@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@fh-hagenberg.at \
--cc=ralf@linux-mips.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