From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 066332DEA78 for ; Mon, 5 Jan 2026 17:20:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767633638; cv=none; b=SAWS087w+o5M1MR1PYTFAJ1PYwrlxCzD/7iBas2JIQikkKdoq2WsKtnGXy1oirF95yAk/vyGpTCEv8uSmIrJd/AJkr5HbQRkfrYLG6mdh2czVMog8x+02ZWVO5cRfNB3Q5MFzpodGNOe6RNJXjYGBGkXhWQ0X5071VeeV9d6Vwo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767633638; c=relaxed/simple; bh=z+mJFIx7PjVsDxzr7dSrZjCHr7bhdRcXtav9a6mlQEk=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=Rzq03VcU3gIOO9bNHs98lkHzq/RftEzmNBea+SUdd4jeFcbjuidAgS/Va52FxwkNswRWLAZY7x0qC3HCX2akTrVIRFaLO6rTE/LNganvAtQ40Z04dNoesv6d6v4tQqkLI2SJvGyF/Rnq6xbIk1bcmaKjv5j4Vgl/RUTH17Q1I9k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.224.107]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4dlLfQ55VmzJ467K; Tue, 6 Jan 2026 01:20:30 +0800 (CST) Received: from dubpeml100005.china.huawei.com (unknown [7.214.146.113]) by mail.maildlp.com (Postfix) with ESMTPS id EAC694057E; Tue, 6 Jan 2026 01:20:30 +0800 (CST) Received: from localhost (10.126.174.38) by dubpeml100005.china.huawei.com (7.214.146.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Mon, 5 Jan 2026 17:20:29 +0000 Date: Mon, 5 Jan 2026 17:20:27 +0000 From: Jonathan Cameron To: Ben Horgan CC: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v2 11/45] arm64: mpam: Initialise and context switch the MPAMSM_EL1 register Message-ID: <20260105172027.0000113c@huawei.com> In-Reply-To: <20251219181147.3404071-12-ben.horgan@arm.com> References: <20251219181147.3404071-1-ben.horgan@arm.com> <20251219181147.3404071-12-ben.horgan@arm.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: lhrpeml500012.china.huawei.com (7.191.174.4) To dubpeml100005.china.huawei.com (7.214.146.113) On Fri, 19 Dec 2025 18:11:13 +0000 Ben Horgan wrote: > The MPAMSM_EL1 sets the MPAM labels, PMG and PARTID, for loads and stores > generated by a shared SMCU. Disable the traps so the kernel can use it and > set it to the same configuration as the per-EL cpu MPAM configuration. > > If an SMCU is not shared with other cpus then it is implementation defined > whether the configuration from MPAMSM_EL1 is used or that from the > appropriate MPAMy_ELx. As we set the same configuration for MPAM0_EL1, > MPAM1_EL1 and MPAMSM_EL1 the resulting configuration is the same > regardless. Maybe tighten that last sentence up to talk about the matching fields rather than the 'same configuration'. Whole bunch of stuff in the first two that aren't in MPAMSM_EL1. > > Signed-off-by: Ben Horgan LGTM Reviewed-by: Jonathan Cameron