From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49366957.70805@domain.hid> Date: Wed, 03 Dec 2008 12:11:19 +0100 From: Philippe Gerum MIME-Version: 1.0 References: <493306F5.2080605@domain.hid> <49330CD3.4090700@domain.hid> <4933BAE2.3000502@domain.hid> <4933F1A4.8060209@domain.hid> <4933F18F.7080103@domain.hid> <49363D9C.7010201@domain.hid> <49365B75.4020207@domain.hid> <4936638B.50306@domain.hid> In-Reply-To: <4936638B.50306@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] pthread cancelation and scheduling magics Reply-To: rpm@xenomai.org List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Wolfgang Grandegger Cc: xenomai-help Wolfgang Grandegger wrote: > Gilles Chanteperdrix wrote: >> Wolfgang Grandegger wrote: >>> Gilles Chanteperdrix wrote: >>>> For architectures with a high-resolution counter, >>>> clock_gettime(CLOCK_MONOTONIC) is a xenomai service which uses the >>>> counter and does not issue any syscall, this includes arm unless you >>>> configured xenomai with --enable-arm-arch=generic or with >>>> --disable-arm-tsc, and this probably includes powerpc. >>>> >>> clock_gettime() is wrapped to __wrap_clock_gettime(), which does a syscall: >>> >>> http://www.rts.uni-hannover.de/xenomai/lxr/source/src/skins/posix/clock.c?v=SVN-trunk#058 >>> >>> Have I missed something? >> Yes, read the code again. > > I was aware of CONFIG_XENO_HW_DIRECT_TSC but didn't look it up correctly > :-(. It is set for my ARM but not for my PowerPC system. Which explains > some differences. > We do have direct TSC readings on powerpc as well by looking at the timebase register from userland, but this only applies to rt_native_tsc(), or clock_gettime() when using CLOCK_MONOTONIC in aperiodic mode. > Wolfgang. > > > _______________________________________________ > Xenomai-help mailing list > Xenomai-help@domain.hid > https://mail.gna.org/listinfo/xenomai-help > -- Philippe.