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 CA22D1DA60D for ; Mon, 22 Jun 2026 08:42:42 +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=1782117763; cv=none; b=HLlv0xn7VBP5oEPSpvD2JTfR0f/HB08y0V2x1FuUHbCNouBlGXtv7Nes4Gj7tRocoUXOCtXqXnzw6P4pc3z3Zlpp8sw3wUV78NIdjWEwfbEB5Fy0VZPOuwfX7ukbqaMYG+0aa7z2as4N9MklN3QX7/7T+qRILByq8n1Y24ZXfio= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782117763; c=relaxed/simple; bh=Gj4wZXQ9Q4crtAmgeE6t1cst/ii856yfRlMTBEvHKX0=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=LG7d+ed8q9e+K4HlY0sDdE0kxZsUkdeV0CwFrPSa59DIUn0rVuMLhb1XFUr44Nceu37al4zWli2uLP4slcpujk/4Aqr9pNzRaPjwtz5pZR7eM4IcDvdE35ye+ZtDUodJyRW5aIM8AtXYj0QX1ygayvMjakniw32IAav3y8QBpgU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=AAPeRVdP; 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="AAPeRVdP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 79ECC1F000E9; Mon, 22 Jun 2026 08:42:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782117762; bh=8DNrJ7xrGazJwS5U3+QWziCoPvFQKYCKjWzIcNy6Wpo=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=AAPeRVdPMJIf9riv+F4PdXeab4TQzM9brLBftORBtbetVeCJdXJ96FZRbVX5XrbQD I7wFWAh5tByuXcvuRYoC4+lm8QQQgEFG/A4Py2EaN0wgI/Dm0mELcNUB0Me3Mfhyha QRfQcA9xmPUBjCgmC4TGSISEUwmCwFH4GzNRDwIaATJI5h/EBwRcfBHpnmffF4IC8X TFU2U//HHttlP1e+wu0nqDaPuryNRicXiHH4dkBKTlr/xMgaZQTXXnOjsNCMENW0tt RufyZx3G6LCId3fnxqHph2ekmK9ya+3wuZ5qVdy7a6hIPDcaLzvSICatq/pRZJMNgy jNWek66CGZV7g== Date: Mon, 22 Jun 2026 09:42:33 +0100 From: Jonathan Cameron To: Mauro Carvalho Chehab Cc: uswg@uefi.org, taoxiaofei@huawei.com, Mauro Carvalho Chehab , linux-acpi@vger.kernel.org, qemu-arm@nongnu.org, Dong Wei , Samer El-Haj-Mahmoud , Jose Marinho , wanghuiqiang@huawei.com Subject: Re: [RESEND] troubles with ARM processor type changes on UEFI 2.11 Message-ID: <20260622094233.1088c8bf@jic23-huawei> In-Reply-To: <20260622102518.0ad0e4de@foz.lan> References: <20260622102518.0ad0e4de@foz.lan> X-Mailer: Claws Mail 4.4.0 (GTK 3.24.52; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-acpi@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 22 Jun 2026 10:25:18 +0200 Mauro Carvalho Chehab wrote: > (as I got no answer, I'm resending it, c/c some ARM people as well) > > Hi, > > I maintain ACPI HEST support on QEMU and I'm one of the Linux kernel reviewers > for the RAS subsystem. I'm also the author and maintainer of Linux rasdaemon, > responsible to handle RAS reports (including from GHES) on Linux. > > There is an incompatible change at UEFI 2.11 spec at Section N.2.4.4.1, > which, according with UEFI 2.11 changelog, it is related to this issue: > > 2462 - Fix the Type mnemonic description in the ARM Processor Error Information Structure > > This is the second time the specs changed the meaning of the type field > inside the ARM processor error info: > > - Before UEFI 2.9A, the spec has a list of values for error type. > From the specs, type, at offset 4 was described as: > > - Cache error > - TLB Error > - Bus Error > - Micro-architectural Error > All other values are reserved > > Yet, there was no information about how this would be encoded. > > - UEFI 2.9A defined the actual expected values as: > > - Bit 1 - Cache Error > - Bit 2 - TLB Error > - Bit 3 - Bus Error > - Bit 4 - Micro-architectural Error > All other values are reserved > > However, even being an incompatible change, the spec didn't change > version field at Section N.2.4.4.1. > > Linux, QEMU, rasdaemon and likely several BIOS implementations > were updated accordingly. > > - UEFI 2.11 changed the definition to: > > - Bit 0 - Cache Error > - Bit 1 - TLB Error > - Bit 2 - Bus Error > - Bit 3 - Micro-architectural Error > All other values are reserved > > Again, another incompatible change and without changing the version > field at Section N.2.4.4.1. > > With the current mess, it is impossible for the OSPM (and RAS apps) to > properly map ARM processor error types, as for instance, type=2 can > mean: > > - Bus error (up to UEFI 2.9) > - Cache error (UEFI 2.9A and UEFI 2.10) > - TLB error (UEFI 2.11) > > Please issue an errata incrementing version number, to allow OSPM > QEMU and rasdaemon to properly interpret this field. > FWIW I fully agree that an errata is needed. (Though, even though ambiguous, changing meaning should probably have been done by deprecating that field and adding a new one... too late now!) It seems a bit odd to do it this way but Mauro, you should be able to file a code first proposal at: https://github.com/tianocore/edk2/issues?q=is%3Aissue%20state%3Aopen%20label%3Atype%3Acode-first Make sure it has a code first label. I think you also need someone to take it through the committee though (I'm sadly not in a position to do so at the moment). Samer or Jose (+CC), can you deal with this one? Thanks, Jonathan > Thanks, > Mauro