public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: piatz@cray.com
To: Ulrich.Windl@rz.uni-regensburg.de (Ulrich Windl)
Cc: linux-kernel@vger.kernel.org
Subject: Re: having a hard time with 2.4.x
Date: Wed, 7 Feb 2001 15:20:22 -0600 (CST)	[thread overview]
Message-ID: <200102072120.PAA68959@lambic.mw.cray.com> (raw)
In-Reply-To: <3A810780.15805.1C14E0@localhost> from "Ulrich Windl" at Feb 07, 2001 08:30:07 AM

While attempting to port Linux to a new platform using a compiler other
then GCC I noticed that there appears to be a volatile missing on the
declaration of xtime in include/linux/sched.h.  The compiler I am using
considers this to be an error.  The following may help your problem.




include/linux/sched.h
*** sched.h     2001/02/05 21:48:10     1.3
--- sched.h     2001/02/07 05:19:09
***************
*** 533,539 ****
  extern unsigned long volatile jiffies;
  extern unsigned long itimer_ticks;
  extern unsigned long itimer_next;
! extern struct timeval xtime;
  extern void do_timer(struct pt_regs *);
  
  extern unsigned int * prof_buffer;
--- 533,539 ----
  extern unsigned long volatile jiffies;
  extern unsigned long itimer_ticks;
  extern unsigned long itimer_next;
! extern volatile struct timeval xtime;
  extern void do_timer(struct pt_regs *);


Ulrich Windl writes:
> 
> Hello,
> 
> I have some news on the topic of timekeeping in Linux-2.4:
> 
> As Alan Cox pointed out the ACPI changes between 2.4.0 and 2.4.1 created a 
> extremely slow console output (if not more). Configuring away ACPI support 
> solved that problem.
> 
> However there is still a problem that I cannot explain. I wrote a test program 
> for my modified kernel (I did not try the original one). I'll include the 
> program plus results (if you want to see the patch go to 
> ftp.kernel.org/pub/linux/daemons/ntp/PPS and get PPS-2.4.0-pre3.tar.bz2 (patch 
> plus signature)):
> 
> #include	<time.h>
> #include	<stdio.h>
> #define	NTP_NANO
> #include	<sys/timex.h>
> 
> int	main()
> {
> 	struct timex	tx;
> 	long		lastns = 0;
> 
> 	tx.modes = 0;
> 	while(1)
> 	{
> 		adjtimex(&tx);
> 		printf("%d %d %d\n",
> 		       tx.time.tv_sec, tx.time.tv_nsec,
> 		       tx.time.tv_nsec - lastns);
> 		lastns = tx.time.tv_nsec;
> 		fflush(stdout);
> 	}
> }


-- 
Steve Piatz                             piatz@cray.com
Cray Inc.                               651-605-9049
1340 Mendota Heights Road
Mendota Heights, MN 55120
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-02-07 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07  7:30 having a hard time with 2.4.x Ulrich Windl
2001-02-07 21:20 ` piatz [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=200102072120.PAA68959@lambic.mw.cray.com \
    --to=piatz@cray.com \
    --cc=Ulrich.Windl@rz.uni-regensburg.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox