From: Stanislav Meduna <stano@meduna.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Shawn Guo <shawn.guo@linaro.org>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: scheduler clock for MXS
Date: Tue, 06 Nov 2012 09:34:39 +0100 [thread overview]
Message-ID: <5098CB9F.9030401@meduna.org> (raw)
In-Reply-To: <20121105222859.GI28327@n2100.arm.linux.org.uk>
On 05.11.2012 23:28, Russell King - ARM Linux wrote:
> It most certainly does handle the wrapping correctly - it was designed
> to from the very start.
I'm not an expert on Linux kernel and its core infrastructure,
but how is the sched_clock_timer armed for the first time
after calling setup_sched_clock?
The explicitely called update_sched_clock() does _not_ arm it.
Shawn: could you try change the
update_sched_clock();
to
sched_clock_poll(sched_clock_timer.data);
right after update_sched_clock call in setup_sched_clock?
Regards
--
Stano
WARNING: multiple messages have this Message-ID (diff)
From: stano@meduna.org (Stanislav Meduna)
To: linux-arm-kernel@lists.infradead.org
Subject: scheduler clock for MXS
Date: Tue, 06 Nov 2012 09:34:39 +0100 [thread overview]
Message-ID: <5098CB9F.9030401@meduna.org> (raw)
In-Reply-To: <20121105222859.GI28327@n2100.arm.linux.org.uk>
On 05.11.2012 23:28, Russell King - ARM Linux wrote:
> It most certainly does handle the wrapping correctly - it was designed
> to from the very start.
I'm not an expert on Linux kernel and its core infrastructure,
but how is the sched_clock_timer armed for the first time
after calling setup_sched_clock?
The explicitely called update_sched_clock() does _not_ arm it.
Shawn: could you try change the
update_sched_clock();
to
sched_clock_poll(sched_clock_timer.data);
right after update_sched_clock call in setup_sched_clock?
Regards
--
Stano
next prev parent reply other threads:[~2012-11-06 8:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 21:41 Wakeup latency measured with SCHED_TRACER depends on HZ Stanislav Meduna
2012-11-02 14:29 ` Stanislav Meduna
2012-11-05 2:57 ` Shawn Guo
2012-11-05 9:14 ` scheduler clock for MXS [Was: Re: Wakeup latency measured with SCHED_TRACER depends on HZ] Stanislav Meduna
2012-11-05 9:14 ` Stanislav Meduna
2012-11-05 13:46 ` Shawn Guo
2012-11-05 13:46 ` Shawn Guo
2012-11-05 16:09 ` Stanislav Meduna
2012-11-05 16:09 ` Stanislav Meduna
2012-11-05 22:28 ` Russell King - ARM Linux
2012-11-05 22:28 ` Russell King - ARM Linux
2012-11-06 2:40 ` Shawn Guo
2012-11-06 2:40 ` Shawn Guo
2012-11-06 10:12 ` Russell King - ARM Linux
2012-11-06 10:12 ` Russell King - ARM Linux
2012-11-06 13:49 ` Shawn Guo
2012-11-06 13:49 ` Shawn Guo
2012-11-06 20:04 ` Russell King - ARM Linux
2012-11-06 20:04 ` Russell King - ARM Linux
2012-11-06 8:34 ` Stanislav Meduna [this message]
2012-11-06 8:34 ` scheduler clock for MXS Stanislav Meduna
2012-11-06 9:45 ` Russell King - ARM Linux
2012-11-06 9:45 ` Russell King - ARM Linux
2012-11-06 13:46 ` Shawn Guo
2012-11-06 13:46 ` Shawn Guo
2012-11-06 20:20 ` Russell King - ARM Linux
2012-11-06 20:20 ` Russell King - ARM Linux
2012-11-06 22:30 ` Stanislav Meduna
2012-11-06 22:30 ` Stanislav Meduna
2012-11-06 22:46 ` Russell King - ARM Linux
2012-11-06 22:46 ` Russell King - ARM Linux
2012-11-07 7:13 ` Shawn Guo
2012-11-07 7:13 ` Shawn Guo
2012-11-08 21:27 ` Stanislav Meduna
2012-11-08 21:27 ` Stanislav Meduna
2012-11-08 22:11 ` Russell King - ARM Linux
2012-11-08 22:11 ` Russell King - ARM Linux
2012-11-08 22:45 ` [PATCH] ARM: mxs: Setup scheduler clock Stanislav Meduna
2012-11-08 22:45 ` Stanislav Meduna
2012-11-12 1:54 ` Shawn Guo
2012-11-12 1:54 ` Shawn Guo
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=5098CB9F.9030401@meduna.org \
--to=stano@meduna.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=shawn.guo@linaro.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.