All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Takahiro Itazuri <itazur@amazon.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, devicetree@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	mail@bchalios.io, graf@amazon.de, mzxreary@0pointer.de,
	xmarcalx@amazon.co.uk, dwmw@amazon.co.uk
Subject: Re: [PATCH v7 0/7] ptp: vmclock: Add VM generation counter and ACPI notification
Date: Tue, 03 Feb 2026 02:10:21 +0000	[thread overview]
Message-ID: <177008462163.1277679.3528738405743179040.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260130173704.12575-1-itazur@amazon.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 30 Jan 2026 17:35:59 +0000 you wrote:
> Similarly to live migration, starting a VM from some serialized state
> (aka snapshot) is an event which calls for adjusting guest clocks, hence
> a hypervisor should increase the disruption_marker before resuming the
> VM vCPUs, letting the guest know.
> 
> However, loading a snapshot, is slightly different than live migration,
> especially since we can start multiple VMs from the same serialized
> state. Apart from adjusting clocks, the guest needs to take additional
> action during such events, e.g. recreate UUIDs, reset network
> adapters/connections, reseed entropy pools, etc. These actions are not
> necessary during live migration. This calls for a differentiation
> between the two triggering events.
> 
> [...]

Here is the summary with links:
  - [v7,1/7] ptp: vmclock: add vm generation counter
    https://git.kernel.org/netdev/net-next/c/3495064b6d65
  - [v7,2/7] ptp: vmclock: support device notifications
    https://git.kernel.org/netdev/net-next/c/3b1526ddb254
  - [v7,3/7] dt-bindings: ptp: Add amazon,vmclock
    https://git.kernel.org/netdev/net-next/c/1d5a66045afa
  - [v7,4/7] ptp: ptp_vmclock: Add device tree support
    https://git.kernel.org/netdev/net-next/c/ddc867d0b5db
  - [v7,5/7] ptp: ptp_vmclock: add 'VMCLOCK' to ACPI device match
    https://git.kernel.org/netdev/net-next/c/ed4d23ed469c
  - [v7,6/7] ptp: ptp_vmclock: remove dependency on CONFIG_ACPI
    https://git.kernel.org/netdev/net-next/c/ac1e7404924c
  - [v7,7/7] ptp: ptp_vmclock: return TAI not UTC
    https://git.kernel.org/netdev/net-next/c/562f59fe3291

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-02-03  2:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 17:35 [PATCH v7 0/7] ptp: vmclock: Add VM generation counter and ACPI notification Takahiro Itazuri
2026-01-30 17:36 ` [PATCH v7 1/7] ptp: vmclock: add vm generation counter Takahiro Itazuri
2026-01-30 17:36 ` [PATCH v7 2/7] ptp: vmclock: support device notifications Takahiro Itazuri
2026-01-30 17:36 ` [PATCH v7 3/7] dt-bindings: ptp: Add amazon,vmclock Takahiro Itazuri
2026-01-30 17:36 ` [PATCH v7 4/7] ptp: ptp_vmclock: Add device tree support Takahiro Itazuri
2026-01-30 17:36 ` [PATCH v7 5/7] ptp: ptp_vmclock: add 'VMCLOCK' to ACPI device match Takahiro Itazuri
2026-01-30 17:36 ` [PATCH v7 6/7] ptp: ptp_vmclock: remove dependency on CONFIG_ACPI Takahiro Itazuri
2026-01-30 17:36 ` [PATCH v7 7/7] ptp: ptp_vmclock: return TAI not UTC Takahiro Itazuri
2026-02-03  2:10 ` patchwork-bot+netdevbpf [this message]

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=177008462163.1277679.3528738405743179040.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw@amazon.co.uk \
    --cc=edumazet@google.com \
    --cc=graf@amazon.de \
    --cc=itazur@amazon.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@bchalios.io \
    --cc=mzxreary@0pointer.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=xmarcalx@amazon.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.