Re: [PATCHv7 01/33] ns: Introduce Time Namespace

2019-10-17 Thread Vincenzo Frascino
On 10/17/19 10:20 AM, Thomas Gleixner wrote: [...] > The architectures which implement VDSO are: > > arm, arm64, mips, nds32, powerpc, riscv, s390, sparc, x86, um > > arm64, mips, x86 use the generic VDSO. Patches for arm are floating > around. UM is special as it just traps into the

Re: [PATCHv7 01/33] ns: Introduce Time Namespace

2019-10-17 Thread Vincenzo Frascino
Hi Andrei, On 10/17/19 12:33 AM, Andrei Vagin wrote: >>> Having CONFIG_TIME_NS "default y" makes so that the option is selected even >>> on >>> the architectures that have no support for time namespaces. >>> The direct consequence is that the fallbacks defined in this patch are never >>>

Re: [PATCHv7 01/33] ns: Introduce Time Namespace

2019-10-17 Thread Thomas Gleixner
Andrei! On Wed, 16 Oct 2019, Andrei Vagin wrote: > On Wed, Oct 16, 2019 at 12:39:11PM +0200, Thomas Gleixner wrote: > > Nah. > > > > config TIME_NS > > bool "TIME namespace" > > depends on GENERIC_VDSO_TIME_NS > > I was thinking to fix this by the same way with a small difference. > >

Re: [PATCHv7 01/33] ns: Introduce Time Namespace

2019-10-16 Thread Andrei Vagin
On Wed, Oct 16, 2019 at 12:39:11PM +0200, Thomas Gleixner wrote: > On Wed, 16 Oct 2019, Vincenzo Frascino wrote: > > < Trim 250+ lines ( 3+ pages) of pointlessly wasted electrons > > > > > --- a/init/Kconfig > > > +++ b/init/Kconfig > > > @@ -1096,6 +1096,13 @@ config UTS_NS > > > In this

Re: [PATCHv7 01/33] ns: Introduce Time Namespace

2019-10-16 Thread Dmitry Safonov
On 10/16/19 11:44 AM, Vincenzo Frascino wrote: > On 10/16/19 11:39 AM, Thomas Gleixner wrote: [..] >> config TIME_NS >> bool "TIME namespace" >> depends on GENERIC_VDSO_TIME_NS >> default y >> >> and in lib/vdso/Kconfig >> >> config GENERIC_VDSO_TIME_NS >> bool >> >> and let

Re: [PATCHv7 01/33] ns: Introduce Time Namespace

2019-10-16 Thread Vincenzo Frascino
On 10/16/19 11:39 AM, Thomas Gleixner wrote: > On Wed, 16 Oct 2019, Vincenzo Frascino wrote: > > < Trim 250+ lines ( 3+ pages) of pointlessly wasted electrons > > >>> --- a/init/Kconfig >>> +++ b/init/Kconfig >>> @@ -1096,6 +1096,13 @@ config UTS_NS >>> In this namespace tasks see

Re: [PATCHv7 01/33] ns: Introduce Time Namespace

2019-10-16 Thread Thomas Gleixner
On Wed, 16 Oct 2019, Vincenzo Frascino wrote: < Trim 250+ lines ( 3+ pages) of pointlessly wasted electrons > > > --- a/init/Kconfig > > +++ b/init/Kconfig > > @@ -1096,6 +1096,13 @@ config UTS_NS > > In this namespace tasks see different info provided with the > > uname() system

Re: [PATCHv7 01/33] ns: Introduce Time Namespace

2019-10-16 Thread Vincenzo Frascino
Hi Andrei and Dmitry, On 10/11/19 2:23 AM, Dmitry Safonov wrote: > From: Andrei Vagin > > Time Namespace isolates clock values. > > The kernel provides access to several clocks CLOCK_REALTIME, > CLOCK_MONOTONIC, CLOCK_BOOTTIME, etc. > > CLOCK_REALTIME > System-wide clock that measures

[PATCHv7 01/33] ns: Introduce Time Namespace

2019-10-10 Thread Dmitry Safonov
From: Andrei Vagin Time Namespace isolates clock values. The kernel provides access to several clocks CLOCK_REALTIME, CLOCK_MONOTONIC, CLOCK_BOOTTIME, etc. CLOCK_REALTIME System-wide clock that measures real (i.e., wall-clock) time. CLOCK_MONOTONIC Clock that cannot be set and