From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 3829F42FCC8 for ; Thu, 16 Jul 2026 16:48:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784220506; cv=none; b=EP51x4hEuTGBxDy3yZ0Xb/EzMaqmLgeM0RtDr75hlY91VJBgWSZPszL7S0TDVC8SnKV/yIoaVw7Be1GbZbW5m6or3KAXTA5KuWvE14xHUcJ54dZqccBEelU+QRHtAeWC7Bz/E71Cc2EUbbTaLzIrndwvxQent7cmgoikP+91hDk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784220506; c=relaxed/simple; bh=z5U5KVclbTAJY5iciE+w0ir5UermokyBQOcjQ4wPU6s=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=gJaS7K0wmm/FLXNZYMDF2yq+YMkE0DaANF2/Pt5Rn3Wupw3qoJxAoSPDXHhfl8dIqr4ez7E9jzsFoE5NOrXGTPobqCsNr3GrHmXVcJuVSaK5ZX5bckm25qrs2jw6mjWtqSvXezmrem5pp1cOBmn9wdpGUJSB8xwsEDFDArmxADo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=AUJL2pls; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="AUJL2pls" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C743D1F00A3A; Thu, 16 Jul 2026 16:48:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784220488; bh=Xc5ThQMHryU1Ipvo5TSCt9FTpHI5kXdKxf3yESYTO2o=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=AUJL2plsSnlHVkA++gOsR70ld8MyFB3UQTvJnOGbD+pAnfn/LKL/BGQKeO9VsH1FL Nai2rgEJ8qbJnsKJOUHY0uYBCWvahhzgr88p8REL55Y0BtFvIXdwiunqIbRmCYymoD OLvOmb+OANCYVvMEeOcsFHPHUmAhmxuTTt5hbE+JU/IsB8BrnkH1fQoFKnmrA7/sBc ZMth56PfU2MAVo/hNc2n0/szTRewyoAsNYelxK0xDY0DGYadR0TnYYUYmEokkEMiAK 97mYF+q3Bes2nM4u6ZANDqsKSlJgclzkC+dKpXzl5QsmjopUTmvKYInGkWcQKob7Zp jjMouL/v3w9bg== From: Will Deacon To: Ben Horgan Cc: catalin.marinas@arm.com, kernel-team@android.com, Will Deacon , james.morse@arm.com, reinette.chatre@intel.com, fenghuay@nvidia.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] arm_mpam: Fix software reset values of MPAMCFG_PRI Date: Thu, 16 Jul 2026 17:47:56 +0100 Message-ID: <178420945293.36085.2697955489302440125.b4-ty@kernel.org> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260515085825.1157812-1-ben.horgan@arm.com> References: <20260515085825.1157812-1-ben.horgan@arm.com> 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="utf-8" Content-Transfer-Encoding: 8bit On Fri, 15 May 2026 09:58:25 +0100, Ben Horgan wrote: > Priority partitioning is not supported other than to set the per-PARTID > defaults in MPAMCFG_PRI, INTPRI and DSPRI, to the highest priority. When 0 > is the lowest priority, all ones is the highest priority. However, these > values are calculated with an extra higher bit set. > > Luckily, there is still no chance of setting functional bits incorrectly. > When the priority widths are maximal, this is ensured as the fields have > width 16 and a u16 holds the value for each field. When the widths are > smaller, the higher order bits beyond the advertised widths, > MPAMF_PRI_IDR.DSPRI_WD and MPAMF_PRI_IDR.INTPRI_WD, in the priority fields > INTPRI and DSPRI are not used to calculate the priority. It is not > specified whether these higher order bits are RAZ/WI or Res0 and so it is > desirable not to set them to avoid the chance of misleading reads. > > [...] Applied to arm64 (for-next/fixes), thanks! [1/1] arm_mpam: Fix software reset values of MPAMCFG_PRI https://git.kernel.org/arm64/c/9469764292e0 Cheers, -- Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev