[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC v2 PATCH 13/13] KVM: Enable memfd based page invalidation/fallo
|
From: |
Chao Peng |
|
Subject: |
Re: [RFC v2 PATCH 13/13] KVM: Enable memfd based page invalidation/fallocate |
|
Date: |
Tue, 23 Nov 2021 23:00:28 +0800 |
|
User-agent: |
Mutt/1.9.4 (2018-02-28) |
On Tue, Nov 23, 2021 at 10:09:28AM +0100, Paolo Bonzini wrote:
> On 11/23/21 02:06, Chao Peng wrote:
> > > Maybe the kvm has to be tagged with a sequential id that incremented every
> > > allocation. This id can be checked here.
> > Sounds like a sequential id will be needed, no existing fields in struct
> > kvm can work for this.
>
> There's no need to new concepts when there's a perfectly usable reference
> count. :)
Indeed, thanks.
>
> Paolo
- [RFC v2 PATCH 09/13] KVM: Introduce kvm_memfd_invalidate_range, (continued)
- [RFC v2 PATCH 09/13] KVM: Introduce kvm_memfd_invalidate_range, Chao Peng, 2021/11/19
- [RFC v2 PATCH 10/13] KVM: Match inode for invalidation of fd-based slot, Chao Peng, 2021/11/19
- [RFC v2 PATCH 11/13] KVM: Add kvm_map_gfn_range, Chao Peng, 2021/11/19
- [RFC v2 PATCH 12/13] KVM: Introduce kvm_memfd_fallocate_range, Chao Peng, 2021/11/19
- [RFC v2 PATCH 13/13] KVM: Enable memfd based page invalidation/fallocate, Chao Peng, 2021/11/19
- Re: [RFC v2 PATCH 13/13] KVM: Enable memfd based page invalidation/fallocate, Paolo Bonzini, 2021/11/23