Hi Huw, On 15/04/2019 13:14, Huw Davies wrote: > On Mon, Apr 15, 2019 at 11:15:56AM +0100, Vincenzo Frascino wrote: >> On 15/04/2019 10:51, Thomas Gleixner wrote: >>> On Mon, 15 Apr 2019, Huw Davies wrote: >>>> On Sun, Apr 14, 2019 at 12:53:32PM +0200, Thomas Gleixner wrote: >>>>> See >>>>> https://lkml.kernel.org/r/[email protected] >>>>> for an alternate solution to this problem, which avoids this and just >>>>> gives >>>>> CLOCK_MONOTONIC_RAW a separate storage space alltogether. >>>> >>>> I can certainly do this for the x86 vdso. Would that be useful or >>>> should I wait for Vincenzo's work on the generic vdso first? >>> >>> Depends. If Vincenzo comes along with his new version soon, then you might >>> get this for free :) >>> >>> Vincenzo, what's the state of your work? >>> >> >> I am mostly done with the development, the only thing missing is the >> integration >> of the generic update_vsyscall. After this is complete, I will need to do >> some >> testing and extract the performance numbers. >> >> Considering that I will be on Easter holiday from this Wednesday till the >> end of >> April, I think v6 will be ready around second week of May. > > Hi Vincenzo, > > Great! In which case there's not much point in me changing the x86 > vdso---it'll just end up making more work for you. > > Let me know if there's anything I can help with. >
I wanted to let you know that I just posted my updated patchset for unifying vdso. I should have tested it enough (I hope :) ), but if your help offer is still valid, and you want to give it a go, you are more than welcome. Please let me know if you find any issue. > Huw. > -- Regards, Vincenzo
