From patchwork Fri May 30 12:47:01 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alexander Graf X-Patchwork-Id: 354169 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id C2C341400E5 for ; Fri, 30 May 2014 22:47:06 +1000 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752666AbaE3MrF (ORCPT ); Fri, 30 May 2014 08:47:05 -0400 Received: from cantor2.suse.de ([195.135.220.15]:34485 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751753AbaE3MrE (ORCPT ); Fri, 30 May 2014 08:47:04 -0400 Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 06285AC3C; Fri, 30 May 2014 12:47:03 +0000 (UTC) Message-ID: <53887DC5.9080908@suse.de> Date: Fri, 30 May 2014 14:47:01 +0200 From: Alexander Graf User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Christian Zigotzky , "kvm-ppc@vger.kernel.org" Subject: Re: Does KVM support the P.A. Semi PA6T cpu? References: <53511C7B.5010208@xenosoft.de> <017C4A38-BB7D-4BCA-B608-9B2966179689@suse.de> <5351A2C9.2000807@xenosoft.de> <5351AB33.5070207@suse.de> <535260BB.8050505@xenosoft.de> <53526DB3.4010200@xenosoft.de> <53529163.6000903@xenosoft.de> <5352D508.90105@xenosoft.de> <53553D16.6040104@xenosoft.de> <535C2F24.3080907@xenosoft.de> <535D4139.6030405@xenosoft.de> <535D42C8.7000207@suse.de> <535E637B.8080706@xenosoft.de> <535F6D63.4020607@suse.de> <5387C7C4.1000105@xenosoft.de> <53883819.1000107@suse.de> <53886E01.5070402@xenosoft.de> <538877B5.2060107@suse.de> <53887C9A.7070108@xenosoft.de> In-Reply-To: <53887C9A.7070108@xenosoft.de> Sender: kvm-ppc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm-ppc@vger.kernel.org On 30.05.14 14:42, Christian Zigotzky wrote: > Am 30.05.14 14:21, schrieb Alexander Graf: >> >> On 30.05.14 13:39, Christian Zigotzky wrote: >>> Hi Alex, >>> >>> Thank you for your answer. Here are the traces: >>> >>> http://www.xenosoft.de/trace_mol_mac_os_x_tiger.txt.tar.gz >>> http://www.xenosoft.de/trace_mol_mac_os_x_jaguar.txt.tar.gz >> >> Looking at the Jaguar log, the guest seems to be stuck trying to map >> a page: >> >> mol-4087 [001] .... 252.368002: kvm_exit: >> exit=DATA_STORAGE | pc=0x900074c4 | msr=0x4000d030 | dar=0xa000a434 | >> srr1=0x100000000000d032 | last_inst=0x912b0 >> 000 >> >> If you look at the trace, you will see that this PC with the exact >> same DAR happens over and over again - every time the guest thinks >> it's mapped the page. >> >> I don't know why that's happening. Try to enable the debug prints (or >> convert them to trace points ;)) in the book3s_32 guest and book3s_64 >> host emulation. Maybe that tells us something. >> >> >> Alex > Thanks Alex for your effort. How can I enable the debug prints? This should do the trick. Output will be in dmesg: There's also always the chance that split real mode is the real culprit for breakage here. Have you verified that the same kernel source (KVM code) works on a PPC32 host with MOL? Alex --- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/arch/powerpc/kvm/book3s_32_mmu.c b/arch/powerpc/kvm/book3s_32_mmu.c index 93503bb..939b14f 100644 --- a/arch/powerpc/kvm/book3s_32_mmu.c +++ b/arch/powerpc/kvm/book3s_32_mmu.c @@ -27,8 +27,8 @@ #include #include -/* #define DEBUG_MMU */ -/* #define DEBUG_MMU_PTE */ +#define DEBUG_MMU +#define DEBUG_MMU_PTE /* #define DEBUG_MMU_PTE_IP 0xfff14c40 */ #ifdef DEBUG_MMU