From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: KVM <kvm@vger.kernel.org>, Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Jaehoon Kim <jhkim@linux.ibm.com>,
Douglas Freimuth <freimuth@linux.ibm.com>,
Farhan Ali <alifm@linux.ibm.com>
Subject: Re: [GIT PULL 0/7] KVM: s390: Fixes for 7.2
Date: Thu, 30 Jul 2026 12:35:41 +0200 [thread overview]
Message-ID: <777b4913-b98d-46c9-939a-bb79d5c89840@linux.ibm.com> (raw)
In-Reply-To: <20260727095720.9150-1-borntraeger@linux.ibm.com>
Paolo,
I have now more patches in virtio-ccw
Same as pci, mostly triggered by AR review.
sashiko feedback is here
https://sashiko.dev/#/patchset/20260728033022.2658232-1-farman%40linux.ibm.com
Shall I simply send a
tags/kvm-s390-master-7.2-3
tag with those as well?
This would be https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/log/
The existing patches from 7.2-2 have been reviewed by sashiko here
https://sashiko.dev/#/patchset/20260723221409.5874-1-alifm%40linux.ibm.com
and
https://sashiko.dev/#/patchset/20260724133943.1664961-1-jhkim%40linux.ibm.com
just fine,
but my pull request itself did not work well with sashiko as it failed to partially
apply my patches and then complained about things that have been fixed in those.
We might even have some more fixes from Claudio this time around, we should probably
then do another pull request early next week. Or do you prefer to wait for those?
Christian
Am 27.07.26 um 11:57 schrieb Christian Borntraeger:
> Paolo,
>
> some more fixes triggered by AI bug reports or testing.
> Mostly for PCI support.
> This also has a regression fix that we introduced in 7.2-rc1
>
> The following changes since commit 3e3aa6da87d30a0064a17b836685cd43c90a3572:
>
> KVM: s390: pci: Fix handling of AIF enable without AISB (2026-07-09 16:23:10 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-master-7.2-2
>
> for you to fetch changes up to 9972befc3e34ff8b6847198c84f11bfc312dde40:
>
> KVM: s390: Fall back to short-term pinning in MAP ioctl (2026-07-27 09:23:53 +0200)
>
>
> All fixes had no new sashiko findings, just pre-existing issues or
> finding that are being fixed by other patches of the series.
>
> We have some more fixes pending for gmap and vfio-ccw that still need
> testing or sashiko fixups, but we should process these fixes now.
>
>
> ----------------------------------------------------------------
> KVM: s390: Fixes for 7.2
>
> - several fixes for PCI passthru in s390 kvm
> - fix a 7.2-rc regression in the adapter interrupt mapping code
>
> ----------------------------------------------------------------
> Farhan Ali (6):
> KVM: s390: pci: Reject adapter interrupt forwarding if already enabled
> KVM: s390: pci: Fix memory accounting for pinned/unpinned pages
> KVM: s390: pci: Fix missing error codes and memory unaccounting
> KVM: s390: pci: Fix NULL dereference on AIBV allocation failure
> KVM: s390: pci: Fix resource leak on IRQ registration failure
> KVM: s390: pci: Validate AIBV and AISB before pinning guest pages
>
> Jaehoon Kim (1):
> KVM: s390: Fall back to short-term pinning in MAP ioctl
>
> Documentation/virt/kvm/devices/s390_flic.rst | 15 +++-
> arch/s390/include/asm/kvm_host.h | 5 ++
> arch/s390/kvm/interrupt.c | 56 ++++++++++----
> arch/s390/kvm/pci.c | 107 +++++++++++++++++++++------
> arch/s390/kvm/pci.h | 2 +
> 5 files changed, 148 insertions(+), 37 deletions(-)
>
prev parent reply other threads:[~2026-07-30 10:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 9:57 [GIT PULL 0/7] KVM: s390: Fixes for 7.2 Christian Borntraeger
2026-07-27 9:57 ` [GIT PULL 1/7] KVM: s390: pci: Reject adapter interrupt forwarding if already enabled Christian Borntraeger
2026-07-27 10:13 ` sashiko-bot
2026-07-27 9:57 ` [GIT PULL 2/7] KVM: s390: pci: Fix memory accounting for pinned/unpinned pages Christian Borntraeger
2026-07-27 10:11 ` sashiko-bot
2026-07-27 11:15 ` Christian Borntraeger
2026-07-27 9:57 ` [GIT PULL 3/7] KVM: s390: pci: Fix missing error codes and memory unaccounting Christian Borntraeger
2026-07-27 9:57 ` [GIT PULL 4/7] KVM: s390: pci: Fix NULL dereference on AIBV allocation failure Christian Borntraeger
2026-07-27 9:57 ` [GIT PULL 5/7] KVM: s390: pci: Fix resource leak on IRQ registration failure Christian Borntraeger
2026-07-27 9:57 ` [GIT PULL 6/7] KVM: s390: pci: Validate AIBV and AISB before pinning guest pages Christian Borntraeger
2026-07-27 10:18 ` sashiko-bot
2026-07-27 9:57 ` [GIT PULL 7/7] KVM: s390: Fall back to short-term pinning in MAP ioctl Christian Borntraeger
2026-07-27 10:10 ` sashiko-bot
2026-07-27 11:24 ` [GIT PULL 0/7] KVM: s390: Fixes for 7.2 Christian Borntraeger
2026-07-30 10:35 ` 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=777b4913-b98d-46c9-939a-bb79d5c89840@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=freimuth@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jhkim@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=svens@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