Re: [GIT PULL 0/6] KVM: s390: Fixes and features for 4.16

Radim Krčmář
2018-01-16T15:27:24Z

2018-01-16 16:14+0100, Christian Borntraeger:
> On 01/16/2018 04:09 PM, Paolo Bonzini wrote:
> > On 16/01/2018 16:03, Christian Borntraeger wrote:
> >> Paolo, Radim,
> >>
> >> the first chunk (of already reviewed) patches for 4.16 via kvm/next.
> >>
> >>
> >> The following changes since commit ccff53fd86ee54022e3d841f3db9280b1deb22e4:
> >>
> >> KVM: x86: avoid unnecessary XSETBV on guest entry (2017-12-18 13:10:25 +0100)
> >>
> >> are available in the git repository at:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-4.16-1
> >>
> >> for you to fetch changes up to 715e0427049606f499ea6b485c997f93f0778c77:
> >>
> >> KVM: s390: cleanup struct kvm_s390_float_interrupt (2018-01-16 15:53:09 +0100)
> >>
> >> ----------------------------------------------------------------
> >> KVM: s390: Fixes and features for 4.16
> >>
> >> - add the virtio-ccw transport for kvmconfig
> >> - more debug tracing for cpu model
> >> - cleanups and fixes
> >>
> >> ----------------------------------------------------------------
> >> Christian Borntraeger (3):
> >> KVM: s390: use created_vcpus in more places
> >> KVM: s390: add debug tracing for cpu features of CPU model
> >> kvm_config: add CONFIG_S390_GUEST
> >>
> >> David Hildenbrand (2):
> >> s390x/mm: cleanup gmap_pte_op_walk()
> >> KVM: s390: cleanup struct kvm_s390_float_interrupt
> >>
> >> Michael Mueller (1):
> >> KVM: s390: drop use of spin lock in __floating_irq_kick
> >>
> >> arch/s390/include/asm/kvm_host.h | 3 ---
> >> arch/s390/kvm/interrupt.c | 27 +++++++++++----------------
> >> arch/s390/kvm/kvm-s390.c | 29 +++++++++++++++++++----------
> >> arch/s390/kvm/kvm-s390.h | 2 +-
> >> arch/s390/kvm/sigp.c | 12 ++++--------
> >> arch/s390/mm/gmap.c | 23 ++++++++---------------
> >> kernel/configs/kvm_guest.config | 1 +
> >> 7 files changed, 44 insertions(+), 53 deletions(-)
> >>
> >
> > We probably will have to rebase kvm/next, sorry, to remove a series that
> > had problems and (worse) complaints from the arch/x86 maintainers. :(
> > Can you rebase on top of 5cb0944c0c66004c0d9006a7f0fba5782ae38
>
> Can you (when doing that) rebase on something newer? rc3 is broken in many ways
> and only works on some of my test systems (those without multipath).

I'd like to avoid rebasing that much -- so far we're only rebasing
patches since Jan 11 and there is a batch from Dec 14 on top of rc3.

> I will rebase on 4.15-rc3 to give you all the freedom you need.

I think that basing s390 on a later -rc would work for all of us,

thanks.