From: David Hildenbrand <david@redhat.com>
To: "Kalyazin, Nikita" <kalyazin@amazon.co.uk>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"shuah@kernel.org" <shuah@kernel.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"michael.day@amd.com" <michael.day@amd.com>,
"jthoughton@google.com" <jthoughton@google.com>,
"Roy, Patrick" <roypat@amazon.co.uk>,
"Thomson, Jack" <jackabt@amazon.co.uk>,
"Manwaring, Derek" <derekmn@amazon.com>,
"Cali, Marco" <xmarcalx@amazon.co.uk>
Subject: Re: [PATCH v4 1/2] KVM: guest_memfd: add generic population via write
Date: Thu, 28 Aug 2025 22:01:58 +0200 [thread overview]
Message-ID: <d58425d4-8e4f-4b70-915f-322658e9878e@redhat.com> (raw)
In-Reply-To: <20250828153049.3922-2-kalyazin@amazon.com>
On 28.08.25 17:31, Kalyazin, Nikita wrote:
> write syscall populates guest_memfd with user-supplied data in a generic
> way, ie no vendor-specific preparation is performed. This is supposed
> to be used in non-CoCo setups where guest memory is not
> hardware-encrypted.
>
> The following behaviour is implemented:
> - only page-aligned count and offset are allowed
> - if the memory is already allocated, the call will successfully
> populate it
> - if the memory is not allocated, the call will both allocate and
> populate
> - if the memory is already populated, the call will not repopulate it
>
> Signed-off-by: Nikita Kalyazin <kalyazin@amazon.com>
> ---
Just nothing that checkpatch complains about
a) Usage of "unsigned" instead of "unsigned int"
b) The From doesn't completely match the SOB: "Kalyazin, Nikita" vs
"Nikita Kalyazin"
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-08-28 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 15:30 [PATCH v4 0/2] KVM: guest_memfd: use write for population Kalyazin, Nikita
2025-08-28 15:31 ` [PATCH v4 1/2] KVM: guest_memfd: add generic population via write Kalyazin, Nikita
2025-08-28 20:01 ` David Hildenbrand [this message]
2025-09-01 14:29 ` Nikita Kalyazin
2025-09-01 15:38 ` David Hildenbrand
2025-08-30 18:56 ` kernel test robot
2025-09-01 10:09 ` David Hildenbrand
2025-09-01 14:29 ` Nikita Kalyazin
2025-08-28 15:31 ` [PATCH v4 2/2] KVM: selftests: update guest_memfd write tests Kalyazin, Nikita
2025-08-28 20:07 ` [PATCH v4 0/2] KVM: guest_memfd: use write for population David Hildenbrand
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=d58425d4-8e4f-4b70-915f-322658e9878e@redhat.com \
--to=david@redhat.com \
--cc=derekmn@amazon.com \
--cc=jackabt@amazon.co.uk \
--cc=jthoughton@google.com \
--cc=kalyazin@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=michael.day@amd.com \
--cc=pbonzini@redhat.com \
--cc=roypat@amazon.co.uk \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).