From: john stultz <johnstul@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
George Anzinger <george@mvista.com>,
Thomas Gleixner <tglx@linutronix.de>,
Frank Sorenson <frank@tuxrocks.com>,
Nishanth Aravamudan <nacc@us.ibm.com>,
Darren Hart <dvhltc@us.ibm.com>
Subject: [RFC] Generic Timeofday Subsystem Simulator (v1)
Date: Thu, 13 Oct 2005 19:08:18 -0700 [thread overview]
Message-ID: <1129255699.27168.24.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <1129255182.27168.14.camel@cog.beaverton.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
All,
At Roman's prodding, and inspired by Dave Mills' simulator, I've
scratched out a pretty simple userspace simulator for my timeofday and
NTP changes.
The project is attached. It is pretty simple right now and if you have
any suggestions for changes, please let me know.
To use it:
1. Download my timeofday patches (or just the cumulative one) and apply
them to a current git tree.
2. Untar the simulator.
3. Run ./generate.sh <path to patched kernel tree>
4. Run make
5. Run ./todsim <offset> <ppm skew>
Pretty easy. It will output a whole lot of data providing:
<simulator time> <kernel time> <hardware value> <offset> <ppm adj>
Its not terribly interesting at the moment, but hopefully folks can play
with it and make suggestions for improvements to the simulator,
timeofday code or the ntp changes.
thanks
-john
[-- Attachment #2: simulator.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 5133 bytes --]
next prev parent reply other threads:[~2005-10-14 2:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 1:59 [RFC][PATCH 0/12] Generic Timeofday Subsystem (v B7) (cumulative-i386) john stultz
2005-10-14 2:08 ` john stultz [this message]
2005-10-14 2:09 ` [RFC][PATCH 1/12] Reduced NTP rework (part 1) john stultz
2005-10-14 2:10 ` [RFC][PATCH 2/12] Reduced NTP rework (part 2) john stultz
2005-10-14 2:11 ` [RFC][PATCH 3/12] clocksource management code john stultz
2005-10-14 2:12 ` [RFC][PATCH 4/12] generic timeofday core subsystem john stultz
2005-10-14 2:14 ` [RFC][PATCH 5/12] generic timeofday i386 arch specific changes, part 1 john stultz
2005-10-14 2:15 ` [RFC][PATCH 6/12] generic timeofday i386 arch specific changes, part 2 john stultz
2005-10-14 2:16 ` [RFC][PATCH 7/12] generic timeofday i386 arch specific changes, part 3 john stultz
2005-10-14 2:19 ` [RFC][PATCH 8/12] generic timeofday i386 arch specific changes, part 4 john stultz
2005-10-14 2:20 ` [RFC][PATCH 9/12] generic timeofday i386 arch specific changes, part 5 john stultz
2005-10-14 2:21 ` [RFC][PATCH 10/12] generic timeofday i386 arch specific changes, part 6 john stultz
2005-10-14 2:22 ` [RFC][PATCH 11/12] generic timeofday i386/x86-64 specific clocksources john stultz
2005-10-14 2:25 ` [RFC][PATCH 12/12] generic timeofday x86-64 arch specific changes john stultz
2005-10-14 4:01 ` [RFC][PATCH 0/12] Generic Timeofday Subsystem (v B7) (cumulative-i386) Kyle Moffett
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=1129255699.27168.24.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=frank@tuxrocks.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.com \
--cc=tglx@linutronix.de \
--cc=ulrich.windl@rz.uni-regensburg.de \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®