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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 56D6EC6778C for ; Thu, 5 Jul 2018 07:58:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0A2A422562 for ; Thu, 5 Jul 2018 07:58:59 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0A2A422562 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753418AbeGEH64 (ORCPT ); Thu, 5 Jul 2018 03:58:56 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:50370 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753041AbeGEH6y (ORCPT ); Thu, 5 Jul 2018 03:58:54 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1A41687A84; Thu, 5 Jul 2018 07:58:54 +0000 (UTC) Received: from localhost.localdomain (ovpn-116-118.ams2.redhat.com [10.36.116.118]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 41213111DD02; Thu, 5 Jul 2018 07:58:52 +0000 (UTC) Subject: Re: [kvmtool test PATCH 24/24] kvmtool: arm: Add support for creating VM with PA size To: Peter Maydell , Will Deacon References: <1530270944-11351-1-git-send-email-suzuki.poulose@arm.com> <1530270944-11351-25-git-send-email-suzuki.poulose@arm.com> <20180704142241.GG4828@arm.com> <8636wzysfl.wl-marc.zyngier@arm.com> <20180704155123.GO4828@arm.com> Cc: Christoffer Dall , kvm-devel , Marc Zyngier , Catalin Marinas , Punit Agrawal , lkml - Kernel Mailing List , QEMU Developers , kvmarm@lists.cs.columbia.edu, arm-mail-list From: Auger Eric Message-ID: Date: Thu, 5 Jul 2018 09:58:50 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Thu, 05 Jul 2018 07:58:54 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Thu, 05 Jul 2018 07:58:54 +0000 (UTC) for IP:'10.11.54.3' DOMAIN:'int-mx03.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'eric.auger@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 07/05/2018 09:51 AM, Peter Maydell wrote: > On 4 July 2018 at 16:51, Will Deacon wrote: >> On Wed, Jul 04, 2018 at 03:41:18PM +0100, Marc Zyngier wrote: >>> Not really. Let's say I want my IPA space split in two: memory covers >>> the low 47 bit, and I want MMIO spanning the top 47 bit. With your >>> scheme, you'd end-up with a 47bit IPA space, while you really want 48 >>> bits (MMIO space implemented by userspace isn't registered to the >>> kernel). >> >> That still sounds quite niche for a VM. Does QEMU do that? > > Not at 47 bits, but we have RAM up to the 256GB mark, and > MMIO above that (including a large PCI window), so the general > arrangement of having the top end of the IPA space not > necessarily be things we've told the kernel about definitely > exists. Is this document (2012) still a reference document? http://infocenter.arm.com/help/topic/com.arm.doc.den0001c/DEN0001C_principles_of_arm_memory_maps.pdf (especially Fig 5?) Peter, comments in QEMU hw/arm/virt.c suggested next RAM chunk should be added at 2TB. This doc suggests to put it at 8TB. I understand the PA memory map only is suggested but shouldn't we align? Thanks Eric > > thanks > -- PMM > _______________________________________________ > kvmarm mailing list > kvmarm@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/kvmarm > From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57864) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fazAJ-0005ka-NZ for qemu-devel@nongnu.org; Thu, 05 Jul 2018 03:59:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fazAF-0004CC-En for qemu-devel@nongnu.org; Thu, 05 Jul 2018 03:58:59 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:35710 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fazAF-00048X-90 for qemu-devel@nongnu.org; Thu, 05 Jul 2018 03:58:55 -0400 References: <1530270944-11351-1-git-send-email-suzuki.poulose@arm.com> <1530270944-11351-25-git-send-email-suzuki.poulose@arm.com> <20180704142241.GG4828@arm.com> <8636wzysfl.wl-marc.zyngier@arm.com> <20180704155123.GO4828@arm.com> From: Auger Eric Message-ID: Date: Thu, 5 Jul 2018 09:58:50 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [kvmtool test PATCH 24/24] kvmtool: arm: Add support for creating VM with PA size List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Will Deacon Cc: Christoffer Dall , kvm-devel , Marc Zyngier , Catalin Marinas , Punit Agrawal , lkml - Kernel Mailing List , QEMU Developers , kvmarm@lists.cs.columbia.edu, arm-mail-list Hi, On 07/05/2018 09:51 AM, Peter Maydell wrote: > On 4 July 2018 at 16:51, Will Deacon wrote: >> On Wed, Jul 04, 2018 at 03:41:18PM +0100, Marc Zyngier wrote: >>> Not really. Let's say I want my IPA space split in two: memory covers >>> the low 47 bit, and I want MMIO spanning the top 47 bit. With your >>> scheme, you'd end-up with a 47bit IPA space, while you really want 48 >>> bits (MMIO space implemented by userspace isn't registered to the >>> kernel). >> >> That still sounds quite niche for a VM. Does QEMU do that? > > Not at 47 bits, but we have RAM up to the 256GB mark, and > MMIO above that (including a large PCI window), so the general > arrangement of having the top end of the IPA space not > necessarily be things we've told the kernel about definitely > exists. Is this document (2012) still a reference document? http://infocenter.arm.com/help/topic/com.arm.doc.den0001c/DEN0001C_principles_of_arm_memory_maps.pdf (especially Fig 5?) Peter, comments in QEMU hw/arm/virt.c suggested next RAM chunk should be added at 2TB. This doc suggests to put it at 8TB. I understand the PA memory map only is suggested but shouldn't we align? Thanks Eric > > thanks > -- PMM > _______________________________________________ > kvmarm mailing list > kvmarm@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/kvmarm > From mboxrd@z Thu Jan 1 00:00:00 1970 From: eric.auger@redhat.com (Auger Eric) Date: Thu, 5 Jul 2018 09:58:50 +0200 Subject: [kvmtool test PATCH 24/24] kvmtool: arm: Add support for creating VM with PA size In-Reply-To: References: <1530270944-11351-1-git-send-email-suzuki.poulose@arm.com> <1530270944-11351-25-git-send-email-suzuki.poulose@arm.com> <20180704142241.GG4828@arm.com> <8636wzysfl.wl-marc.zyngier@arm.com> <20180704155123.GO4828@arm.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, On 07/05/2018 09:51 AM, Peter Maydell wrote: > On 4 July 2018 at 16:51, Will Deacon wrote: >> On Wed, Jul 04, 2018 at 03:41:18PM +0100, Marc Zyngier wrote: >>> Not really. Let's say I want my IPA space split in two: memory covers >>> the low 47 bit, and I want MMIO spanning the top 47 bit. With your >>> scheme, you'd end-up with a 47bit IPA space, while you really want 48 >>> bits (MMIO space implemented by userspace isn't registered to the >>> kernel). >> >> That still sounds quite niche for a VM. Does QEMU do that? > > Not at 47 bits, but we have RAM up to the 256GB mark, and > MMIO above that (including a large PCI window), so the general > arrangement of having the top end of the IPA space not > necessarily be things we've told the kernel about definitely > exists. Is this document (2012) still a reference document? http://infocenter.arm.com/help/topic/com.arm.doc.den0001c/DEN0001C_principles_of_arm_memory_maps.pdf (especially Fig 5?) Peter, comments in QEMU hw/arm/virt.c suggested next RAM chunk should be added at 2TB. This doc suggests to put it at 8TB. I understand the PA memory map only is suggested but shouldn't we align? Thanks Eric > > thanks > -- PMM > _______________________________________________ > kvmarm mailing list > kvmarm at lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/kvmarm >