Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp2485376pxb; Mon, 11 Jan 2021 10:47:00 -0800 (PST) X-Google-Smtp-Source: ABdhPJw6KZ88ZVnQZxpZ/sZBZLH7VZuJkBEVbk5PuHqeeA0n4Vqo4y18UF37YXbU41eQzRyk+Qo2 X-Received: by 2002:a17:906:720e:: with SMTP id m14mr559209ejk.161.1610390820130; Mon, 11 Jan 2021 10:47:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610390820; cv=none; d=google.com; s=arc-20160816; b=g51trlWvd9wg1fY2rTv80mYwfuTm7x3sYPHy/HL62kt7ax592w6pCvqjrbofpbu/dS lamR7st6z0K7np7tUFaY+so0+yZz+jDdjaWTS6HgJu/C6g/UOl9Zj3TyXw0t9yU7XYVd I5kmG+O9IT0uwegorrp273rO+sepgOgMCnmbstDozVhhcoAMCTC5vIBrvOe54ZSRvZeX 14vF7VdIfTIpqgkNS6WTmWmOjg3+oXdOp8+VH5WNIFyVm6KXq9UjWD5fnpazeCrhEjPC Oo02r0/1orz+lXAHGy04lFErF97k0eCTF+TjAcukaJHlxVe3QDDRuoW9s5YQFbUUMwJd z99w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=qpE1eg/svYYtYTrA+LICp3C+xQ0XanaQJ3rstIVJLVM=; b=ivGymrJD86GXf4AMesqqiV7lHVl+KHG/mmvmRSWk7z8Lo5DwgtuLtOXkeih7g8VaXl vaoD7OiZZzW+mvSGW0T8E0HZWuXE8FhLWFYyagTOlm/J0EAjuNxRO4KC+Oh3sdmhLHnk 14kJ5UoEgFBsKJ/CgqpS2uQnvp1ESXfDND9i0+MmpdVXq/W/SGAlAnyeYghMLduGPtvt qEmUa0lGTQ0AQ2cozkHKEVg0I0dry/xanDNiKMOFAkH3fSRCbGNsI+ZS26oGYo2i6v7m 24xU4oHL23kAIANYo8NJZNpFJ6NvR8AuXzQu2xqJMwSUPkQCwMemQeWfQv5fJMJFYUID CxUg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f6si217552edm.128.2021.01.11.10.46.36; Mon, 11 Jan 2021 10:47:00 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390277AbhAKSml (ORCPT + 99 others); Mon, 11 Jan 2021 13:42:41 -0500 Received: from mail.kernel.org ([198.145.29.99]:41896 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726063AbhAKSml (ORCPT ); Mon, 11 Jan 2021 13:42:41 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 65CE22251F; Mon, 11 Jan 2021 18:41:57 +0000 (UTC) Date: Mon, 11 Jan 2021 18:41:54 +0000 From: Catalin Marinas To: Marc Zyngier Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org, Will Deacon , Mark Rutland , David Brazdil , Alexandru Elisei , Ard Biesheuvel , Jing Zhang , Ajay Patil , Prasad Sodagudi , Srinivas Ramana , James Morse , Julien Thierry , Suzuki K Poulose , kernel-team@android.com Subject: Re: [PATCH v3 09/21] arm64: cpufeature: Add global feature override facility Message-ID: <20210111184154.GC17941@gaia> References: <20210111132811.2455113-1-maz@kernel.org> <20210111132811.2455113-10-maz@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210111132811.2455113-10-maz@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Marc, On Mon, Jan 11, 2021 at 01:27:59PM +0000, Marc Zyngier wrote: > Add a facility to globally override a feature, no matter what > the HW says. Yes, this is dangerous. Yeah, it's dangerous. We can make it less so if we only allow safe values (e.g. lower if FTR_UNSIGNED). > diff --git a/arch/arm64/include/asm/cpufeature.h b/arch/arm64/include/asm/cpufeature.h > index 9a555809b89c..465d2cb63bfc 100644 > --- a/arch/arm64/include/asm/cpufeature.h > +++ b/arch/arm64/include/asm/cpufeature.h > @@ -75,6 +75,8 @@ struct arm64_ftr_reg { > u64 sys_val; > u64 user_val; > const struct arm64_ftr_bits *ftr_bits; > + u64 *override_val; > + u64 *override_mask; > }; At the arm64_ftr_reg level, we don't have any information about the safe values for a feature. Could we instead move this to arm64_ftr_bits? We probably only need a single field. When populating the feature values, we can make sure it doesn't go above the hardware one. I attempted a feature modification for MTE here, though I dropped the entire series in the meantime as we clarified the ARM ARM: https://lore.kernel.org/linux-arm-kernel/20200515171612.1020-24-catalin.marinas@arm.com/ Srinivas copied it in his patch (but forgot to give credit ;)): https://lore.kernel.org/linux-arm-msm/1610152163-16554-3-git-send-email-sramana@codeaurora.org/ The above adds a filter function but, instead, just use your mechanism in this series for idreg.feature setting via cmdline. The arm64_ftr_value() function extracts the hardware value and lowers it if a cmdline argument was passed. -- Catalin