From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Cc: kvm@vger.kernel.org, npiggin@gmail.com, kvm-ppc@vger.kernel.org,
pbonzini@redhat.com, seanjc@google.com
Subject: Re: [PATCH] KVM: PPC: Book3S HV: Fix kvm_unmap_gfn_range_hv() for Hash MMU
Date: Sun, 16 May 2021 08:43:54 +1000 [thread overview]
Message-ID: <162111863429.1890426.10684298398002879085.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210511105459.800788-1-mpe@ellerman.id.au>
On Tue, 11 May 2021 20:54:59 +1000, Michael Ellerman wrote:
> Commit 32b48bf8514c ("KVM: PPC: Book3S HV: Fix conversion to gfn-based
> MMU notifier callbacks") fixed kvm_unmap_gfn_range_hv() by adding a for
> loop over each gfn in the range.
>
> But for the Hash MMU it repeatedly calls kvm_unmap_rmapp() with the
> first gfn of the range, rather than iterating through the range.
>
> [...]
Applied to powerpc/fixes.
[1/1] KVM: PPC: Book3S HV: Fix kvm_unmap_gfn_range_hv() for Hash MMU
https://git.kernel.org/powerpc/c/da3bb206c9ceb0736d9e2897ea697acabad35833
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Cc: kvm-ppc@vger.kernel.org, pbonzini@redhat.com, npiggin@gmail.com,
kvm@vger.kernel.org, seanjc@google.com
Subject: Re: [PATCH] KVM: PPC: Book3S HV: Fix kvm_unmap_gfn_range_hv() for Hash MMU
Date: Sun, 16 May 2021 08:43:54 +1000 [thread overview]
Message-ID: <162111863429.1890426.10684298398002879085.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210511105459.800788-1-mpe@ellerman.id.au>
On Tue, 11 May 2021 20:54:59 +1000, Michael Ellerman wrote:
> Commit 32b48bf8514c ("KVM: PPC: Book3S HV: Fix conversion to gfn-based
> MMU notifier callbacks") fixed kvm_unmap_gfn_range_hv() by adding a for
> loop over each gfn in the range.
>
> But for the Hash MMU it repeatedly calls kvm_unmap_rmapp() with the
> first gfn of the range, rather than iterating through the range.
>
> [...]
Applied to powerpc/fixes.
[1/1] KVM: PPC: Book3S HV: Fix kvm_unmap_gfn_range_hv() for Hash MMU
https://git.kernel.org/powerpc/c/da3bb206c9ceb0736d9e2897ea697acabad35833
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Cc: kvm@vger.kernel.org, npiggin@gmail.com, kvm-ppc@vger.kernel.org,
pbonzini@redhat.com, seanjc@google.com
Subject: Re: [PATCH] KVM: PPC: Book3S HV: Fix kvm_unmap_gfn_range_hv() for Hash MMU
Date: Sat, 15 May 2021 22:43:54 +0000 [thread overview]
Message-ID: <162111863429.1890426.10684298398002879085.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210511105459.800788-1-mpe@ellerman.id.au>
On Tue, 11 May 2021 20:54:59 +1000, Michael Ellerman wrote:
> Commit 32b48bf8514c ("KVM: PPC: Book3S HV: Fix conversion to gfn-based
> MMU notifier callbacks") fixed kvm_unmap_gfn_range_hv() by adding a for
> loop over each gfn in the range.
>
> But for the Hash MMU it repeatedly calls kvm_unmap_rmapp() with the
> first gfn of the range, rather than iterating through the range.
>
> [...]
Applied to powerpc/fixes.
[1/1] KVM: PPC: Book3S HV: Fix kvm_unmap_gfn_range_hv() for Hash MMU
https://git.kernel.org/powerpc/c/da3bb206c9ceb0736d9e2897ea697acabad35833
cheers
next prev parent reply other threads:[~2021-05-15 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 10:54 [PATCH] KVM: PPC: Book3S HV: Fix kvm_unmap_gfn_range_hv() for Hash MMU Michael Ellerman
2021-05-11 10:54 ` Michael Ellerman
2021-05-11 10:54 ` Michael Ellerman
2021-05-11 16:39 ` Sean Christopherson
2021-05-11 16:39 ` Sean Christopherson
2021-05-12 3:20 ` Michael Ellerman
2021-05-12 3:20 ` Michael Ellerman
2021-05-12 3:20 ` Michael Ellerman
2021-05-15 22:43 ` Michael Ellerman [this message]
2021-05-15 22:43 ` Michael Ellerman
2021-05-15 22:43 ` Michael Ellerman
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=162111863429.1890426.10684298398002879085.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.