From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 34FBE30DECA for ; Wed, 17 Dec 2025 21:09:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766005776; cv=none; b=ImNizcYKGrDFmsv4Txdf0zXp4jTuspw6+0KudrbcroTuNMHi6Qj/3ZqalF8WXh6WLsT0zv8v21MihQiENWiKcAiTUuBDWQpfjwq9p1JnV4YA0Pvcg29T5FWSlHKAZCQGhQ6hPCm76NZ6adhdPfqCbOq6PKRz0oTIgSRcDDwmKFc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766005776; c=relaxed/simple; bh=WZl1V76oIj350IRmltdWQpn08Pw9yNxWNSMQU0y3n5Q=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=qHnV39sIituizN7YkwmJDYs3qNLuZNroahUsRhhE5SS554BtqTMPw5jtclop778glfIdQX/ka/Hm7ZnDoL7F58DGuXMpDJA0UuHGRsZmFg/G5HZY4LyWcV9KjIKmHzFkasBgYCLoKr5VRRYdCJxEQh4sPfVS5EnCIci9s4UR/o0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=AToMP9Pn; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="AToMP9Pn" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1FA49C4CEF5; Wed, 17 Dec 2025 21:09:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1766005775; bh=WZl1V76oIj350IRmltdWQpn08Pw9yNxWNSMQU0y3n5Q=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=AToMP9PnWMOJkOU/yHl8HGhqSUT1DY8nHLvRQxqHPIKxnyZOwZ3GFYL8ZUJy5HkKp +2eKvElai4D9EabsQI5xsoJA5PrOB1Hmu88wiURAJaARqG0CZNZtJSOy1sfpKtqcuQ FIVKQSRRseUNaSTZtyGMcKhU4k8VT+Q3lWxR3lpwd/87G+EQxS12aj1uDbPxgkOUmU OZHovIzYsNtby/0LZPOSjuzWgnBNG6axGXJna6zaXw5fCPy+Mk9tNUx248P/PmK/YF UZ4ceeFbJVxi1eREPD1jyDGvebNYIJEZA0gKqEAVuEpuEbmUrVoF9g+BmIzgS5RsvC iFKRPK59B0BDQ== Message-ID: <78dbc0eb-37a3-468d-b43e-f5a5a06ad8fe@kernel.org> Date: Wed, 17 Dec 2025 15:09:33 -0600 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 3/7] firmware: dmi: Read additional information when decoding DMI table To: Yazen Ghannam Cc: "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , Jean Delvare , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H . Peter Anvin" , linux-kernel@vger.kernel.org References: <20251216123354.9219-1-superm1@kernel.org> <20251216123354.9219-4-superm1@kernel.org> <20251217210352.GA1263950@yaz-khff2.amd.com> Content-Language: en-US From: Mario Limonciello In-Reply-To: <20251217210352.GA1263950@yaz-khff2.amd.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 12/17/25 3:03 PM, Yazen Ghannam wrote: > On Tue, Dec 16, 2025 at 06:33:50AM -0600, Mario Limonciello (AMD) wrote: >> Type 40 entries (Additional information) are summarized in section >> 7.41 as part of the SMBIOS specification. Save these entries when >> decoding the DMI tables. >> > > Why can't an interested user just use dmidecode? > > Thanks, > Yazen They could. The reason for doing it in this series is the same reason for the one that we did the S5 bit. It shows up in the logs, you can tie regressions to the AGESA version at specifically at the time of the failure if they've done BIOS updates since then.