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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BC585ECAAD4 for ; Fri, 26 Aug 2022 12:00:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230307AbiHZMAc (ORCPT ); Fri, 26 Aug 2022 08:00:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49486 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245496AbiHZMA0 (ORCPT ); Fri, 26 Aug 2022 08:00:26 -0400 Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3DCB723BFE for ; Fri, 26 Aug 2022 05:00:25 -0700 (PDT) Received: by mail-ej1-x631.google.com with SMTP id cu2so2797815ejb.0 for ; Fri, 26 Aug 2022 05:00:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc; bh=MxGGd+3msz7Zn8awEDtaAUBprmyOYrYaH1QuR+N4/7o=; b=Gpo7N7AFg7ypzz4ziWV5/xqGFn6VPSfepZxdPxvYxjBT44+e2TYfUynhvuN4bgXRS/ Y1lMBDwSuSvsL4hGB4NVY0v3EWF3sT7n/bwVeuIOO0ODHJdT0/abtE6mRH2DymksTXXO r1ObcZJ+e7Ndu8lJcEp/bXAX2zEQ1GVh4vtmyJ2otqk5MeOeGigP0uXSnvUviUdyKMUb 9msUNjrYLw+GCjpRbA06oyQANC2DsCXnYbXtaRvOYkeCMk/UHYKt4JhjPsqcwksrWypU p8o94YuVPtobGYa1F4jwdkuKvP6bhOSsOcBBEtFTo7INwdfxMTydzpLeyUkWamzDAgnB 0w8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=MxGGd+3msz7Zn8awEDtaAUBprmyOYrYaH1QuR+N4/7o=; b=AuNabCvj97WT2kjGHECGKBRV5DZix7aAac2zJVyGR1AGB4uKIdJScjeyy2R75/JZ6d YI+a6G6IDNnyKqvjT78j4HhuDMT0prJ4Jj8wAq+GYoQiiKauUrwKmw/B9iS+9ipRW/am bpL9GTCI/+idDbunPIys6eF5intco6x+S01/JJsp4rjsWh/SCefvLxwtvJwa24AsOF4y jytEncr5VBfXG3QwG+KLDCegaJoZ8aRutXOZzGyQKp45/oPv+Tc4AEbg9HRTEG+e1iDy TO40hhxEJ5UY0KtBfBIB8VVeWgAdJZnsjn/GAo/XTPLcBgFbYe8jfX5f66/5XtnSZUXv NgBg== X-Gm-Message-State: ACgBeo1xcSFLtl5x7hJvoQxXssdpSsyUJMSkYbN4Bua0m0VQDCUMRGcD 46Oqcb9T+efk0WFHSA2iViLf9Q4XPG7Etg== X-Google-Smtp-Source: AA6agR6pWzpqNgeu5nYDI5mFIoqg2F0SdV1dhlacTRMXfwMX4RTLBi/UMn/Zte3pGXH6yssBl9NJZA== X-Received: by 2002:a17:907:6d2a:b0:73d:9ba5:633a with SMTP id sa42-20020a1709076d2a00b0073d9ba5633amr5386524ejc.201.1661515223724; Fri, 26 Aug 2022 05:00:23 -0700 (PDT) Received: from mutt (c-e429e555.07-21-73746f28.bbcust.telenor.se. [85.229.41.228]) by smtp.gmail.com with ESMTPSA id w20-20020a05640234d400b00447c2c1b9a0sm1164957edc.91.2022.08.26.05.00.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Aug 2022 05:00:22 -0700 (PDT) Date: Fri, 26 Aug 2022 14:00:20 +0200 From: Anders Roxell To: Anshuman Khandual Cc: linux-arm-kernel@lists.infradead.org, James Morse , Catalin Marinas , Will Deacon , Marc Zyngier , Suzuki K Poulose , Ard Biesheuvel , Mark Rutland , kvmarm@lists.cs.columbia.edu, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, alex.bennee@linaro.org, arnd@arndb.de Subject: Re: [PATCH V2] arm64/mm: Fix __enable_mmu() for new TGRAN range values Message-ID: <20220826120020.GB520@mutt> References: <1615355590-21102-1-git-send-email-anshuman.khandual@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1615355590-21102-1-git-send-email-anshuman.khandual@arm.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021-03-10 11:23, Anshuman Khandual wrote: > From: James Morse > > As per ARM ARM DDI 0487G.a, when FEAT_LPA2 is implemented, ID_AA64MMFR0_EL1 > might contain a range of values to describe supported translation granules > (4K and 16K pages sizes in particular) instead of just enabled or disabled > values. This changes __enable_mmu() function to handle complete acceptable > range of values (depending on whether the field is signed or unsigned) now > represented with ID_AA64MMFR0_TGRAN_SUPPORTED_[MIN..MAX] pair. While here, > also fix similar situations in EFI stub and KVM as well. > > Cc: Catalin Marinas > Cc: Will Deacon > Cc: Marc Zyngier > Cc: James Morse > Cc: Suzuki K Poulose > Cc: Ard Biesheuvel > Cc: Mark Rutland > Cc: linux-arm-kernel@lists.infradead.org > Cc: kvmarm@lists.cs.columbia.edu > Cc: linux-efi@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Acked-by: Marc Zyngier > Signed-off-by: James Morse > Signed-off-by: Anshuman Khandual Hi, When building an arm64 defconfig kernel from stable/linux-5.10.y and booting that in QEMU (version: 1:7.0+dfsg-2~bpo11+2) with '-cpu max' the kernel doesn't boot. I don't get any output. The kernel boots fine if I change to '-cpu cortex-a72'. If I cherry-pick this patch to stable/linux-5.10.y I'm able too boot the kernel with '-cpu max'. However, I'm not comfortable to backport this patch to older kernels since there are a lot of conflicts. Can someone help out to do the packport? Cheers, Anders