Re: Fwd: [PATCH v4.15.7 1/1] on Intel, VDSO should handle CLOCK_MONOTONIC_RAW and export 'tsc_calibration' pointer

Hi Thomas - Thanks very much for your help & guidance in previous mail: RE: On 08/03/2018, Thomas Gleixner wrote: > > The right way to do that is to put the raw conversion values and the raw > seconds base value into the vdso data and implement the counterpart of >

Re: Fwd: [PATCH v4.15.7 1/1] on Intel, VDSO should handle CLOCK_MONOTONIC_RAW and export 'tsc_calibration' pointer

Hi Thomas - Thanks very much for your help & guidance in previous mail: RE: On 08/03/2018, Thomas Gleixner wrote: > > The right way to do that is to put the raw conversion values and the raw > seconds base value into the vdso data and implement the counterpart of > getrawmonotonic64(). And if

Re: Fwd: [PATCH v4.15.7 1/1] on Intel, VDSO should handle CLOCK_MONOTONIC_RAW and export 'tsc_calibration' pointer

On Thu, 8 Mar 2018, Jason Vas Dias wrote: > On 08/03/2018, Thomas Gleixner wrote: > I'd appreciate clarification on few points : > > > Well, you did not expose the raw conversion data in vsyscall_gtod_data. You > > are using: > > > > + tsc*= gtod->mult; > > +

Re: Fwd: [PATCH v4.15.7 1/1] on Intel, VDSO should handle CLOCK_MONOTONIC_RAW and export 'tsc_calibration' pointer

On Thu, 8 Mar 2018, Jason Vas Dias wrote: > On 08/03/2018, Thomas Gleixner wrote: > I'd appreciate clarification on few points : > > > Well, you did not expose the raw conversion data in vsyscall_gtod_data. You > > are using: > > > > + tsc*= gtod->mult; > > + tsc >>=

Re: Fwd: [PATCH v4.15.7 1/1] on Intel, VDSO should handle CLOCK_MONOTONIC_RAW and export 'tsc_calibration' pointer

On 08/03/2018, Thomas Gleixner wrote: > On Tue, 6 Mar 2018, Jason Vas Dias wrote: >> I will prepare a new patch that meets submission + coding style guidelines >> and >> does not expose pointers within the vsyscall_gtod_data region to >> user-space code - >> but I don't really

Re: Fwd: [PATCH v4.15.7 1/1] on Intel, VDSO should handle CLOCK_MONOTONIC_RAW and export 'tsc_calibration' pointer

On 08/03/2018, Thomas Gleixner wrote: > On Tue, 6 Mar 2018, Jason Vas Dias wrote: >> I will prepare a new patch that meets submission + coding style guidelines >> and >> does not expose pointers within the vsyscall_gtod_data region to >> user-space code - >> but I don't really understand why not,

Re: Fwd: [PATCH v4.15.7 1/1] on Intel, VDSO should handle CLOCK_MONOTONIC_RAW and export 'tsc_calibration' pointer

On Tue, 6 Mar 2018, Jason Vas Dias wrote: > I will prepare a new patch that meets submission + coding style guidelines and > does not expose pointers within the vsyscall_gtod_data region to > user-space code - > but I don't really understand why not, since only the gtod->mult value will > change

Re: Fwd: [PATCH v4.15.7 1/1] on Intel, VDSO should handle CLOCK_MONOTONIC_RAW and export 'tsc_calibration' pointer

On Tue, 6 Mar 2018, Jason Vas Dias wrote: > I will prepare a new patch that meets submission + coding style guidelines and > does not expose pointers within the vsyscall_gtod_data region to > user-space code - > but I don't really understand why not, since only the gtod->mult value will > change