From: Greg KH <gregkh@linuxfoundation.org>
To: Will Deacon <will@kernel.org>
Cc: linux-kernel@vger.kernel.org, maz@kernel.org,
suzuki.poulose@arm.com, james.morse@arm.com, pbonzini@redhat.com,
kernel-team@android.com, stable@vger.kernel.org
Subject: Re: [PATCH stable-5.8.y backport 1/2] KVM: Pass MMU notifier range flags to kvm_unmap_hva_range()
Date: Mon, 24 Aug 2020 17:19:33 +0200 [thread overview]
Message-ID: <20200824151933.GB435319@kroah.com> (raw)
In-Reply-To: <20200824113048.24960-1-will@kernel.org>
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@vger.kernel.org> # v5.8 only
This matched the 5.8 patch I had already, but I took it just to be safe,
thanks :)
greg k-h
prev parent reply other threads:[~2020-08-24 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 11:30 [PATCH stable-5.8.y backport 1/2] KVM: Pass MMU notifier range flags to kvm_unmap_hva_range() Will Deacon
2020-08-24 11:30 ` [PATCH stable-5.8.y backport 2/2] KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is not set Will Deacon
2020-08-24 15:19 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200824151933.GB435319@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox