Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp908016imm; Wed, 4 Jul 2018 08:01:11 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfkKAPkSXc1YMtwBov9c6z42yKFQ1iqu5/i1C1iu6yMid/iuMCnlp4Dbc6Zh/5C/9v+8IQu X-Received: by 2002:a65:4849:: with SMTP id i9-v6mr2237804pgs.350.1530716471275; Wed, 04 Jul 2018 08:01:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530716471; cv=none; d=google.com; s=arc-20160816; b=STP2RVNdEkIOsMGqnOqaHEkB8UkbOpJkNxk7xzEZFxX7dBGoosaf6rDMSeDY+Dn7E4 M3zgHo2YXgBogq6w4kg2vsIY6SEWt8YuBIXjw/2LbTYLVBcs1GDzg8f2cR6VWkXkqpA1 52XwRYzJHoHq211yko+AnBfNs10jvDanQn/67fjJGXgdhgxfpXE3TlLLPWe1dhYNZuU3 DeHYunVMr/Cq9pBcd1yQ005xDqG1QbZdjgnCEqCLxw2PUcke/5QqeF1SzCGOFUyyX/NQ IdcpKoq23jDe6mfwwIDrdzM14dV4+w919kNfjc4XwTYN7O/HlfiDLb435QgJh8A/CwzF XWLg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=pJfYBjvHn5DEmkyOswZQi4xNj6xRWbwCc9lUtXTMwz4=; b=yehkbQ/HnnT1RTGXgIhYzIz5mTR+zpGhTVv4unqGYbbjRZqARLUu6BEGeBMUHdngM2 QRPBQvAEXw9bdUwJxDdUmVgIyTL+9iYJIsxjVWQmFai9pw/X+DIO7obFnlruS+DE97As 47KSVXdZJm+Ez6yp9KijpPikmg2McGg+EWNcO0XmHMWlwHSsI+CdFNKGvB4TSG1ft55U CkpDnOg/yZPsfj+BB3qVH3F47XucjrexodkWFAY+vWzaj3CING8XjLGGs6XYyxBema6U 0LCy0IWckG4YtKL7kK6b/BuXTD+ezMUXDGxiP3SEKMiEHB5sSPTE1oqf5wU6/eYMVvM9 jxlQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b78-v6si4140878pfk.342.2018.07.04.08.00.56; Wed, 04 Jul 2018 08:01:11 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752511AbeGDPAQ (ORCPT + 99 others); Wed, 4 Jul 2018 11:00:16 -0400 Received: from foss.arm.com ([217.140.101.70]:38938 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752114AbeGDPAP (ORCPT ); Wed, 4 Jul 2018 11:00:15 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A8F8B18A; Wed, 4 Jul 2018 08:00:14 -0700 (PDT) Received: from [10.1.206.53] (e108454-lin.cambridge.arm.com [10.1.206.53]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 955463F5A0; Wed, 4 Jul 2018 08:00:12 -0700 (PDT) Subject: Re: [kvmtool test PATCH 22/24] kvmtool: arm64: Add support for guest physical address size To: Will Deacon , Suzuki K Poulose Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu, james.morse@arm.com, marc.zyngier@arm.com, cdall@kernel.org, eric.auger@redhat.com, catalin.marinas@arm.com, punit.agrawal@arm.com, qemu-devel@nongnu.org References: <1530270944-11351-1-git-send-email-suzuki.poulose@arm.com> <1530270944-11351-23-git-send-email-suzuki.poulose@arm.com> <20180704140943.GF4828@arm.com> From: Julien Grall Message-ID: <8c9bb3cd-f673-17f3-656f-66b7e14fc73c@arm.com> Date: Wed, 4 Jul 2018 16:00:11 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180704140943.GF4828@arm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 04/07/18 15:09, Will Deacon wrote: > On Fri, Jun 29, 2018 at 12:15:42PM +0100, Suzuki K Poulose wrote: >> Add an option to specify the physical address size used by this >> VM. >> >> Signed-off-by: Suzuki K Poulose >> --- >> arm/aarch64/include/kvm/kvm-config-arch.h | 5 ++++- >> arm/include/arm-common/kvm-config-arch.h | 1 + >> 2 files changed, 5 insertions(+), 1 deletion(-) >> >> diff --git a/arm/aarch64/include/kvm/kvm-config-arch.h b/arm/aarch64/include/kvm/kvm-config-arch.h >> index 04be43d..dabd22c 100644 >> --- a/arm/aarch64/include/kvm/kvm-config-arch.h >> +++ b/arm/aarch64/include/kvm/kvm-config-arch.h >> @@ -8,7 +8,10 @@ >> "Create PMUv3 device"), \ >> OPT_U64('\0', "kaslr-seed", &(cfg)->kaslr_seed, \ >> "Specify random seed for Kernel Address Space " \ >> - "Layout Randomization (KASLR)"), >> + "Layout Randomization (KASLR)"), \ >> + OPT_INTEGER('\0', "phys-shift", &(cfg)->phys_shift, \ >> + "Specify maximum physical address size (not " \ >> + "the amount of memory)"), > > Given that this is a shift value, I think the help message could be more > informative. Something like: > > "Specify maximum number of bits in a guest physical address" > > I think I'd actually leave out any mention of memory, because this does > actually have an effect on the amount of addressable memory in a way that I > don't think we want to describe in half of a usage message line :) Is there any particular reasons to expose this option to the user? I have recently sent a series to allow the user to specify the position of the RAM [1]. With that series in mind, I think the user would not really need to specify the maximum physical shift. Instead we could automatically find it. Cheers, [1] http://archive.armlinux.org.uk/lurker/message/20180510.140428.1c295b5b.en.html > > Will > -- Julien Grall