On Thu, 15 Feb 2024 15:28:55 +0000, Paul Durrant wrote: > From: Paul Durrant <pdurrant@xxxxxxxxxx> > > This series contains a new patch from Sean added since v12 [1]: > > * KVM: s390: Refactor kvm_is_error_gpa() into kvm_is_gpa_in_memslot() > > This frees up the function name kvm_is_error_gpa() such that it can then be > re-defined in: > > [...] *sigh* I forgot to hit "send" on this yesterday. But lucky for me, that worked out in my favor as I needed to rebase on top of kvm/kvm-uapi to avoid pointless conflicts in the uapi headeres. So.... Applied to kvm-x86 xen, minus 18 and 19 (trylock stuff) and 21 (locking cleanup that we're doing elsewhere). Paul and David, please take (another) look at the end result to make sure you don't object to any of my tweaks and that I didn't botch anything. s390 folks, I'm applying/pushing now to get it into -next asap, but I'll make sure to get acks/reviews on patch 08/21 before I do anything else with this branch/series. Thanks! [01/21] KVM: pfncache: Add a map helper function https://github.com/kvm-x86/linux/commit/f39b80e3ff12 [02/21] KVM: pfncache: remove unnecessary exports https://github.com/kvm-x86/linux/commit/41496fffc0e1 [03/21] KVM: x86/xen: mark guest pages dirty with the pfncache lock held https://github.com/kvm-x86/linux/commit/4438355ec6e1 [04/21] KVM: pfncache: add a mark-dirty helper https://github.com/kvm-x86/linux/commit/78b74638eb6d [05/21] KVM: pfncache: remove KVM_GUEST_USES_PFN usage https://github.com/kvm-x86/linux/commit/a4bff3df5147 [06/21] KVM: pfncache: stop open-coding offset_in_page() https://github.com/kvm-x86/linux/commit/53e63e953e14 [07/21] KVM: pfncache: include page offset in uhva and use it consistently https://github.com/kvm-x86/linux/commit/406c10962a4c [08/21] KVM: s390: Refactor kvm_is_error_gpa() into kvm_is_gpa_in_memslot() https://github.com/kvm-x86/linux/commit/9e7325acb3dc [09/21] KVM: pfncache: allow a cache to be activated with a fixed (userspace) HVA https://github.com/kvm-x86/linux/commit/721f5b0dda78 [10/21] KVM: x86/xen: separate initialization of shared_info cache and content https://github.com/kvm-x86/linux/commit/c01c55a34f28 [11/21] KVM: x86/xen: re-initialize shared_info if guest (32/64-bit) mode is set https://github.com/kvm-x86/linux/commit/21b99e4d6db6 [12/21] KVM: x86/xen: allow shared_info to be mapped by fixed HVA https://github.com/kvm-x86/linux/commit/10dcbfc46724 [13/21] KVM: x86/xen: allow vcpu_info to be mapped by fixed HVA https://github.com/kvm-x86/linux/commit/16877dd45f98 [14/21] KVM: selftests: map Xen's shared_info page using HVA rather than GFN https://github.com/kvm-x86/linux/commit/95c27ed8619b [15/21] KVM: selftests: re-map Xen's vcpu_info using HVA rather than GPA https://github.com/kvm-x86/linux/commit/5359bf19a3f0 [16/21] KVM: x86/xen: advertize the KVM_XEN_HVM_CONFIG_SHARED_INFO_HVA capability https://github.com/kvm-x86/linux/commit/49668ce7e1ae [17/21] KVM: x86/xen: split up kvm_xen_set_evtchn_fast() (not applied) [18/21] KVM: x86/xen: don't block on pfncache locks in kvm_xen_set_evtchn_fast() (not applied) [19/21] KVM: pfncache: check the need for invalidation under read lock first https://github.com/kvm-x86/linux/commit/21dadfcd665e [20/21] KVM: x86/xen: allow vcpu_info content to be 'safely' copied https://github.com/kvm-x86/linux/commit/dadeabc3b6fa [21/21] KVM: pfncache: rework __kvm_gpc_refresh() to fix locking issues (not applied) -- https://github.com/kvm-x86/linux/tree/next