From: Paolo Bonzini <pbonzini@redhat.com>
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>,
"Radim Krčmář" <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>
Subject: Re: [PATCH] x86: convert x86_platform_ops to timespec64
Date: Mon, 16 Oct 2017 14:21:22 +0200 [thread overview]
Message-ID: <9eed0fcb-ec0b-9a1a-934f-e79a4b428e14@redhat.com> (raw)
In-Reply-To: <CAK8P3a1imdvg3TA810GNy49JhnzTka05DXhFLyxZmdk0YuugBw@mail.gmail.com>
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
next prev parent reply other threads:[~2017-10-16 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 18:37 Arnd Bergmann
2017-10-13 20:45 ` Boris Ostrovsky
2017-10-16 8:11 ` Arnd Bergmann
2017-10-16 12:08 ` Paolo Bonzini
2017-10-16 12:16 ` Arnd Bergmann
2017-10-16 12:21 ` Paolo Bonzini [this message]
2017-10-16 1:48 ` kbuild test robot
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=9eed0fcb-ec0b-9a1a-934f-e79a4b428e14@redhat.com \
--to=pbonzini@redhat.com \
--cc=arnd@arndb.de \
--cc=boris.ostrovsky@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=john.stultz@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.souza.org@gmail.com \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=y2038@lists.linaro.org \
/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
all inboxes | Powered by JetHome®