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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D5838C433EF for ; Mon, 7 Mar 2022 17:14:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Vt+kseR9/UKpLZg1tm4Ad2RV+UdCXiA99x4yMFGG3jw=; b=j9GG1FKuyKUcRu 1Jk535vhnhCo1uRFcIqKOCEizkTzNj5KYFwkvcDWpYLLW7QX9iUqe6byLwHapHaw3nZFvAvaQl5il Mm/I7ZVZ+sxKqfPZlygsMBdpCLORnQGh598FjlGwDeP5S2GYHABTR9LWzZtztvIgugta6mt/d8Nlf 69k2AO4QnKvBNaSmZk1XhQZfTJ7KHJ9dUCenceilOudml5U7KIO7mNlDBUNbZ5iQlibk51b1ftdv5 +0ZG44j9KcGBkPojlXmob5xB1icGfGf3VBQZQM9XVNeDhxRqsaum/l/0Di7dbW3z9ejSey8j0qECw 7FTqIbVOpDWWj5L9Pu6A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nRGvJ-000zF8-N3; Mon, 07 Mar 2022 17:13:29 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nRGvF-000zEN-VF for linux-arm-kernel@lists.infradead.org; Mon, 07 Mar 2022 17:13:27 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A2F87153B; Mon, 7 Mar 2022 09:13:24 -0800 (PST) Received: from monolith.localdoman (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 585883FA45; Mon, 7 Mar 2022 09:13:21 -0800 (PST) Date: Mon, 7 Mar 2022 17:13:50 +0000 From: Alexandru Elisei To: Marc Zyngier Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, Andre Przywara , Christoffer Dall , Jintack Lim , Haibo Xu , Ganapatrao Kulkarni , Chase Conklin , "Russell King (Oracle)" , James Morse , Suzuki K Poulose , karl.heubaum@oracle.com, mihai.carabas@oracle.com, miguel.luis@oracle.com, kernel-team@android.com Subject: Re: [PATCH v6 43/64] KVM: arm64: nv: arch_timer: Support hyp timer emulation Message-ID: References: <20220128121912.509006-1-maz@kernel.org> <20220128121912.509006-44-maz@kernel.org> <8735jt1z9c.wl-maz@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <8735jt1z9c.wl-maz@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220307_091326_129214_FD8E45C3 X-CRM114-Status: GOOD ( 26.11 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi, On Mon, Mar 07, 2022 at 04:52:15PM +0000, Marc Zyngier wrote: > On Mon, 07 Mar 2022 16:28:44 +0000, > Alexandru Elisei wrote: > > > > Hi, > > > > On Mon, Mar 07, 2022 at 03:48:19PM +0000, Marc Zyngier wrote: > > > On 2022-03-07 14:52, Alexandru Elisei wrote: > > > > Hi, > > > > > > > > I was under the impression that KVM's nested virtualization doesn't > > > > support > > > > AArch32 in the guest, why is the subject about hyp mode aarch32 timers? > > > > > > Where did you see *ANY* mention of AArch32? > > > > I saw an implicit mention of aarch32 when the commit message used > > the term "hyp", which is the name of an aarch32 execution mode. > > > > > > > > Or is that a very roundabout way to object to the 'hyp' name? > > > > Bingo. > > > > > If that's the case, just apply a mental 's/hyp/el2/' substitution. > > > > I'm a bit confused about that. Is that something that anyone reading > > the patch should apply mentally when reading the patch, or is it > > something that you plan to change in the commit subject? > > Big picture: > > maz@hot-poop:~/arm-platforms$ git grep -i hyp arch/arm64/|wc -l > 1701 > maz@hot-poop:~/arm-platforms$ git grep -i el2 arch/arm64/|wc -l > 1008 > > Are we going to also repaint all these 'hyp' references? I didn't say, nor suggest that. I suggested that *this* commit could be changed to use the architectural terminology, which I assumed it's the most natural terminology to use in a patch series which has the goal to emulate the architectural EL2. Obviously, opinions vary. > > I really appreciate all the hard work you are putting in carefully > reviewing the code. I *really* do. But bickering on this really > doesn't help, and I know you understand exactly what this subject line > means (you've been reviewing KVM code for long enough, and won't fool > anyone). > > The point you are trying to make really is moot. Everybody understands > that HYP means EL2. I'd even argue that it is clearer than EL2, > because it indicates that we're running at EL2 with the role of a > hypervisor, which isn't that clear with running with VHE. So HYP means EL2 or EL2 with the role of a hypervisor? Because when booting KVM on a machine without FEAT_VHE, dmesg uses "hyp mode" to refer to EL2 without FEAT_VHE. And is_hyp_ctxt(), which this series adds, refers to EL0 with HCR_EL2.TGE set. I've given these examples before (and others), in the end it's up to you how precise you want the terminology to be and how easy to understand you want to make the code. Thanks, Alex _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel