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 42C8A431A49 for ; Thu, 16 Jul 2026 16:48:15 +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=XZ/wly0YAlG9ac7CulrusP6q4E7DFmKt2vsbaVyxgvBLAdRHU0PrZtSquKl3Vx1KqQpAnzZ5QcjytkzFPQvUvjaz+eVHiTapdiAMPdvLSdZDw5Frl/QOBpOs8218LcLCOBx02OuCWeFsN3o3OLlf7z/b0/Hehf8ysuH44k2iR6g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784220506; c=relaxed/simple; bh=2wwxBv1iWZwHdi7x7bbbguuqo3owtNOO0Tg3LyvlJmk=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=dyqc44LdDh/8gdsXfx+Cq9pSfAroBZjad/bKvdiCM8hCh6U8wyJFjyMrKTOrvhgYJc/hwCmodqQulDdzkbZxV1WqixlmZJqzucKC8ZXDV9CA3n9ngan8mKMp8v0QoIx4FaudhPaiTKybX8YW7GNy8z/Ri3RPekNSbIr0u1AHHxo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ViWsLPL2; 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="ViWsLPL2" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 119C51F00A3D; Thu, 16 Jul 2026 16:48:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784220490; bh=ao3Os8JtzbF7f7/1BpjjC1xMw0gtVZj+GS1Rx2K1zgA=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=ViWsLPL2L52z1dRWFarT3WKwOmdLfcmjumsZrcTU6Y7mQm+T+bUqGdAuCrWJvh7Qd GrHnXyA5x6zeUnMHSelbd6ChDxPwHqtpRj01pW9yfSyRfe34/PNIQn1KzAv67vR3JU lJ2AvbihnqW5kcVPEEB+d34Ne0MWTdxZ7SJcT8u/7rRvJehdg4AiFwQGxqPfMlefMh CHhNo6M5PufoIqqSkpgvWwbXhCG7pOuMSztxpOPDDUXB+1IyUCTVGMDzHJyoKa7rEh 19iw6RsUoNLdkWGjlh91PrD7ks5HYgESM7rGlc/R4maw1UFr5/VD3EuGPqyAiRGUf4 jQxRC312NvcBg== From: Will Deacon To: Catalin Marinas , Mark Brown Cc: kernel-team@android.com, Will Deacon , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] arm64: mm: When logging data aborts only decode Xs when ISV=1 Date: Thu, 16 Jul 2026 17:47:57 +0100 Message-ID: <178421467427.63287.7221010122666741553.b4-ty@kernel.org> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260702-arm64-xs-decode-v1-1-64600f149969@kernel.org> References: <20260702-arm64-xs-decode-v1-1-64600f149969@kernel.org> 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 Thu, 02 Jul 2026 20:13:35 +0100, Mark Brown wrote: > When logging the decode of a data abort we currently unconditionally decode > and display Xs. Currently the only defined non-RES0 values for this field > are for cases where ISV=1, move the decode of Xs into our existing check > for ISV=1. This avoids potential confusion if some other use is assigned to > these bits for ISV=0 cases in future, or misleading someone into thinking > there is a meaningful value there with currently defined architecture. > > [...] Applied to arm64 (for-next/fixes), thanks! [1/1] arm64: mm: When logging data aborts only decode Xs when ISV=1 https://git.kernel.org/arm64/c/f797f51a185f Cheers, -- Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev