From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
borntraeger@de.ibm.com, nrb@linux.ibm.com, seiden@linux.ibm.com,
gra@linux.ibm.com, schlameuss@linux.ibm.com, hca@linux.ibm.com,
david@kernel.org
Subject: Re: [PATCH v2 7/8] KVM: s390: vsie: Fix guest page tables protection
Date: Tue, 24 Mar 2026 16:20:46 +0100 [thread overview]
Message-ID: <b9d39789-be93-4133-bad9-09db4f90c169@linux.ibm.com> (raw)
In-Reply-To: <20260320161542.202913-8-imbrenda@linux.ibm.com>
On 3/20/26 17:15, Claudio Imbrenda wrote:
> When shadowing, the guest page tables are write-protected, in order to
> trap changes and properly unshadow the shadow mapping for the nested
> guest. Already shadowed levels are skipped, so that only the needed
> levels are write protected.
>
> Currently the levels that get write protected are exactly one level too
> deep: the last level (nested guest memory) gets protected in the wrong
> way, and will be protected again correctly a few lines afterwards; most
> importantly, the highest non-shadowed level does *not* get write
> protected.
>
> Moreover, if the nested guest is running in a real address space, there
> are no DAT tables to shadow.
>
> Write protect the correct levels, so that all the levels that need to
> be protected are protected, and avoid double protecting the last level;
> skip attempting to shadow the DAT tables when the nested guest is
> running in a real address space.
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Fixes: e38c884df921 ("KVM: s390: Switch to new gmap")
> ---
> arch/s390/kvm/gaccess.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/arch/s390/kvm/gaccess.c b/arch/s390/kvm/gaccess.c
> index 1054f9bd107f..17563f889c6b 100644
> --- a/arch/s390/kvm/gaccess.c
> +++ b/arch/s390/kvm/gaccess.c
> @@ -1517,13 +1517,15 @@ static int _gaccess_do_shadow(struct kvm_s390_mmu_cache *mc, struct gmap *sg,
> * Skip levels that are already protected. For each level, protect
> * only the page containing the entry, not the whole table.
> */
> - for (i = gl ; i >= w->level; i--) {
> - rc = gmap_protect_rmap(mc, sg, entries[i - 1].gfn, gpa_to_gfn(saddr),
> - entries[i - 1].pfn, i, entries[i - 1].writable);
Yeah, tt for page tables is -1 and adding -1 ends up being LEVEL_MEM...
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> - if (rc)
> - return rc;
> - if (!sg->parent)
> - return -EAGAIN;
> + if (w->level > LEVEL_MEM) {
> + for (i = gl ; i >= w->level; i--) {
You could have fixed the rogue white space after "gl"
> + rc = gmap_protect_rmap(mc, sg, entries[i].gfn, gpa_to_gfn(saddr),
> + entries[i].pfn, i + 1, entries[i].writable);
> + if (rc)
> + return rc;
> + if (!sg->parent)
> + return -EAGAIN;
> + }
> }
>
> rc = dat_entry_walk(NULL, entries[LEVEL_MEM].gfn, sg->parent->asce, DAT_WALK_LEAF,
next prev parent reply other threads:[~2026-03-24 15:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 16:15 [PATCH v2 0/8] KVM: s390: More memory management fixes Claudio Imbrenda
2026-03-20 16:15 ` [PATCH v2 1/8] KVM: s390: vsie: Fix dat_split_ste() Claudio Imbrenda
2026-03-23 10:46 ` Steffen Eiden
2026-03-23 13:43 ` Christoph Schlameuss
2026-03-24 12:57 ` Janosch Frank
2026-03-20 16:15 ` [PATCH v2 2/8] KVM: s390: Remove non-atomic dat_crstep_xchg() Claudio Imbrenda
2026-03-23 10:46 ` Steffen Eiden
2026-03-20 16:15 ` [PATCH v2 3/8] KVM: s390: vsie: Fix check for pre-existing shadow mapping Claudio Imbrenda
2026-03-23 10:47 ` Steffen Eiden
2026-03-24 13:14 ` Janosch Frank
2026-03-20 16:15 ` [PATCH v2 4/8] KVM: s390: Fix gmap_link() Claudio Imbrenda
2026-03-23 10:47 ` Steffen Eiden
2026-03-24 14:01 ` Janosch Frank
2026-03-20 16:15 ` [PATCH v2 5/8] KVM: s390: vsie: Fix refcount overflow for shadow gmaps Claudio Imbrenda
2026-03-23 10:49 ` Steffen Eiden
2026-03-24 14:35 ` Janosch Frank
2026-03-20 16:15 ` [PATCH v2 6/8] KVM: s390: vsie: Fix unshadowing while shadowing Claudio Imbrenda
2026-03-24 14:52 ` Janosch Frank
2026-03-24 15:28 ` Claudio Imbrenda
2026-03-20 16:15 ` [PATCH v2 7/8] KVM: s390: vsie: Fix guest page tables protection Claudio Imbrenda
2026-03-24 15:20 ` Janosch Frank [this message]
2026-03-20 16:15 ` [PATCH v2 8/8] KVM: s390: Fix KVM_S390_VCPU_FAULT ioctl Claudio Imbrenda
2026-03-23 11:10 ` Steffen Eiden
2026-03-24 8:47 ` Janosch Frank
2026-03-23 11:27 ` Christian Borntraeger
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=b9d39789-be93-4133-bad9-09db4f90c169@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@kernel.org \
--cc=gra@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=schlameuss@linux.ibm.com \
--cc=seiden@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox