On Mon, Aug 24, 2020 at 12:30:47PM +0100, Will Deacon wrote:
> commit fdfe7cbd58806522e799e2a50a15aee7f2cbb7b6 upstream.
>
> The 'flags' field of 'struct mmu_notifier_range' is used to indicate
> whether invalidate_range_{start,end}() are permitted to block. In the
> case of kvm_mmu_notifier_invalidate_range_start(), this field is not
> forwarded on to the architecture-specific implementation of
> kvm_unmap_hva_range() and therefore the backend cannot sensibly decide
> whether or not to block.
>
> Add an extra 'flags' parameter to kvm_unmap_hva_range() so that
> architectures are aware as to whether or not they are permitted to block.
>
> Cc: <stable@xxxxxxxxxxxxxxx> # v5.8 only
This matched the 5.8 patch I had already, but I took it just to be safe,
thanks :)
greg k-h
