From: Marc Zyngier <maz@kernel.org>
To: Andreas Grapentin <gra@linux.ibm.com>
Cc: Steffen Eiden <seiden@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@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>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM: s390: arm64: Fixes for arm64 KVM support
Date: Tue, 03 Nov 2026 18:31:31 +0000 [thread overview]
Message-ID: <864idx3gxo.wl-maz@kernel.org> (raw)
In-Reply-To: <20261103-s390_arm64_kvm_fixups-v1-0-21c36fedd878@linux.ibm.com>
On Tue, 03 Nov 2026 16:37:01 +0000,
Andreas Grapentin <gra@linux.ibm.com> wrote:
>
> Some fixups for the previous series that introduced arm64 KVM support on
> s390. Forward-declare enum vcpu_sysreg because we are definitely going
> to need that, then make the module naming consistent and iron out an
> inconsistency in the definition of vcpu->arch.pause between s390 and
> native arm64 KVM.
It's an interesting one. Obviously, this wasn't caught by building the
upstream code. I guess this triggered with the rest of the patches?
>
> No functional changes intended on either arm64 or s390.
>
> Signed-off-by: Andreas Grapentin <gra@linux.ibm.com>
> ---
> Andreas Grapentin (2):
> KVM: s390: arm64: Declare enum vcpu_sysreg
> KVM: s390: arm64: Fix kvm_arm64 module naming consistency
>
> Steffen Eiden (1):
> KVM: s390: arm64: Turn vcpu->arch.pause into a counter
>
> arch/s390/include/asm/kvm_host_arm64.h | 8 ++++----
> arch/s390/kvm/arm64/Makefile | 12 ++++++------
> 2 files changed, 10 insertions(+), 10 deletions(-)
Looks all reasonable to me.
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-11-03 18:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 16:37 [PATCH 0/3] KVM: s390: arm64: Fixes for arm64 KVM support Andreas Grapentin
2026-11-03 16:37 ` [PATCH 1/3] KVM: s390: arm64: Turn vcpu->arch.pause into a counter Andreas Grapentin
2026-11-03 16:41 ` sashiko-bot
2026-11-04 8:12 ` Andreas Grapentin
2026-11-03 16:37 ` [PATCH 2/3] KVM: s390: arm64: Declare enum vcpu_sysreg Andreas Grapentin
2026-11-03 16:41 ` sashiko-bot
2026-11-04 8:01 ` Steffen Eiden
2026-11-04 9:20 ` Christian Borntraeger
2026-11-03 16:37 ` [PATCH 3/3] KVM: s390: arm64: Fix kvm_arm64 module naming consistency Andreas Grapentin
2026-11-03 16:41 ` sashiko-bot
2026-11-04 8:07 ` Steffen Eiden
2026-11-04 9:16 ` Christian Borntraeger
2026-11-03 18:31 ` Marc Zyngier [this message]
2026-11-04 7:59 ` [PATCH 0/3] KVM: s390: arm64: Fixes for arm64 KVM support Steffen Eiden
2026-11-05 12:45 ` 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=864idx3gxo.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gor@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=seiden@linux.ibm.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 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.