From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, linux-s390@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.4 10/10] KVM: s390: fix memory slot handling for KVM_SET_USER_MEMORY_REGION
Date: Wed, 5 Jun 2019 14:14:30 +0200 [thread overview]
Message-ID: <d2c1b279-ba67-bd0e-07ef-1587b4aa77d3@de.ibm.com> (raw)
In-Reply-To: <20190604232532.7953-10-sashal@kernel.org>
On 05.06.19 01:25, Sasha Levin wrote:
> From: Christian Borntraeger <borntraeger@de.ibm.com>
>
> [ Upstream commit 19ec166c3f39fe1d3789888a74cc95544ac266d4 ]
>
> kselftests exposed a problem in the s390 handling for memory slots.
> Right now we only do proper memory slot handling for creation of new
> memory slots. Neither MOVE, nor DELETION are handled properly. Let us
> implement those.
I gave this a quick spin on 4.4.y and it seems to work fine.
>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> arch/s390/kvm/kvm-s390.c | 35 +++++++++++++++++++++--------------
> 1 file changed, 21 insertions(+), 14 deletions(-)
>
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index 5ddb1debba95..23911ecfbad6 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -2721,21 +2721,28 @@ void kvm_arch_commit_memory_region(struct kvm *kvm,
> const struct kvm_memory_slot *new,
> enum kvm_mr_change change)
> {
> - int rc;
> -
> - /* If the basics of the memslot do not change, we do not want
> - * to update the gmap. Every update causes several unnecessary
> - * segment translation exceptions. This is usually handled just
> - * fine by the normal fault handler + gmap, but it will also
> - * cause faults on the prefix page of running guest CPUs.
> - */
> - if (old->userspace_addr == mem->userspace_addr &&
> - old->base_gfn * PAGE_SIZE == mem->guest_phys_addr &&
> - old->npages * PAGE_SIZE == mem->memory_size)
> - return;
> + int rc = 0;
>
> - rc = gmap_map_segment(kvm->arch.gmap, mem->userspace_addr,
> - mem->guest_phys_addr, mem->memory_size);
> + switch (change) {
> + case KVM_MR_DELETE:
> + rc = gmap_unmap_segment(kvm->arch.gmap, old->base_gfn * PAGE_SIZE,
> + old->npages * PAGE_SIZE);
> + break;
> + case KVM_MR_MOVE:
> + rc = gmap_unmap_segment(kvm->arch.gmap, old->base_gfn * PAGE_SIZE,
> + old->npages * PAGE_SIZE);
> + if (rc)
> + break;
> + /* FALLTHROUGH */
> + case KVM_MR_CREATE:
> + rc = gmap_map_segment(kvm->arch.gmap, mem->userspace_addr,
> + mem->guest_phys_addr, mem->memory_size);
> + break;
> + case KVM_MR_FLAGS_ONLY:
> + break;
> + default:
> + WARN(1, "Unknown KVM MR CHANGE: %d\n", change);
> + }
> if (rc)
> pr_warn("failed to commit memory region\n");
> return;
>
prev parent reply other threads:[~2019-06-05 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190604232532.7953-1-sashal@kernel.org>
2019-06-04 23:25 ` [PATCH AUTOSEL 4.4 10/10] KVM: s390: fix memory slot handling for KVM_SET_USER_MEMORY_REGION Sasha Levin
2019-06-05 12:14 ` Christian Borntraeger [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=d2c1b279-ba67-bd0e-07ef-1587b4aa77d3@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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