From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Zyngier Subject: Re: [GIT PULL 1/2] KVM: s390: allow user space to handle instr 0x0000 Date: Wed, 20 Jul 2016 18:47:22 +0100 Message-ID: <578FB92A.5030806@arm.com> References: <1469018400-8397-1-git-send-email-borntraeger@de.ibm.com> <1469018400-8397-2-git-send-email-borntraeger@de.ibm.com> <578F8C45.6060505@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Cc: KVM , Cornelia Huck , linux-s390 , David Hildenbrand , cdall@cs.columbia.edu To: Christian Borntraeger , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= Return-path: Received: from foss.arm.com ([217.140.101.70]:43987 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753575AbcGTRrZ (ORCPT ); Wed, 20 Jul 2016 13:47:25 -0400 In-Reply-To: <578F8C45.6060505@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 20/07/16 15:35, Christian Borntraeger wrote: > Marc, Christoffer, > FYI/FYA > the CAP number will conflict with your kvmarm changes. > I assume Paolo/Radim will resolve this when merging. Yea, that's usually the case. > Seems that you have no hit in api.txt, correct? There is a small update for the KVM_CAP_SIGNAL_MSI API, but we don't seem to step on each other's toes over there. Thanks for the heads up! M. -- Jazz is not dead. It just smells funny...