From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4BF38F14.1060105@domain.hid> Date: Wed, 19 May 2010 09:11:16 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <2319761F7FA0D1479BA77EC2E0A8E7BCE3D6E7@domain.hid><245373446233674495BCA5CA2FC1EB17378D01593B@RCexchangeSVR1.ruggedcom.local> <4BED2910.6020105@domain.hid> <181804936ABC2349BE503168465576460EBD6239@domain.hid> <4BF17464.5090100@domain.hid> <181804936ABC2349BE503168465576460EBD62C8@domain.hid> <4BF251EC.7040605@domain.hid> <4BF267D3.4040500@domain.hid> <4BF28401.6060503@domain.hid> <4BF28B0C.3080705@domain.hid> <4BF2AB19.5060701@domain.hid> <4BF2DF77.90806@domain.hid> <4BF2F73C.7070605@domain.hid> <4BF3045E.5080707@domain.hid> <4BF31010.2080003@domain.hid> <4BF31386.4030402@domain.hid> <4BF31C83.5070109@domain.hid> <4BF37BFD.6030709@domain.hid> In-Reply-To: <4BF37BFD.6030709@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig671CD58FF880881970BDE309" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-core] Question about getting system time List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Andreas Glatz , Wolfgang Mauerer , "xenomai@xenomai.org" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig671CD58FF880881970BDE309 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Gilles Chanteperdrix wrote: > Jan Kiszka wrote: >> Just like it seems to be the case for Steve (unless I misunderstood hi= s >> reply), it is very useful for us being able to time-stamp events in RT= >> context that need to be correlated with events stamped in non-RT >> (including non-Xenomai) parts or even on other systems: (offline) data= >> fusion, logging, tracing. I even bet that this is currently the major >> use case for synchronized clocks, only a smaller part already has the >> need to synchronize timed activities on a common clock source. But the= re >> is huge potential in the second part once we can provide a stable >> infrastructure. >=20 > I already had such issues, and I did not solve them by modifying Xenoma= i > core. >=20 >> Even a "third clock" would have to be delivered for more archs than x8= 6, >> no question. We would basically need a generic but slow syscall varian= t >> and per-arch syscall-less optimizations (where feasible). >=20 > So, you would add a syscall which would becomre useless when you have > implemented synchronized clocks properly? Yet another reason for > avoiding this solution. >=20 Could be "CLOCK_LINUX" - ie. no need for a new syscall. Jan --------------enig671CD58FF880881970BDE309 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkvzjzsACgkQitSsb3rl5xRmiwCfQIez/38MD6hFdkLkXsqHqN0s CdoAn2ttfUdiI7eU9gfjvJhspC0E+vHM =9l6Z -----END PGP SIGNATURE----- --------------enig671CD58FF880881970BDE309--