From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tony Luck" Date: Sat, 08 Jul 2006 02:51:52 +0000 Subject: Re: [PATCH] ia64: change usermode HZ to 250 Message-Id: <12c511ca0607071951p4fe7e1bfm7be5ad48ede895f1@mail.gmail.com> List-Id: References: <617E1C2C70743745A92448908E030B2A27FC5F@scsmsx411.amr.corp.intel.com> <1151578928.23785.0.camel@localhost.localdomain> <44A3AFFB.2000203@sgi.com> <1151578513.3122.22.camel@laptopd505.fenrus.org> <20060708001427.GA723842@sgi.com> In-Reply-To: <20060708001427.GA723842@sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jeremy Higdon Cc: Arjan van de Ven , Jes Sorensen , Alan Cox , John Daiker , John Hawkes , Andrew Morton , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, Jack Steiner , Dan Higgins > So does i386 convert the return value of the times(2) call to user > hertz? On IA64, it returns the value in internal clock ticks, and > then when a program uses the value in param.h, it gets it wrong now, > because internal HZ is now 250. > > So is times() is broken in IA64, or is this an exception to Alan's > statement? The Linux man page for times(2) specifically says "ticks" and refers to sysconf for how to determine how long a "tick" is. So ia64 matches the man page. Dunno if that matches POSIX though. -Tony