From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Serge Noiraud <serge.noiraud@bull.net>,
linux-kernel@vger.kernel.org, ltt-dev@shafik.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: RT patch and arch/i386/kernel/time.c question
Date: Tue, 7 Mar 2006 12:45:18 -0500 [thread overview]
Message-ID: <20060307174517.GA24610@Krystal> (raw)
In-Reply-To: <Pine.LNX.4.58.0603071220100.15305@gandalf.stny.rr.com>
* Steven Rostedt (rostedt@goodmis.org) wrote:
>
> On Tue, 7 Mar 2006, Serge Noiraud wrote:
>
> > hi,
> >
> > I'm trying to port the LTTng patch over the rt20 and I got the following problem :
> > The LTTng patch try to modify the arch/i386/kernel/time.c file in which the
> > timer_interrupt function doesn't exist anymore.
> >
> > In which file / function could I try to patch the equivalent function ?
> >
>
> The -rt patch uses the lastest stuff from Thomas Gleixner, John Stultz and
> of course Ingo Molnar. The functions you are interested in, are in
> kernel/time/ directory. Take a look at clockevents.c and perhaps
> handle_tick(). I'm not sure what LTTng is doing there, but this will give
> you a direction in which way to look.
>
> -- Steve
>
LTTng is updating its logical clock there. Note that this clock is only used on
architectures missing a synchronised CPU timestamp counter (NUMA and old i586).
If you have a fairly standard architecture (i686 with TSC available), this
combination of jiffies counter and logical clock is not used.
Look for where the xtime_lock seqlock is taken in the -rt patch : that's where
the logical clock should be updated.
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
prev parent reply other threads:[~2006-03-07 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 16:42 RT patch and arch/i386/kernel/time.c question Serge Noiraud
2006-03-07 17:23 ` Steven Rostedt
2006-03-07 17:45 ` Mathieu Desnoyers [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=20060307174517.GA24610@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=serge.noiraud@bull.net \
/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