From: "Chalios, Babis" <bchalios@amazon.es>
To: <linux-kernel@vger.kernel.org>
Cc: <tytso@mit.edu>, <Jason@zx2c4.com>, <dwmw@amazon.co.uk>,
<graf@amazon.de>, <xmarcalx@amazon.co.uk>,
<gregkh@linuxfoundation.org>,
<"mst@redhat.com ani@anisinha.ca imammedo"@redhat.com>
Subject: Re: [PATCH 0/2] virt: vmgenid: add generation counter
Date: Wed, 3 Aug 2022 17:50:23 +0200 [thread overview]
Message-ID: <ccc1112e-7ae9-3c81-0b72-41bdd7c058ec@amazon.es> (raw)
In-Reply-To: <20220803152127.48281-1-bchalios@amazon.es>
CC'ing some more people to the discussion.
On 3/8/22 17:21, bchalios@amazon.es wrote:
> From: Babis Chalios <bchalios@amazon.es>
>
> Linux recently added support for the VM Generation ID mechanism from
> Microsoft. The way this works currently is using the 128-bit blob
> provided by the vmgenid device to re-seed the RNG. While this works it
> has two main issues, (a) it is inherently racy due to the fact that it
> relies on a ACPI notification being delivered and handled and (b) the ID
> is unsuitable for exposing to user-space.
>
> This patch-set extends the vmgenid device to introduce a generation
> counter, a 32-bit counter which is different every time the unique ID
> changes. The addition to the original implementation in QEMU can be
> found here:
> https://lists.nongnu.org/archive/html/qemu-devel/2022-08/msg00524.html.
>
> The first patch re-works slightly the current vmgenid driver to add a
> function that parses an object from the vmgenid device and returns the
> physical address of the vmgenid data. The second patch uses that
> function to parse additionally the address of the generation counter
> from the vmgenid namespace. The counter is then exposed to the
> user-space through a misc-device which provides `read` and `mmap`
> interfaces.
>
> Babis Chalios (2):
> virt: vmgenid: add helper function to parse ADDR
> virt: vmgenid: add support for generation counter
>
> Documentation/virt/vmgenid.rst | 120 ++++++++++++++++++++++++++
> drivers/virt/vmgenid.c | 151 ++++++++++++++++++++++++++++-----
> 2 files changed, 251 insertions(+), 20 deletions(-)
> create mode 100644 Documentation/virt/vmgenid.rst
>
Amazon Spain Services sociedad limitada unipersonal, Calle Ramirez de Prado 5, 28045 Madrid. Registro Mercantil de Madrid . Tomo 22458 . Folio 102 . Hoja M-401234 . CIF B84570936
next prev parent reply other threads:[~2022-08-03 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 15:21 bchalios
2022-08-03 15:21 ` [PATCH 1/2] virt: vmgenid: add helper function to parse ADDR bchalios
2022-08-03 15:21 ` [PATCH 2/2] virt: vmgenid: add support for generation counter bchalios
2022-08-03 15:28 ` Greg KH
2022-08-03 15:30 ` Greg KH
2022-08-03 17:53 ` Chalios, Babis
2022-08-03 15:31 ` Greg KH
2022-08-03 17:58 ` Chalios, Babis
2022-08-14 3:26 ` kernel test robot
2022-08-03 15:50 ` Chalios, Babis [this message]
2022-08-03 15:57 ` [PATCH 0/2] virt: vmgenid: add " Chalios, Babis
2022-08-04 13:33 ` Chalios, Babis
2022-08-04 14:59 ` Jason A. Donenfeld
2022-08-04 15:46 ` bchalios
2022-08-10 9:19 ` bchalios
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=ccc1112e-7ae9-3c81-0b72-41bdd7c058ec@amazon.es \
--to=bchalios@amazon.es \
--cc="mst@redhat.com ani@anisinha.ca imammedo"@redhat.com \
--cc=Jason@zx2c4.com \
--cc=dwmw@amazon.co.uk \
--cc=graf@amazon.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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®