From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59593) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c7TCn-0005fL-KF for qemu-devel@nongnu.org; Thu, 17 Nov 2016 15:22:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c7TCk-0006pa-FN for qemu-devel@nongnu.org; Thu, 17 Nov 2016 15:22:45 -0500 From: Laurent Vivier References: <1479285571-28145-1-git-send-email-thuth@redhat.com> <20161116131321.35d58700@bahia> <20161116122450.GC2050@work-vm> <20161116133756.76854958@bahia> <2f74eb45-b36d-3d4d-5b47-f06259ade5c4@redhat.com> <20161116151755.47c05cb7@bahia> Message-ID: <1b4598af-5109-b54e-7958-f8e9f346c1df@redhat.com> Date: Thu, 17 Nov 2016 21:22:33 +0100 MIME-Version: 1.0 In-Reply-To: <20161116151755.47c05cb7@bahia> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] tests/postcopy: Use KVM on ppc64 only if it is KVM-HV List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Greg Kurz , Thomas Huth Cc: "Dr. David Alan Gilbert" , David Gibson , qemu-ppc@nongnu.org, Stefan Hajnoczi , qemu-devel@nongnu.org, Andrea Arcangeli , Eric Blake On 16/11/2016 15:17, Greg Kurz wrote: > On Wed, 16 Nov 2016 14:17:47 +0100 > Thomas Huth wrote: > >> On 16.11.2016 13:37, Greg Kurz wrote: >>> On Wed, 16 Nov 2016 12:24:50 +0000 >>> "Dr. David Alan Gilbert" wrote: >>> >>>> * Greg Kurz (groug@kaod.org) wrote: >>>>> On Wed, 16 Nov 2016 09:39:31 +0100 >>>>> Thomas Huth wrote: >>>>> >>>>>> The ppc64 postcopy test does not work with KVM-PR, and it is also >>>>>> causing annoying warning messages when run on a x86 host. So let's >>>>>> use KVM here only if we know that we're running with KVM-HV (which >>>>>> automatically also means that we're running on a ppc64 host), and >>>>>> fall back to TCG otherwise. >>>>>> [..] > The changes to the code look ok and I prefer to spend time chasing the > KVM PR issue rather than arguing on a comment... For the problem itself, it seems to appear only after a BOOK3S_INTERRUPT_SYSCALL interrupt for an KVM_EXIT_PAPR_HCALL (H_PUT_TERM_CHAR). In this case, KVM has to exit to QEMU to manage the output. The following interrupt is always an BOOK3S_INTERRUPT_PROGRAM with an emulation failure. Laurent