mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Babis Chalios <bchalios@amazon.es>,
	tytso@mit.edu, Jason@zx2c4.com,  linux-kernel@vger.kernel.org
Cc: graf@amazon.de, mzxreary@0pointer.de, xmarcalx@amazon.co.uk,
	 gregkh@linuxfoundation.org
Subject: Re: [PATCH 1/1] vmgenid: emit uevent with new generation ID
Date: Tue, 30 Jul 2024 12:32:15 +0100	[thread overview]
Message-ID: <a161733dd063104b371f4587ace612025b4981f9.camel@debian.org> (raw)
In-Reply-To: <20240730094831.882166-2-bchalios@amazon.es>

On Tue, 2024-07-30 at 11:48 +0200, Babis Chalios wrote:
> There are many system services that need to be notified when the VM they
> are running in is resumed from a snapshot. One example are network
> managers which need to renew DHCP leases and/or re-create MAC addresses
> for virtual interfaces. Other example are daemons that manage system
> clocks which need reset upon snapshot resume.
> 
> Send a uevent notification to user space from the VMGenID driver when
> we receive the ACPI notification about a new generation ID. This way, we
> notify user space software about the VM cloning event and give it a
> chance to adapt to the new environment.
> 
> Signed-off-by: Babis Chalios <bchalios@amazon.es>
> ---
>  drivers/virt/vmgenid.c | 2 ++
>  1 file changed, 2 insertions(+)

Speaking as a systemd maintainer, this is precisely what we need for
systemd-networkd and systemd-timesyncd, thanks for taking care of this.

Acked-by: Luca Boccassi <bluca@debian.org>

-- 
Kind regards,
Luca Boccassi

      reply	other threads:[~2024-07-30 11:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30  9:48 [PATCH 0/1] Notify system services about VM clones Babis Chalios
2024-07-30  9:48 ` [PATCH 1/1] vmgenid: emit uevent with new generation ID Babis Chalios
2024-07-30 11:32   ` Luca Boccassi [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=a161733dd063104b371f4587ace612025b4981f9.camel@debian.org \
    --to=bluca@debian.org \
    --cc=Jason@zx2c4.com \
    --cc=bchalios@amazon.es \
    --cc=graf@amazon.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mzxreary@0pointer.de \
    --cc=tytso@mit.edu \
    --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 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®