From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Huw Davies <huw@codeweavers.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux kernel <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH 2/3] x86/vdso: Allow clock specific mult and shift values
Date: Thu, 30 May 2019 15:21:46 +0100 [thread overview]
Message-ID: <d7fd1ac4-c0fc-7d6c-ff7d-38079e65a1f0@arm.com> (raw)
In-Reply-To: <20190415121431.GA22003@merlot.physics.ox.ac.uk>
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/alpine.DEB.2.21.1902231727060.1666@nanos.tec.linutronix.de
>>>>> 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
next prev parent reply other threads:[~2019-05-30 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 10:12 [PATCH 0/3] x86/vdso: Add support for CLOCK_MONOTONIC_RAW in the vDSO Huw Davies
2019-04-11 10:12 ` [PATCH 1/3] x86/vdso: Remove unused 'mask' member Huw Davies
2019-04-14 10:36 ` Thomas Gleixner
2019-04-11 10:12 ` [PATCH 2/3] x86/vdso: Allow clock specific mult and shift values Huw Davies
2019-04-14 10:53 ` Thomas Gleixner
2019-04-15 9:30 ` Huw Davies
2019-04-15 9:51 ` Thomas Gleixner
2019-04-15 10:15 ` Vincenzo Frascino
2019-04-15 12:14 ` Huw Davies
2019-05-30 14:21 ` Vincenzo Frascino [this message]
2019-04-11 10:12 ` [PATCH 3/3] x86/vdso: Add support for CLOCK_MONOTONIC_RAW in the vDSO Huw Davies
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d7fd1ac4-c0fc-7d6c-ff7d-38079e65a1f0@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=huw@codeweavers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).