From mboxrd@z Thu Jan 1 00:00:00 1970 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: [GIT PULL 5/9] KVM: s390: gs support for kvm guests Date: Tue, 11 Apr 2017 21:23:47 +0200 Message-ID: <20170411192346.GA32380@potion> References: <1491562082-6392-1-git-send-email-borntraeger@de.ibm.com> <1491562082-6392-6-git-send-email-borntraeger@de.ibm.com> <70b26028-8076-c7ff-be17-b99946a20642@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Hildenbrand , Paolo Bonzini , KVM , Cornelia Huck , linux-s390 , Fan Zhang To: Christian Borntraeger Return-path: Received: from mx1.redhat.com ([209.132.183.28]:40784 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753261AbdDKTXx (ORCPT ); Tue, 11 Apr 2017 15:23:53 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 2017-04-11 14:42+0200, Christian Borntraeger: > On 04/07/2017 02:01 PM, Christian Borntraeger wrote: > > > > Indeed this looks like a bug (and the right fix). > > > > This was not noticed during test since KVM enables the host management of > > registers and we do not use the sdnx. So for the KVM under KVM case this > > does not matter. Still, we should fix it. > > > > Radim, Paolo, do you want a respin of the whole series or can I simply send > > a fixup patch with the next round of patches? > > Radim, Paolo, > > is it ok to schedule the fixup patch for the next round of patches(I plan to > have some more for 4.12 anyway) and apply this series as is? I have not noticed the bottom hunk on Friday and waited before asking, sorry. Pulled now, the new capability numbers are #define KVM_CAP_S390_GS 140 #define KVM_CAP_S390_AIS 141 Thanks.