From: Janosch Frank <frankja@linux.ibm.com>
To: pbonzini@redhat.com
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, 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
Subject: [GIT PULL 0/4] KVM: s390: Changes for 6.8
Date: Tue, 2 Jan 2024 14:34:51 +0100 [thread overview]
Message-ID: <20240102133629.108405-1-frankja@linux.ibm.com> (raw)
Dear Paolo,
please pull the following changes for 6.8.
The changes are fixes/cleanups that didn't require a fix pull and
hence landed in next.
-The uvdevice didn't return a firmware return value to
userspace. This didn't matter since that value was unused but might
be used in the future.
-The stfle vsie code was not 100% spec compliant because it checked
for readability of an area that was larger than the one accessed by
firmware. Additionally there was an issue with a mask being applied
to early.
The following changes since commit 98b1cc82c4affc16f5598d4fa14b1858671b2263:
Linux 6.7-rc2 (2023-11-19 15:02:14 -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.8-1
for you to fetch changes up to 10f7b1dcdfe05efcd26e90e337daf1bfd8f4a6da:
KVM: s390: cpu model: Use proper define for facility mask size (2023-12-23 10:41:09 +0100)
----------------------------------------------------------------
- uvdevice fixed additional data return length (Steffen)
- stfle (feature indication) vsie fixes and minor cleanup (Nina)
----------------------------------------------------------------
Nina Schoetterl-Glausch (3):
KVM: s390: vsie: Fix STFLE interpretive execution identification
KVM: s390: vsie: Fix length of facility list shadowed
KVM: s390: cpu model: Use proper define for facility mask size
Steffen Eiden (1):
s390/uvdevice: Report additional-data length for attestation
arch/s390/include/asm/facility.h | 6 ++++++
arch/s390/include/asm/kvm_host.h | 2 +-
arch/s390/kernel/Makefile | 2 +-
arch/s390/kernel/facility.c | 21 +++++++++++++++++++++
arch/s390/kvm/vsie.c | 19 +++++++++++++++++--
drivers/s390/char/uvdevice.c | 3 +++
6 files changed, 49 insertions(+), 4 deletions(-)
create mode 100644 arch/s390/kernel/facility.c
--
2.43.0
next reply other threads:[~2024-01-02 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 13:34 Janosch Frank [this message]
2024-01-02 13:34 ` [GIT PULL 1/4] s390/uvdevice: Report additional-data length for attestation Janosch Frank
2024-01-02 13:34 ` [GIT PULL 2/4] KVM: s390: vsie: Fix STFLE interpretive execution identification Janosch Frank
2024-01-02 13:34 ` [GIT PULL 3/4] KVM: s390: vsie: Fix length of facility list shadowed Janosch Frank
2024-01-02 13:34 ` [GIT PULL 4/4] KVM: s390: cpu model: Use proper define for facility mask size Janosch Frank
2024-01-02 18:19 ` [GIT PULL 0/4] KVM: s390: Changes for 6.8 Paolo Bonzini
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=20240102133629.108405-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nsg@linux.ibm.com \
--cc=pbonzini@redhat.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