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=-14.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1,USER_IN_DEF_DKIM_WL 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 F342DC433DB for ; Fri, 19 Mar 2021 15:03:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C64A86191A for ; Fri, 19 Mar 2021 15:03:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231168AbhCSPDW (ORCPT ); Fri, 19 Mar 2021 11:03:22 -0400 Received: from linux.microsoft.com ([13.77.154.182]:46116 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231136AbhCSPCy (ORCPT ); Fri, 19 Mar 2021 11:02:54 -0400 Received: from [192.168.254.32] (unknown [47.187.194.202]) by linux.microsoft.com (Postfix) with ESMTPSA id BB0C520B3754; Fri, 19 Mar 2021 08:02:53 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com BB0C520B3754 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1616166174; bh=Zt/90atLLHUzYhfmjFjtxdJCiAuaf3iXLSZvdUpTUSU=; h=Subject:From:To:Cc:References:Date:In-Reply-To:From; b=JCKaCL6Cc0K17Rj0DZPEAImdGv8luXbG5TOtJ5OmZmUjPYu3hE/ycUh8b4PopBFZy 0Z9ayWl2OLdVpi25bXnuNnXJ+vsnQOCIUwv64zmcpQtZKkRIfTVOJ5lNZlo1PndaKg QlMxLETG8XOjSUMMrq1RHMLKF1ZjvkizjuryVWts= Subject: Re: [RFC PATCH v2 2/8] arm64: Implement frame types From: "Madhavan T. Venkataraman" To: Mark Brown Cc: mark.rutland@arm.com, jpoimboe@redhat.com, jthierry@redhat.com, catalin.marinas@arm.com, will@kernel.org, linux-arm-kernel@lists.infradead.org, live-patching@vger.kernel.org, linux-kernel@vger.kernel.org References: <5997dfe8d261a3a543667b83c902883c1e4bd270> <20210315165800.5948-1-madvenka@linux.microsoft.com> <20210315165800.5948-3-madvenka@linux.microsoft.com> <20210318174029.GM5469@sirena.org.uk> <6474b609-b624-f439-7bf7-61ce78ff7b83@linux.microsoft.com> <20210319132208.GD5619@sirena.org.uk> Message-ID: Date: Fri, 19 Mar 2021 10:02:52 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/19/21 9:40 AM, Madhavan T. Venkataraman wrote: >> Are you referring to ARMv8.1 VHE extension where the kernel can run >> at EL2? Could you elaborate? I thought that EL2 was basically for >> Hypervisors. > KVM is the main case, yes - IIRC otherwise it's mainly error handlers > but I might be missing something. We do recommend that the kernel is > started at EL2 where possible. > > Actually now I look again it's just not adding anything on EL2 entries > at all, they use a separate set of macros which aren't updated - this > will only update things for EL0 and EL1 entries so my comment above > about this tracking EL2 as EL1 isn't accurate. So, do I need to do anything here? Madhavan