Re: [RFC PATCH v1 00/26] KVM: Restricted mapping of guest_memfd at the host and pKVM/arm64 support

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

Subject: Re: [RFC PATCH v1 00/26] KVM: Restricted mapping of guest_memfd at the host and pKVM/arm64 support
From: David Hildenbrand <david@xxxxxxxxxx>
Date: Tue, 27 Feb 2024 15:49:11 +0100
Cc: kvm@xxxxxxxxxxxxxxx, kvmarm@xxxxxxxxxxxxxxx, 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, yu.c.zhang@xxxxxxxxxxxxxxx, 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
In-reply-to: <a09996d9-17be-4017-9297-2004f0bc8ed3@redhat.com>
Organization: Red Hat
References: <20240222161047.402609-1-tabba@google.com> <9e983090-f336-43b9-8f2b-5dabe7e73b72@redhat.com> <CA+EHjTyGDv0z=X_EN5NAv3ZuqHkPw0rPtGmxjmkc21JqZ+oJLw@mail.gmail.com> <a09996d9-17be-4017-9297-2004f0bc8ed3@redhat.com>
User-agent: Mozilla Thunderbird

I missed here "I'm wondering whether ..."

Extending guest_memfd (the one that was promised initially to not be
mmappable) to be mmappable just to avoid some crashes in corner cases is
the right approach. But I'm pretty sure that has all been discussed
before, that's why I am asking about some details :)


--
Cheers,

David / dhildenb

References:
- [RFC PATCH v1 00/26] KVM: Restricted mapping of guest_memfd at the host and pKVM/arm64 support
  - From: Fuad Tabba
- Re: [RFC PATCH v1 00/26] KVM: Restricted mapping of guest_memfd at the host and pKVM/arm64 support
  - From: David Hildenbrand
- Re: [RFC PATCH v1 00/26] KVM: Restricted mapping of guest_memfd at the host and pKVM/arm64 support
  - From: Fuad Tabba
- Re: [RFC PATCH v1 00/26] KVM: Restricted mapping of guest_memfd at the host and pKVM/arm64 support
  - From: David Hildenbrand

Prev by Date: Re: [RFC PATCH v1 00/26] KVM: Restricted mapping of guest_memfd at the host and pKVM/arm64 support
Next by Date: Re: [PATCH v4 53/66] i386/tdx: Wire TDX_REPORT_FATAL_ERROR with GuestPanic facility
Previous by thread: Re: [RFC PATCH v1 00/26] KVM: Restricted mapping of guest_memfd at the host and pKVM/arm64 support
Next by thread: Re: [RFC PATCH v1 00/26] KVM: Restricted mapping of guest_memfd at the host and pKVM/arm64 support
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]