From: Konrad Eisele <konrad@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: sparc - generic clock event support
Date: Fri, 20 Apr 2012 08:21:51 +0000 [thread overview]
Message-ID: <4F911C9F.9070402@gaisler.com> (raw)
In-Reply-To: <20120404200704.GA16958@merkur.ravnborg.org>
> I runtime tested your patch. For single-CPU the patch works
> fine. For SMP I cannot test because Leon-SMP for 3.x doesnt
> work right now, also without your patch. The last version
> that I could verify LEON-SMP was 2.6.36, 3.0 should also work,
> however there your patches dont apply. I'll have to make
> Leon-SMP work with 3.4 first , then I can test the SMP part
> of the patch. However I'll write this on my todo list for
> after easter. As for Leon-SMP is broken right now I would
> vote for that your patches are applied now and after that to
> try to fix Leon-SMP.
> -- Konrad
With SMP working again I tested your timer patch for sparc-leon
SMP. It works!
-- Konrad
# cat /proc/cpuinfo
cpu : LEON
fpu : GRFPU
promlib : Version 0 Revision 0
prom : 0.0
type : leon
ncpus probed : 2
ncpus active : 2
Cpu0Bogo : 70.04
Cpu1Bogo : 70.86
MMU type : LEON
contexts : 256
nocache total : 5242880
nocache used : 118528
State:
CPU0 : online
CPU1 : online
# cat /proc/timer_list
Timer List Version: v0.6
HRTIMER_MAX_CLOCK_BASES: 3
now at 22403528241 nsecs
cpu: 0
clock 0:
.base: f13d34e8
.index: 0
.resolution: 10000000 nsecs
.get_time: ktime_get
active timers:
clock 1:
.base: f13d3520
.index: 1
.resolution: 10000000 nsecs
.get_time: ktime_get_real
active timers:
clock 2:
.base: f13d3558
.index: 2
.resolution: 10000000 nsecs
.get_time: ktime_get_boottime
active timers:
cpu: 1
clock 0:
.base: f13db4e8
.index: 0
.resolution: 10000000 nsecs
.get_time: ktime_get
active timers:
clock 1:
.base: f13db520
.index: 1
.resolution: 10000000 nsecs
.get_time: ktime_get_real
active timers:
clock 2:
.base: f13db558
.index: 2
.resolution: 10000000 nsecs
.get_time: ktime_get_boottime
active timers:
Tick Device: mode: 0
Per CPU device: 0
Clock Event Device: percpu_ce
max_delta_ns: 1000000068
min_delta_ns: 100000
mult: 4294967
shift: 32
mode: 2
next_event: 2147483646999999999 nsecs
set_next_event: percpu_ce_set_next_event
set_mode: percpu_ce_setup
event_handler: tick_handle_periodic
retries: 0
Tick Device: mode: 0
Per CPU device: 1
Clock Event Device: percpu_ce
max_delta_ns: 1000000068
min_delta_ns: 100000
mult: 4294967
shift: 32
mode: 2
next_event: 2147483646999999999 nsecs
set_next_event: percpu_ce_set_next_event
set_mode: percpu_ce_setup
event_handler: tick_handle_periodic
retries: 0
#
next prev parent reply other threads:[~2012-04-20 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 20:07 sparc - generic clock event support Sam Ravnborg
2012-04-05 6:55 ` Konrad Eisele
2012-04-05 7:26 ` Sam Ravnborg
2012-04-05 14:23 ` Konrad Eisele
2012-04-05 15:12 ` Sam Ravnborg
2012-04-20 8:21 ` Konrad Eisele [this message]
2012-04-20 14:46 ` Sam Ravnborg
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=4F911C9F.9070402@gaisler.com \
--to=konrad@gaisler.com \
--cc=sparclinux@vger.kernel.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.