From: David Miller <davem@davemloft.net>
To: vithampi@vmware.com
Cc: richardcochran@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Pv-drivers@vmware.com,
virtualization@lists.linux-foundation.org, x86@kernel.org,
thellstrom@vmware.com, jgross@suse.com
Subject: Re: [PATCH RESEND] ptp: add VMware virtual PTP clock driver
Date: Wed, 04 Mar 2020 14:04:10 -0800 (PST) [thread overview]
Message-ID: <20200304.140410.731261448085906331.davem@davemloft.net> (raw)
In-Reply-To: <20200228053230.GA457139@sc2-cpbu2-b0737.eng.vmware.com>
From: Vivek Thampi <vithampi@vmware.com>
Date: Fri, 28 Feb 2020 05:32:46 +0000
> Add a PTP clock driver called ptp_vmw, for guests running on VMware ESXi
> hypervisor. The driver attaches to a VMware virtual device called
> "precision clock" that provides a mechanism for querying host system time.
> Similar to existing virtual PTP clock drivers (e.g. ptp_kvm), ptp_vmw
> utilizes the kernel's PTP hardware clock API to implement a clock device
> that can be used as a reference in Chrony for synchronizing guest time with
> host.
>
> The driver is only applicable to x86 guests running in VMware virtual
> machines with precision clock virtual device present. It uses a VMware
> specific hypercall mechanism to read time from the device.
>
> Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
> Signed-off-by: Vivek Thampi <vithampi@vmware.com>
> ---
> Based on feedback, resending patch to include a broader audience.
If it's just providing a read of an accurate timesource, I think it's kinda
pointless to provide a full PTP driver for it.
next prev parent reply other threads:[~2020-03-04 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 5:32 Vivek Thampi
2020-03-04 22:04 ` David Miller [this message]
2020-03-05 4:47 ` Vivek Thampi
2020-03-06 1:25 ` David Miller
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=20200304.140410.731261448085906331.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Pv-drivers@vmware.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=thellstrom@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vithampi@vmware.com \
--cc=x86@kernel.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®