From: Alexander Graf <graf@amazon.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Ard Biesheuvel" <ardb@kernel.org>,
"KVM list" <kvm@vger.kernel.org>,
"Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>,
linux-hyperv@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
adrian@parity.io, ben@skyportsystems.com,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Colm MacCarthaigh" <colmmacc@amazon.com>,
"Dexuan Cui" <decui@microsoft.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"Eric Biggers" <ebiggers@kernel.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Jann Horn" <jannh@google.com>,
"KY Srinivasan" <kys@microsoft.com>,
"Laszlo Ersek" <lersek@redhat.com>,
"Dominik Brodowski" <linux@dominikbrodowski.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Weiss, Radu" <raduweis@amazon.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
"Wei Liu" <wei.liu@kernel.org>
Subject: Re: [PATCH v4] virt: vmgenid: introduce driver for reinitializing RNG on VM fork
Date: Fri, 25 Feb 2022 16:57:41 +0100 [thread overview]
Message-ID: <5a196de5-d7cb-d462-2292-af05907d3544@amazon.com> (raw)
In-Reply-To: <Yhj5Dyd6+oC/R1H5@zx2c4.com>
On 25.02.22 16:43, Jason A. Donenfeld wrote:
>
> Hi Alex,
>
> On Fri, Feb 25, 2022 at 04:22:54PM +0100, Alexander Graf wrote:
>> I don't understand the rush here. This had been sitting on the ML for 1
>> year - and now suddenly talking the match through properly and getting
>> VMGenID spec compatible matching support into the ACPI core is a
>> problem? What did I miss? :)
> I don't think this is a question about speed. Ard doesn't like the spec.
> You like the feature more than you dislike the spec. Apparently that
> means there's a disagreement.
>
> As I mentioned earlier, I'd encourage you to send a patch to the ACPI
> people and let them decide. If that gets in, then I'm fine with
> modifying vmgenid to meet the spec and take advantage of the change
> you'll be making to the ACPI code. If it is rejected by the ACPI people,
> and consequently Linux isn't able to match on _CID, then I guess we'll
> have the next best thing, which is "well, it still works on QEMU."
> Hopefully you'll convince them. Feel free to CC me on that patch.
I agree with that approach and CC'ed you on the ACPI patch :). Let's
explore all options to match against _CID before we give up.
Alex
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next prev parent reply other threads:[~2022-02-25 15:58 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 13:39 [PATCH v3 0/2] VM fork detection for RNG Jason A. Donenfeld
2022-02-24 13:39 ` Jason A. Donenfeld
2022-02-24 13:39 ` [PATCH v3 1/2] random: add mechanism for VM forks to reinitialize crng Jason A. Donenfeld
2022-02-24 13:39 ` Jason A. Donenfeld
2022-02-25 11:26 ` Ard Biesheuvel
2022-02-25 11:26 ` Ard Biesheuvel
2022-02-25 11:43 ` Jason A. Donenfeld
2022-02-25 11:43 ` Jason A. Donenfeld
2022-02-25 11:44 ` Ard Biesheuvel
2022-02-25 11:44 ` Ard Biesheuvel
2022-02-24 13:39 ` [PATCH v3 2/2] virt: vmgenid: introduce driver for reinitializing RNG on VM fork Jason A. Donenfeld
2022-02-24 13:39 ` Jason A. Donenfeld
2022-02-25 10:37 ` Laszlo Ersek
2022-02-25 10:37 ` Laszlo Ersek
2022-02-25 11:24 ` Ard Biesheuvel
2022-02-25 11:24 ` Ard Biesheuvel
2022-02-25 11:51 ` Michael S. Tsirkin
2022-02-25 11:51 ` Michael S. Tsirkin
2022-02-25 12:01 ` Jason A. Donenfeld
2022-02-25 12:01 ` Jason A. Donenfeld
2022-02-25 12:00 ` Jason A. Donenfeld
2022-02-25 12:00 ` Jason A. Donenfeld
2022-02-25 12:48 ` [PATCH v4] " Jason A. Donenfeld
2022-02-25 12:48 ` Jason A. Donenfeld
2022-02-25 12:52 ` Greg KH
2022-02-25 12:52 ` Greg KH
2022-02-25 12:53 ` Greg KH
2022-02-25 12:53 ` Greg KH
2022-02-25 12:56 ` Jason A. Donenfeld
2022-02-25 12:56 ` Jason A. Donenfeld
2022-02-25 15:04 ` Ard Biesheuvel
2022-02-25 15:04 ` Ard Biesheuvel
2022-02-25 13:57 ` Alexander Graf
2022-02-25 14:12 ` Jason A. Donenfeld
2022-02-25 14:12 ` Jason A. Donenfeld
2022-02-25 14:18 ` Jason A. Donenfeld
2022-02-25 14:18 ` Jason A. Donenfeld
2022-02-25 14:18 ` Alexander Graf
2022-02-25 14:33 ` Jason A. Donenfeld
2022-02-25 14:33 ` Jason A. Donenfeld
2022-02-25 15:11 ` Alexander Graf
2022-02-25 15:16 ` Ard Biesheuvel
2022-02-25 15:16 ` Ard Biesheuvel
2022-02-25 15:22 ` Alexander Graf
2022-02-25 15:43 ` Jason A. Donenfeld
2022-02-25 15:43 ` Jason A. Donenfeld
2022-02-25 15:57 ` Alexander Graf [this message]
2022-02-25 15:34 ` Jason A. Donenfeld
2022-02-25 15:34 ` Jason A. Donenfeld
2022-02-25 15:37 ` Alexander Graf
2022-02-25 15:45 ` Jason A. Donenfeld
2022-02-25 15:45 ` Jason A. Donenfeld
2022-02-25 14:36 ` Greg KH
2022-02-25 14:36 ` Greg KH
2022-02-25 15:31 ` Alexander Graf
2022-02-25 15:36 ` Jason A. Donenfeld
2022-02-25 15:36 ` Jason A. Donenfeld
2022-02-25 14:54 ` Jason A. Donenfeld
2022-02-25 14:54 ` Jason A. Donenfeld
2022-02-25 15:15 ` Alexander Graf
2022-02-25 15:28 ` Jason A. Donenfeld
2022-02-25 15:28 ` Jason A. Donenfeld
2022-02-25 15:03 ` Ard Biesheuvel
2022-02-25 15:03 ` Ard Biesheuvel
2022-02-25 15:14 ` Alexander Graf
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=5a196de5-d7cb-d462-2292-af05907d3544@amazon.com \
--to=graf@amazon.com \
--cc=Jason@zx2c4.com \
--cc=adrian@parity.io \
--cc=ardb@kernel.org \
--cc=ben@skyportsystems.com \
--cc=berrange@redhat.com \
--cc=colmmacc@amazon.com \
--cc=decui@microsoft.com \
--cc=dwmw@amazon.co.uk \
--cc=ebiggers@kernel.org \
--cc=ehabkost@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=imammedo@redhat.com \
--cc=jannh@google.com \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=lersek@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=raduweis@amazon.com \
--cc=sthemmin@microsoft.com \
--cc=tytso@mit.edu \
--cc=wei.liu@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 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.