Re: [PATCH v11 09/18] KVM: guest_memfd: Track shared memory support in memslot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Fuad Tabba <tabba@xxxxxxxxxx>, kvm@xxxxxxxxxxxxxxx, linux-arm-msm@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, kvmarm@xxxxxxxxxxxxxxx
Subject: Re: [PATCH v11 09/18] KVM: guest_memfd: Track shared memory support in memslot
From: David Hildenbrand <david@xxxxxxxxxx>
Date: Fri, 6 Jun 2025 11:13:20 +0200
Cc: pbonzini@xxxxxxxxxx, chenhuacai@xxxxxxxxxx, mpe@xxxxxxxxxxxxxx, anup@xxxxxxxxxxxxxx, paul.walmsley@xxxxxxxxxx, palmer@xxxxxxxxxxx, aou@xxxxxxxxxxxxxxxxx, seanjc@xxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, brauner@xxxxxxxxxx, willy@xxxxxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, xiaoyao.li@xxxxxxxxx, yilun.xu@xxxxxxxxx, chao.p.peng@xxxxxxxxxxxxxxx, jarkko@xxxxxxxxxx, amoorthy@xxxxxxxxxx, dmatlack@xxxxxxxxxx, isaku.yamahata@xxxxxxxxx, mic@xxxxxxxxxxx, vbabka@xxxxxxx, vannapurve@xxxxxxxxxx, ackerleytng@xxxxxxxxxx, mail@xxxxxxxxxxxxxxxxxxxxx, michael.roth@xxxxxxx, wei.w.wang@xxxxxxxxx, liam.merwick@xxxxxxxxxx, isaku.yamahata@xxxxxxxxx, kirill.shutemov@xxxxxxxxxxxxxxx, suzuki.poulose@xxxxxxx, steven.price@xxxxxxx, quic_eberman@xxxxxxxxxxx, quic_mnalajal@xxxxxxxxxxx, quic_tsoni@xxxxxxxxxxx, quic_svaddagi@xxxxxxxxxxx, quic_cvanscha@xxxxxxxxxxx, quic_pderrin@xxxxxxxxxxx, quic_pheragu@xxxxxxxxxxx, catalin.marinas@xxxxxxx, james.morse@xxxxxxx, yuzenghui@xxxxxxxxxx, oliver.upton@xxxxxxxxx, maz@xxxxxxxxxx, will@xxxxxxxxxx, qperret@xxxxxxxxxx, keirf@xxxxxxxxxx, roypat@xxxxxxxxxxxx, shuah@xxxxxxxxxx, hch@xxxxxxxxxxxxx, jgg@xxxxxxxxxx, rientjes@xxxxxxxxxx, jhubbard@xxxxxxxxxx, fvdl@xxxxxxxxxx, hughd@xxxxxxxxxx, jthoughton@xxxxxxxxxx, peterx@xxxxxxxxxx, pankaj.gupta@xxxxxxx, ira.weiny@xxxxxxxxx
In-reply-to: <20250605153800.557144-10-tabba@google.com>
Organization: Red Hat
References: <20250605153800.557144-1-tabba@google.com> <20250605153800.557144-10-tabba@google.com>
User-agent: Mozilla Thunderbird

On 05.06.25 17:37, Fuad Tabba wrote:

Add a new internal flag in the top half of memslot->flags to track when
a guest_memfd-backed slot supports shared memory, which is reserved for
internal use in KVM.

This avoids repeatedly checking the underlying guest_memfd file for
shared memory support, which requires taking a reference on the file.

Suggested-by: David Hildenbrand <david@xxxxxxxxxx>
Signed-off-by: Fuad Tabba <tabba@xxxxxxxxxx>
---


Acked-by: David Hildenbrand <david@xxxxxxxxxx>

--
Cheers,

David / dhildenb

References:
- [PATCH v11 00/18] KVM: Mapping guest_memfd backed memory at the host for software protected VMs
  - From: Fuad Tabba
- [PATCH v11 09/18] KVM: guest_memfd: Track shared memory support in memslot
  - From: Fuad Tabba

Prev by Date: Re: [PATCH v11 08/18] KVM: guest_memfd: Allow host to map guest_memfd pages
Next by Date: Re: [PATCH v11 11/18] KVM: x86: Consult guest_memfd when computing max_mapping_level
Previous by thread: [PATCH v11 09/18] KVM: guest_memfd: Track shared memory support in memslot
Next by thread: Re: [PATCH v11 09/18] KVM: guest_memfd: Track shared memory support in memslot
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]