[PATCH] KVM: allow NULL writable argument to __kvm_faultin_pfn

 > On 06 January 2025 at 07:57 pm, Sean Christopherson wrote: > > On Wed, Jan 01, 2025, Paolo Bonzini wrote: >> kvm_follow_pfn() is able to work with NULL in the .map_writable field >> of the homonymous struct. But __kvm_faultin_pfn() rejects the combo >> despite KVM for e500 trying to use it

[PATCH] KVM: allow NULL writable argument to __kvm_faultin_pfn

> On 06 January 2025 at 07:57 pm, Sean Christopherson wrote: > > On Wed, Jan 01, 2025, Paolo Bonzini wrote: >> kvm_follow_pfn() is able to work with NULL in the .map_writable field >> of the homonymous struct. But __kvm_faultin_pfn() rejects the combo >> despite KVM for e500 trying to use it

Re: [PATCH] KVM: allow NULL writable argument to __kvm_faultin_pfn

On Mon, Jan 06, 2025, Sean Christopherson wrote: > On Wed, Jan 01, 2025, Paolo Bonzini wrote: > > kvm_follow_pfn() is able to work with NULL in the .map_writable field > > of the homonymous struct. But __kvm_faultin_pfn() rejects the combo > > despite KVM for e500 trying to use it. Indeed .map_wr

Re: [PATCH] KVM: allow NULL writable argument to __kvm_faultin_pfn

On Wed, Jan 01, 2025, Paolo Bonzini wrote: > kvm_follow_pfn() is able to work with NULL in the .map_writable field > of the homonymous struct. But __kvm_faultin_pfn() rejects the combo > despite KVM for e500 trying to use it. Indeed .map_writable is not > particularly useful if the flags include

[PATCH] KVM: allow NULL writable argument to __kvm_faultin_pfn

kvm_follow_pfn() is able to work with NULL in the .map_writable field of the homonymous struct. But __kvm_faultin_pfn() rejects the combo despite KVM for e500 trying to use it. Indeed .map_writable is not particularly useful if the flags include FOLL_WRITE and readonly guest memory is not support