mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Babis Chalios <bchalios@amazon.es>,
	KVM list <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Sean Christopherson <seanjc@google.com>,
	Marc Zyngier <maz@kernel.org>, Alexander Graf <graf@amazon.de>,
	"Cali, Marco" <xmarcalx@amazon.co.uk>
Subject: Re: [ANNOUNCE] KVM Microconference at LPC 2023
Date: Wed, 7 Jun 2023 12:37:50 +0200	[thread overview]
Message-ID: <5283b17c-185b-a37f-84e2-dcd08e042ec0@redhat.com> (raw)
In-Reply-To: <150e1ad0-3d59-762b-6032-897d5630a3bf@amazon.es>

On 6/7/23 12:13, Babis Chalios wrote:
> 
> 
> On our side, we 've been working on providing ways to let VMs (kernel
>  and user space) know that they have been cloned/snapshotted/restored
> from snapshots[1].
> 
> This is tightly coupled with PRNGs both in kernel and user space and
>  there needs to be some collaboration with random.c to tie everything
> together [2][3]. It sounds like it could be a good fit for this MC
> (?).

Does the VM generation ID ACPI device from Microsoft work for you?  It 
is not tied to Hyper-V.

Paolo


  reply	other threads:[~2023-06-07 10:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  9:55 Paolo Bonzini
2023-05-26 15:24 ` Gowans, James
2023-05-26 16:39   ` Sean Christopherson
2023-05-26 17:08     ` Sean Christopherson
2023-05-26 16:09 ` Mickaël Salaün
2023-06-01 21:52   ` Mickaël Salaün
2023-06-02  0:23     ` Sean Christopherson
2023-06-07 10:13 ` Babis Chalios
2023-06-07 10:37   ` Paolo Bonzini [this message]
2023-06-07 12:20     ` Babis Chalios

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=5283b17c-185b-a37f-84e2-dcd08e042ec0@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=bchalios@amazon.es \
    --cc=graf@amazon.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=seanjc@google.com \
    --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®