| Message ID | 20230824124522.75408-1-frankja@linux.ibm.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On 8/24/23 14:43, Janosch Frank wrote: > Hello Paolo, > > please pull the following changes for 6.6. > @Paolo: Seems like neither Claudio (who picked the selftest) nor I had a closer look into the x86 selftest changes and Nina just informed me that this might lead to problems. Please hold back on this pull request, I'll send a new one on Monday where we'll pull in the selftest changes and have a fixed up version of the selftest. I've spoken to Ilya privately and he's ok with Claudio fixing this up.
On Fri, Aug 25, 2023, Janosch Frank wrote: > On 8/24/23 14:43, Janosch Frank wrote: > > Hello Paolo, > > > > please pull the following changes for 6.6. > > > > @Paolo: > Seems like neither Claudio (who picked the selftest) nor I had a closer look > into the x86 selftest changes and Nina just informed me that this might lead > to problems. > > Please hold back on this pull request, I'll send a new one on Monday where > we'll pull in the selftest changes and have a fixed up version of the > selftest. I've spoken to Ilya privately and he's ok with Claudio fixing this > up. If you haven't already done a merge, I pushed https://github.com/kvm-x86/linux.git tags/kvm-x86-selftests-immutable-6.6 to guarantee a stable point (I have a few last minute selftests fixes for 6.6 that I'm planning on applying "soon"). Thanks for dealing with the conflicts, let me know if you run into any problems.
On 8/25/23 17:58, Sean Christopherson wrote: > On Fri, Aug 25, 2023, Janosch Frank wrote: >> On 8/24/23 14:43, Janosch Frank wrote: >>> Hello Paolo, >>> >>> please pull the following changes for 6.6. >>> >> >> @Paolo: >> Seems like neither Claudio (who picked the selftest) nor I had a closer look >> into the x86 selftest changes and Nina just informed me that this might lead >> to problems. >> >> Please hold back on this pull request, I'll send a new one on Monday where >> we'll pull in the selftest changes and have a fixed up version of the >> selftest. I've spoken to Ilya privately and he's ok with Claudio fixing this >> up. > > If you haven't already done a merge, I pushed > > https://github.com/kvm-x86/linux.git tags/kvm-x86-selftests-immutable-6.6 > > to guarantee a stable point (I have a few last minute selftests fixes for 6.6 > that I'm planning on applying "soon"). > > Thanks for dealing with the conflicts, let me know if you run into any problems. Hey Sean / Paolo, I've pulled this in, fixed up the selftest and pushed it to the repo for everyone to have a look at. I'll give it a night in the CI and send a new PULL request tomorrow if you guys don't complain. :)
Hello Paolo, please pull the following changes for 6.6. Please note that Heiko and I both merged Heiko's vfio-ap feature branch. We had to do that since vfio-ap patches go through his s390 repository but Steffen's KVM cpumodel patches are based on Tony's vfio-ap changes. In the long run we're considering putting vfio-ap patches into their own repository but for 6.6 we didn't find the time to speak with all affected maintainers. - PV crypto passthrough enablement (Tony, Steffen, Viktor, Janosch) Allows a PV guest to use crypto cards. Card access is governed by the firmware and once a crypto queue is "bound" to a PV VM every other entity (PV or not) looses access until it is not bound anymore. Enablement is done via flags when creating the PV VM. - Guest debug fixes (Ilya) The following changes since commit fdf0eaf11452d72945af31804e2a1048ee1b574c: Linux 6.5-rc2 (2023-07-16 15:10:37 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-6.6-1 for you to fetch changes up to b1d8b21681db97b775d05ebc39c4d662192c8f15: KVM: s390: pv: Allow AP-instructions for pv-guests (2023-08-18 16:11:39 +0200) ---------------------------------------------------------------- Ilya Leoshkevich (6): KVM: s390: interrupt: Fix single-stepping into interrupt handlers KVM: s390: interrupt: Fix single-stepping into program interrupt handlers KVM: s390: interrupt: Fix single-stepping kernel-emulated instructions KVM: s390: interrupt: Fix single-stepping userspace-emulated instructions KVM: s390: interrupt: Fix single-stepping keyless mode exits KVM: s390: selftests: Add selftest for single-stepping Janosch Frank (2): s390/uv: export uv_pin_shared for direct usage Merge remote-tracking branch 'vfio-ap' into kvm-next Steffen Eiden (3): s390/uv: UV feature check utility KVM: s390: Add UV feature negotiation KVM: s390: pv: Allow AP-instructions for pv-guests Tony Krowiak (11): s390/vfio-ap: no need to check the 'E' and 'I' bits in APQSW after TAPQ s390/vfio-ap: clean up irq resources if possible s390/vfio-ap: wait for response code 05 to clear on queue reset s390/vfio-ap: allow deconfigured queue to be passed through to a guest s390/vfio-ap: remove upper limit on wait for queue reset to complete s390/vfio-ap: store entire AP queue status word with the queue object s390/vfio-ap: use work struct to verify queue reset s390/vfio-ap: handle queue state change in progress on reset s390/vfio-ap: check for TAPQ response codes 0x35 and 0x36 KVM: s390: export kvm_s390_pv*_is_protected functions s390/vfio-ap: make sure nib is shared Viktor Mihajlovski (1): KVM: s390: pv: relax WARN_ONCE condition for destroy fast arch/s390/include/asm/kvm_host.h | 5 + arch/s390/include/asm/uv.h | 25 +++- arch/s390/include/uapi/asm/kvm.h | 16 +++ arch/s390/kernel/uv.c | 5 +- arch/s390/kvm/intercept.c | 38 +++++- arch/s390/kvm/interrupt.c | 14 ++ arch/s390/kvm/kvm-s390.c | 102 ++++++++++++++- arch/s390/kvm/kvm-s390.h | 12 -- arch/s390/kvm/pv.c | 23 +++- arch/s390/mm/fault.c | 2 +- drivers/s390/crypto/vfio_ap_ops.c | 172 ++++++++++++++++--------- drivers/s390/crypto/vfio_ap_private.h | 6 +- tools/testing/selftests/kvm/Makefile | 1 + tools/testing/selftests/kvm/s390x/debug_test.c | 160 +++++++++++++++++++++++ 14 files changed, 486 insertions(+), 95 deletions(-) create mode 100644 tools/testing/selftests/kvm/s390x/debug_test.c