From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4C2F9CBE.4060604@domain.hid> Date: Sat, 03 Jul 2010 22:25:34 +0200 From: Wolfgang Mauerer MIME-Version: 1.0 References: <1278071353-13836-1-git-send-email-wolfgang.mauerer@domain.hid> <1278071353-13836-5-git-send-email-wolfgang.mauerer@domain.hid> <4C2F25C1.3050801@domain.hid> <4C2F9028.7010406@domain.hid> <4C2F94F1.5080002@domain.hid> In-Reply-To: <4C2F94F1.5080002@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] [PATCH 4/7] nucleus: Add CLOCK_HOST_REALTIME bits to nkvdso List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: "Kiszka, Jan" , "xenomai@xenomai.org" Gilles Chanteperdrix wrote: > Wolfgang Mauerer wrote: >> Gilles Chanteperdrix wrote: >>> Wolfgang Mauerer wrote: >>>> Augment the shared vdso page with all data required to >>>> implement a clock CLOCK_HOST_REALTIME that provides time >>>> information synchronised with the NTP-corrected time >>>> in the Linux kernel. >>>> >>>> The definition of the hostrt data is placed in a separate >>>> head file so that we can use it irregardless of pervasive >>>> rt support is compiled in or not. >>> Ok. Would not it be more simple to define the nkvdso even without >>> pervasive support? >> Thought about that, but having a shared kernel/userland object >> without pervasive RT support seemed a bit unnatural to me. > > The idea would be to have a static nkvdso in the non-pervasive case, we > do not need the mapping stuff. But at least, if we do this once and for > all for nkvdso, we will not have to repeat the code which handles the > non-pervasive case for all the data in nkvdso which need to exist in > that case. okay, let's do it like this. Might also save a couple of ifdefs. Regards, Wolfgang