From: Vasily Gorbik <gor@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [GIT PULL] s390 updates for 5.11-rc6
Date: Sat, 30 Jan 2021 16:32:38 +0100 [thread overview]
Message-ID: <your-ad-here.call-01612020758-ext-9054@work.hours> (raw)
Hello Linus,
please pull s390 fixes for 5.11-rc6.
Thank you,
Vasily
The following changes since commit 6ee1d745b7c9fd573fba142a2efdad76a9f1cb04:
Linux 5.11-rc5 (2021-01-24 16:47:14 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-5.11-4
for you to fetch changes up to e82080e1f456467cc185fe65ee69fe9f9bd0b576:
s390: uv: Fix sysfs max number of VCPUs reporting (2021-01-27 13:00:04 +0100)
----------------------------------------------------------------
- Fix max number of VCPUs reported via ultravisor information sysfs interface.
- Fix memory leaks during vfio-ap resources clean up on KVM pointer
invalidation notification.
- Fix potential specification exception by avoiding unnecessary interrupts
disable after queue reset in vfio-ap.
----------------------------------------------------------------
Janosch Frank (1):
s390: uv: Fix sysfs max number of VCPUs reporting
Tony Krowiak (2):
s390/vfio-ap: clean up vfio_ap resources when KVM pointer invalidated
s390/vfio-ap: No need to disable IRQ after queue reset
arch/s390/boot/uv.c | 2 +-
arch/s390/include/asm/uv.h | 4 +-
arch/s390/kernel/uv.c | 2 +-
drivers/s390/crypto/vfio_ap_drv.c | 6 +-
drivers/s390/crypto/vfio_ap_ops.c | 149 ++++++++++++++++++++--------------
drivers/s390/crypto/vfio_ap_private.h | 12 +--
6 files changed, 101 insertions(+), 74 deletions(-)
next reply other threads:[~2021-01-30 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 15:32 Vasily Gorbik [this message]
2021-01-30 20:01 ` [GIT PULL] s390 updates for 5.11-rc6 pr-tracker-bot
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=your-ad-here.call-01612020758-ext-9054@work.hours \
--to=gor@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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