From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A793CC433DF for ; Mon, 1 Jun 2020 13:29:43 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 714FB2077D for ; Mon, 1 Jun 2020 13:29:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=xen.org header.i=@xen.org header.b="n4Ozb6I2" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 714FB2077D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=xen.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jfkV6-0007xz-PG; Mon, 01 Jun 2020 13:29:12 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jfkV5-0007xq-7H for xen-devel@lists.xenproject.org; Mon, 01 Jun 2020 13:29:11 +0000 X-Inumbo-ID: e07b8f64-a40b-11ea-9dbe-bc764e2007e4 Received: from mail.xenproject.org (unknown [104.130.215.37]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id e07b8f64-a40b-11ea-9dbe-bc764e2007e4; Mon, 01 Jun 2020 13:29:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=GLHrgBGOFloKOwkupYiTD8oGR2dt6jDGmP+jyKOu7VY=; b=n4Ozb6I2PA7HX5cZtUfLvdvfeP LDL7tQPpyZvwraa+OtdCaLig1wMkbrkEubL4HcbU4om8lTGprhPz+wDZW/GJJucm133sovO953ZnD t827myyAAjqKBeDw/BoTSHqgbiPCPAKs2RUAhPimKjNapHffHWgJySGvsb1876Ox46EM=; Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jfkV4-0002Ah-Fe; Mon, 01 Jun 2020 13:29:10 +0000 Received: from [54.239.6.186] (helo=a483e7b01a66.ant.amazon.com) by xenbits.xenproject.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jfkV4-0003nL-93; Mon, 01 Jun 2020 13:29:10 +0000 Subject: Re: Keystone Issue To: CodeWiz2280 , xen-devel@lists.xenproject.org References: From: Julien Grall Message-ID: Date: Mon, 1 Jun 2020 14:29:08 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" Hello, I have a few questions in order to understand a bit more your problem. On 01/06/2020 13:38, CodeWiz2280 wrote: > Hello, I am using a Texas Instruments K2E Keystone Eval board with Linux > 4.19.59.  It has a 32-bit ARM Cortex A15 processor. There is keystone > specific code in the kernel in arch/arm/mm/pv-fixup-asm.s that executes > during early_paging_init for LPAE support.  This causes the kernel to > switch its running 32-bit address space to a 36-bit address space and > the hypervisor traps repeatedly and stops it from booting. Without any log it is going to be difficult to help. Could you post the hypervisor log when debug is enabled? >  I suspect > this is because Xen only allowed for the original 32-bit memory range > specified by the dom0 device tree. How much RAM did you give to your Dom0? > The 36-bit LPAE address is a fixed > offset from the 32-bit address and is not physically different memory. I am not sure to understand this. Are you suggesting that the kernel is trying to relocate itself in a different part of the physical memory? Can you provide more details on the fixed offset? > > Can you suggest any way to get through this problem? I am using the > master branch of xen from earlier this year. Can you provide the exact baseline your are using? Did make any changes on top? > Any help is greatly > appreciated. Best regards, -- Julien Grall