Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp830746ybi; Thu, 30 May 2019 07:25:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqySVrFBgcdAC3tWNUYMsdllqHUcmfzukmFFo0oxZZ8snyfOS0yyjQ2adOuwQljC4o7NCD/k X-Received: by 2002:a17:902:b615:: with SMTP id b21mr4049761pls.12.1559226317738; Thu, 30 May 2019 07:25:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559226317; cv=none; d=google.com; s=arc-20160816; b=s2zDOLfSkSJnkYHP6QlTeoyLcpRC8nOCy5dRt8+o98V52jzI27eZ3gefx3vfhoUhxl Ej0AjjtHnsbOkMOvTpyZV3Ys18smV/CVSo8/jRZrkuUMY0PgQ28pxUT/xRIiUpzn1IyB RJAotk09NdTB6qD+V11TECx/VFlM8pBnv0Q1+V4sqBGUS1V0xWgRxT0ffOpSgWQurqgD WDB55nuEJWCVHcsaXQvIlpdMeZnX/ykI/suDJ5+Bkr9PTvRB4FLC7qMkjf/zvBm8ILkh FTw/sYBgaVxLg0x87hKBZ0oGMxDPR6TlKN15BLgvpWL3lD0BXDjaoixPNkKShU740bVv povg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=uNBKOUESA/gziL1CNYa38U/Z80lcDrpcWfw91jdKsn8=; b=rnv2MT7WBl092jWDvXlV89MWS8hUL8e5l+D+s1dt29p+Li6Jd7X4yOYJQAbup+kMuh pG6mQM8gKrL+DVgcDqjsVLL791KY9Zmle8F1Exakak+zap0XL2DIriX+u3xoANLyP7oR Kp5yyYq6LuaRkOrBq+RTa87RCcCsodBplMJNp/4JaosrgdWICMNfsvkql8Y4EMsfT3Ve fvWPOLnCGrLP67Gawp3q/XS7X9x49bTpmWd479GSogzWxtHqELoOPZNAumnWfRBZBIWF cT5O3xbHQOlgtl1lDSH9V/kEOPztXSj94+aRe9NFTerhlseQqSG5IAqdszyGEUzdHbBe Ewug== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 92si3127894plf.299.2019.05.30.07.25.01; Thu, 30 May 2019 07:25:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727187AbfE3OVt (ORCPT + 99 others); Thu, 30 May 2019 10:21:49 -0400 Received: from foss.arm.com ([217.140.101.70]:37432 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726045AbfE3OVt (ORCPT ); Thu, 30 May 2019 10:21:49 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 9B323A78; Thu, 30 May 2019 07:21:48 -0700 (PDT) Received: from [10.1.196.72] (e119884-lin.cambridge.arm.com [10.1.196.72]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C9C853F59C; Thu, 30 May 2019 07:21:47 -0700 (PDT) Subject: Re: [PATCH 2/3] x86/vdso: Allow clock specific mult and shift values To: Huw Davies Cc: Thomas Gleixner , linux kernel , Andy Lutomirski References: <20190411101205.10006-1-huw@codeweavers.com> <20190411101205.10006-3-huw@codeweavers.com> <20190415093042.GA21726@merlot.physics.ox.ac.uk> <82a61daf-f6f9-8be0-2157-e9f9d7ba1cdf@arm.com> <20190415121431.GA22003@merlot.physics.ox.ac.uk> From: Vincenzo Frascino Message-ID: Date: Thu, 30 May 2019 15:21:46 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190415121431.GA22003@merlot.physics.ox.ac.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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