From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752811AbdJPMVe (ORCPT <rfc822;w@1wt.eu>);
        Mon, 16 Oct 2017 08:21:34 -0400
Received: from mx1.redhat.com ([209.132.183.28]:56696 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752226AbdJPMVd (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 16 Oct 2017 08:21:33 -0400
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com D09A24E4C2
Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=pbonzini@redhat.com
Subject: Re: [PATCH] x86: convert x86_platform_ops to timespec64
To: Arnd Bergmann <arnd@arndb.de>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
        Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>,
        the arch/x86 maintainers <x86@kernel.org>,
        y2038 Mailman List <y2038@lists.linaro.org>,
        =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= <rkrcmar@redhat.com>,
        Juergen Gross <jgross@suse.com>,
        Marcos Paulo de Souza <marcos.souza.org@gmail.com>,
        Dmitry Torokhov <dmitry.torokhov@gmail.com>,
        John Stultz <john.stultz@linaro.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        kvm@vger.kernel.org, xen-devel <xen-devel@lists.xenproject.org>
References: <20171013183933.3757079-1-arnd@arndb.de>
 <ae24f18e-9a48-b6c0-9073-95121a444b53@oracle.com>
 <CAK8P3a1dUJVF9Ljg-3KX-T+EaurcVVPNRxB5L6hwOJuQTZNMSg@mail.gmail.com>
 <57be470f-0f45-cdb8-09d2-15a6dd0c3054@redhat.com>
 <CAK8P3a1imdvg3TA810GNy49JhnzTka05DXhFLyxZmdk0YuugBw@mail.gmail.com>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <9eed0fcb-ec0b-9a1a-934f-e79a4b428e14@redhat.com>
Date: Mon, 16 Oct 2017 14:21:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAK8P3a1imdvg3TA810GNy49JhnzTka05DXhFLyxZmdk0YuugBw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Mon, 16 Oct 2017 12:21:33 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 16/10/2017 14:16, Arnd Bergmann wrote:
> On Mon, Oct 16, 2017 at 2:08 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> On 16/10/2017 10:11, Arnd Bergmann wrote:
>>> Thanks!
>>>
>>> Since you've looked at it overall, do you have an opinion on the question
>>> how to fix the PV interface to deal with the pvclock_wall_clock overflow?
>>
>> It has to be done separately for each hypervisor.
>>
>> In KVM, for example, it is probably best to abandon
>> pvclock_read_wallclock altogether, and instead use the recently
>> introduced KVM_HC_CLOCK_PAIRING hypercall.  drivers/ptp/ptp_kvm.c is
>> already using it and it's y2106 safe.
> 
> Right, makes sense. I see that this interface is currently implemented
> only for 64-bit x86 in kvm_emulate_hypercall(). Could this be extended
> to x86-32 and the non-x86 architectures as well?

Yes, it could be implemented for x86-32 too.  The whole pvclock concept
however is specific to x86.

Paolo