mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	frankja@linux.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 v5 00/10] KVM: s390: More memory management fixes
Date: Thu, 26 Mar 2026 15:48:59 +0100	[thread overview]
Message-ID: <f894d3f7-01a2-46c7-b2b0-5933919dfe98@de.ibm.com> (raw)
In-Reply-To: <20260326131719.98229-1-imbrenda@linux.ibm.com>

Am 26.03.26 um 14:17 schrieb Claudio Imbrenda:
> This series fixes some bugs that have been recently introduced with the
> big gmap rewrite.
> 
> Most of the fixes are related to vSIE (nested guests), although some
> are more general. The last patch fixes an issue introduced last year.
> 
> v4->v5
> * Use gmap_crstep_xchg_atomic() in gmap_handle_minor_crste_fault()
>    instead of dat_crstep_xchg_atomic()
> * Check the special bit in the new pte and crste, instead of the old
>    one in _gmap_crstep_xchg_atomic() and in _gmap_ptep_xchg()
> * Fix handling of pgste spinlock
> * Handle more unshadowing events in _do_shadow_pte() and in
>    _do_shadow_crste()

Lets add this version to kvms390/master. This already is much much better
than the current 7.0-rc state. It is hard to review the differences and
we want to get these fixes queued asap. kvms390/master is picked up by
next so we will have CI coverage inside (and outside) of IBM.

If something is really broken we can refresh kvms390/master, otherwise
we can still do followup patches.

      parent reply	other threads:[~2026-03-26 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 13:17 Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 01/10] KVM: s390: vsie: Fix dat_split_ste() Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 02/10] KVM: s390: Remove non-atomic dat_crstep_xchg() Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 03/10] KVM: s390: vsie: Fix check for pre-existing shadow mapping Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 04/10] KVM: s390: Fix gmap_link() Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 05/10] KVM: s390: Correctly handle guest mappings without struct page Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 06/10] KVM: s390: vsie: Fix nested guest memory shadowing Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 07/10] KVM: s390: vsie: Fix refcount overflow for shadow gmaps Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 08/10] KVM: s390: vsie: Fix unshadowing while shadowing Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 09/10] KVM: s390: vsie: Fix guest page tables protection Claudio Imbrenda
2026-03-26 13:17 ` [PATCH v5 10/10] KVM: s390: Fix KVM_S390_VCPU_FAULT ioctl Claudio Imbrenda
2026-03-26 14:48 ` 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=f894d3f7-01a2-46c7-b2b0-5933919dfe98@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=david@kernel.org \
    --cc=frankja@linux.ibm.com \
    --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

all inboxes | Powered by JetHome®