From: Paolo Bonzini <pbonzini@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, david@redhat.com, borntraeger@linux.ibm.com,
cohuck@redhat.com, linux-s390@vger.kernel.org,
imbrenda@linux.ibm.com, seiden@linux.ibm.com, nsg@linux.ibm.com,
farman@linux.ibm.com, agordeev@linux.ibm.com
Subject: Re: [GIT PULL 0/3] KVM: s390: Changes for 6.9
Date: Fri, 15 Mar 2024 11:28:54 +0100 [thread overview]
Message-ID: <CABgObfZA_=W1GoKaQ-OW05rfJAcxf3N5wC=Jj1bn6m3J9QNw+Q@mail.gmail.com> (raw)
In-Reply-To: <20240226122059.58099-1-frankja@linux.ibm.com>
On Mon, Feb 26, 2024 at 1:24 PM Janosch Frank <frankja@linux.ibm.com> wrote:
>
> Paolo,
>
> please pull the 3 fixes that I've held on to as they were very low priority:
> - Memop selftest rotate fix
> - SCLP event bits over indication fix
> - Missing virt_to_phys for the CRYCB fix
>
>
> Attention:
> Three additional patches will go over the main s390 repository since
> Heiko made changes to the FPU handling that caused a conflict with KVM
> but we didn't want to create a feature branch.
Pulled, thanks.
Paolo
> See:
> https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/log/?h=for-next
>
> - KVM: s390: fix access register usage in ioctls
> - KVM: s390: selftests: memop: add a simple AR test
> - KVM: s390: introduce kvm_s390_fpu_(store|load)
>
>
> Cheers,
> Janosch
>
>
> The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:
>
> Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-6.9-1
>
> for you to fetch changes up to 00de073e2420df02ac0f1a19dbfb60ff8eb198be:
>
> KVM: s390: selftest: memop: Fix undefined behavior (2024-02-23 14:02:27 +0100)
>
> ----------------------------------------------------------------
> - Memop selftest rotate fix
> - SCLP event bits over indication fix
> - Missing virt_to_phys for the CRYCB fix
> ----------------------------------------------------------------
> Alexander Gordeev (1):
> KVM: s390: fix virtual vs physical address confusion
>
> Eric Farman (1):
> KVM: s390: only deliver the set service event bits
>
> Nina Schoetterl-Glausch (1):
> KVM: s390: selftest: memop: Fix undefined behavior
>
> arch/s390/kvm/interrupt.c | 4 ++--
> arch/s390/kvm/kvm-s390.c | 2 +-
> tools/testing/selftests/kvm/s390x/memop.c | 2 ++
> 3 files changed, 5 insertions(+), 3 deletions(-)
>
>
>
>
>
> --
> 2.43.2
>
prev parent reply other threads:[~2024-03-15 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 12:13 [GIT PULL 0/3] KVM: s390: Changes for 6.9 Janosch Frank
2024-02-26 12:13 ` [GIT PULL 1/3] KVM: s390: fix virtual vs physical address confusion Janosch Frank
2024-02-26 12:13 ` [GIT PULL 2/3] KVM: s390: only deliver the set service event bits Janosch Frank
2024-02-26 12:13 ` [GIT PULL 3/3] KVM: s390: selftest: memop: Fix undefined behavior Janosch Frank
2024-03-15 10:28 ` Paolo Bonzini [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='CABgObfZA_=W1GoKaQ-OW05rfJAcxf3N5wC=Jj1bn6m3J9QNw+Q@mail.gmail.com' \
--to=pbonzini@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nsg@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).