From: patchwork-bot+netdevbpf@kernel.org
To: David Woodhouse <dwmw2@infradead.org>
Cc: richardcochran@gmail.com, peter.hilber@opensynergy.com,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, linux-rtc@vger.kernel.org,
ridouxj@amazon.com, virtio-dev@lists.linux.dev, rluu@amazon.com,
chashper@amazon.com, abuehaze@amazon.com, pabeni@redhat.com,
christopher.s.hall@intel.com, jasowang@redhat.com,
jstultz@google.com, mst@redhat.com, netdev@vger.kernel.org,
sboyd@kernel.org, tglx@linutronix.de, xuanzhuo@linux.alibaba.com,
maz@kernel.org, mark.rutland@arm.com, daniel.lezcano@linaro.org,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
qemu-devel@nongnu.org, horms@kernel.org
Subject: Re: [PATCH net-next v7] ptp: Add support for the AMZNC10C 'vmclock' device
Date: Wed, 09 Oct 2024 11:20:40 +0000 [thread overview]
Message-ID: <172847284000.1228916.8770974683503977940.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <78969a39b51ec00e85551b752767be65f6794b46.camel@infradead.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Sun, 06 Oct 2024 08:17:58 +0100 you wrote:
> From: David Woodhouse <dwmw@amazon.co.uk>
>
> The vmclock device addresses the problem of live migration with
> precision clocks. The tolerances of a hardware counter (e.g. TSC) are
> typically around ±50PPM. A guest will use NTP/PTP/PPS to discipline that
> counter against an external source of 'real' time, and track the precise
> frequency of the counter as it changes with environmental conditions.
>
> [...]
Here is the summary with links:
- [net-next,v7] ptp: Add support for the AMZNC10C 'vmclock' device
https://git.kernel.org/netdev/net-next/c/205032724226
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-10-09 11:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 7:17 [PATCH net-next v7] ptp: Add support for the AMZNC10C 'vmclock' device David Woodhouse
2024-10-07 16:09 ` Richard Cochran
2024-10-09 11:20 ` patchwork-bot+netdevbpf [this message]
2024-10-10 0:32 ` Jakub Kicinski
2024-10-14 7:25 ` David Woodhouse
2024-10-14 20:12 ` Jakub Kicinski
2024-10-19 17:49 ` David Woodhouse
2024-10-28 16:12 ` Jakub Kicinski
2024-10-28 16:17 ` David Woodhouse
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=172847284000.1228916.8770974683503977940.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.zummo@towertech.it \
--cc=abuehaze@amazon.com \
--cc=alexandre.belloni@bootlin.com \
--cc=chashper@amazon.com \
--cc=christopher.s.hall@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=dwmw2@infradead.org \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=jstultz@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peter.hilber@opensynergy.com \
--cc=qemu-devel@nongnu.org \
--cc=richardcochran@gmail.com \
--cc=ridouxj@amazon.com \
--cc=rluu@amazon.com \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=virtio-dev@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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).