releasenote.md: cleanup and fixes (on top of microcode-20250512) #103
+150
−122
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
microcode-20231114 release has removed the baffling usage of U+0080; however, unfortunately, it also has misaligned the "New Platforms" table of the microcode-20230808 release and "Updated Platforms" table of the microcode-20230214 release; fix that. Fixes: ece0d29 "microcode-20231114 Release" Signed-off-by: Eugene Syromiatnikov <[email protected]>
Starting with microcode-20220809, the first-level "Release Notes" header is duplicated for unknown reason; remove it, as it does not make sense to have it multiple times in the middle of the document, consider the fact that first-level header is usually reserved for the document name (and it seems that it indeed bears that role). * releasenote.md: Remove all "Release Notes" headers after the first one. Signed-off-by: Eugene Syromiatnikov <[email protected]>
…cally microcode-20230214 seemingly (but not fully; the "New Platforms" section still have used the old sorting order) have switched the entries order from sorting on the FF-MM-SS/PI field to sorting on the Codename field (which is arguably significantly less useful and much more confusing, especially in cases of CPUIDs spanning several code names, such as 06-8e-0[9ac]). However, it is impossible to devise the sorting order of the entries in the microcode-20230808 changelog table, which makes it even more difficult to navigate, so this patch just changes it to the lastly used one. Signed-off-by: Eugene Syromiatnikov <[email protected]>
microcode-20230214, microcode-20230512, and microcode-20230512-rev2
release notes state that the platform mask for CPUIDs with FF-MM-SS
06-ba-02 and 06-ba-03 is 0x07, but it is, in fact, 0xc0:
$ iucode_tool -L microcode-20230{214,512,512-rev2}/intel-ucode/06-ba-0[23]
microcode bundle 1: microcode-20230214/intel-ucode/06-ba-02
001/001: sig 0x000b06a2, pf_mask 0xc0, 2022-12-08, rev 0x410e, size 212992
sig 0x000b06a2, pf_mask 0xc0, 2022-12-08, rev 0x410e
sig 0x000b06a3, pf_mask 0xc0, 2022-12-08, rev 0x410e
microcode bundle 2: microcode-20230214/intel-ucode/06-ba-03
002/001: sig 0x000b06a2, pf_mask 0xc0, 2022-12-08, rev 0x410e, size 212992
sig 0x000b06a2, pf_mask 0xc0, 2022-12-08, rev 0x410e
sig 0x000b06a3, pf_mask 0xc0, 2022-12-08, rev 0x410e
microcode bundle 3: microcode-20230512/intel-ucode/06-ba-02
003/001: sig 0x000b06a2, pf_mask 0xc0, 2023-02-22, rev 0x4112, size 212992
sig 0x000b06a2, pf_mask 0xc0, 2023-02-22, rev 0x4112
sig 0x000b06a3, pf_mask 0xc0, 2023-02-22, rev 0x4112
microcode bundle 4: microcode-20230512/intel-ucode/06-ba-03
004/001: sig 0x000b06a2, pf_mask 0xc0, 2023-02-22, rev 0x4112, size 212992
sig 0x000b06a2, pf_mask 0xc0, 2023-02-22, rev 0x4112
sig 0x000b06a3, pf_mask 0xc0, 2023-02-22, rev 0x4112
microcode bundle 5: microcode-20230512-rev2/intel-ucode/06-ba-02
005/001: sig 0x000b06a2, pf_mask 0xc0, 2023-02-22, rev 0x4112, size 212992
sig 0x000b06a2, pf_mask 0xc0, 2023-02-22, rev 0x4112
sig 0x000b06a3, pf_mask 0xc0, 2023-02-22, rev 0x4112
microcode bundle 6: microcode-20230512-rev2/intel-ucode/06-ba-03
006/001: sig 0x000b06a2, pf_mask 0xc0, 2023-02-22, rev 0x4112, size 212992
sig 0x000b06a2, pf_mask 0xc0, 2023-02-22, rev 0x4112
sig 0x000b06a3, pf_mask 0xc0, 2023-02-22, rev 0x4112
Also, fix incorrect RPL-U stepping in the microcode-20230214 table.
* releasenote.md (microcode-20230214, microcode-20230512,
microcode-20230512-rev2) <RPL-H 6+8, RPL-P 6+8>: Change the F-M-S field
from 06-ba-02/07 to 06-ba-02/c0.
(microcode-20230214) <RPL-U 2+8>: Change the F-M-S field from 06-ba-02/07
to 06-ba-03/c0.
(microcode-20230512, microcode-20230512-rev2) <RPL-U 2+8>: Change the F-M-S
field from 06-ba-03/07 to 06-ba-03/c0.
Signed-off-by: Eugene Syromiatnikov <[email protected]>
microcode-20221108, microcode-20230214, microcode-20230512,
and microcode-20230512-rev2 release notes (incorrectly) state RPL-S
(06-b7-01/32) stepping as S0, while microcode-20230808 release notes
state it as B0, and [1] confirms the correctness of the latter.
[1] "13th Generation Intel Core Processors. Datasheet, Volume 1 of 2"
Rev. 005, February 2023, section 15.0 "CPU And Device IDs"
https://cdrdv2-public.intel.com/743844/743844-005.pdf
* releasenote.md (microcode-20221108, microcode-20230214,
microcode-20230512, microcode-20230512-rev2) <RPL-S>: Change
the stepping field value from "S0" to "B0".
Signed-off-by: Eugene Syromiatnikov <[email protected]>
microcode-20230808 release notes for CPUIDs 06-ba-02/e0 (RPL-H/P/PX 6+8), 06-ba-03/e0 (RPL-U 2+8), and 06-be-00/11 (ADL-N) are peculiar in a way that these CPUIDs have their PF mask values changed (from 06-ba-02/c0, 06-ba-03/c0, and 06-be-00/01, respectively). Since 06-ba-02/e0 and 06-be-00/11 are listed both in "New Platforms" and "Updated Platforms" sections (which makes some sense, as it is both addition of the platform 0x10 and update for the rest of the platforms), it is natural to assume that this is done this way on purpose, and that 06-ba-03/e0 of these three is accidentally missing from the "New Platforms" section. * releasenote.md (microcode-20230808) <New Platforms>: Add 06-ba-03/e0 (RPL-U 2+8) entry. Signed-off-by: Eugene Syromiatnikov <[email protected]>
CFL-S stepping P0 (06-9e-0c/22) is already listed as "CFL-H/S" and it has not been listed in the notes to the previous releases separately. * releasenote.md (microcode-20230808) <CFL-S P0>: Remove. Signed-off-by: Eugene Syromiatnikov <[email protected]>
…ries The values provided are from the microcode-20230214 release, even though they have been updated in microcode-20230512. Curiously, only one entry of two with CPUID of 06-55-04/b7 has manifested this mistake. * releasenote.md (microcode-20230808) <AML-Y22 H0>: Change the "Old Ver" field from 000000f0 to 000000f2. (microcode-20230808) <SKX-SP H0/M0/U0>: Change the "Old Ver" field from 02006e05 to 02006f05. Signed-off-by: Eugene Syromiatnikov <[email protected]>
…6-ba-03/e0 As has been mentioned already in commit "releasenote.md: add missing 06-ba-03/e0 to the new microcode section", platforms with CPUIDs 06-be-00, 06-ba-02, and 06-ba-03 have their platform mask changed and thusly listed in both "New Platforms" and "Updated Platforms" sections of microcode-20230808 release notes. It is, however, puzzling to have the "Old Ver" field of these entries empty in the "Updated Platforms" section, so it seemingly make sense to populate it with the previous microcode versions for the existing platforms along with the mention of the platform mask change. * releasenote.md (microcode-20230808) <Updated Platforms>: Provide 00000010 as the "Old Ver" field value for ADL-N A0 (06-be-00/11, nee 06-be-00/01); provide 00004112 as the "Old Ver" field value for RPL-H/P/PX 6+8 J0 (06-ba-02/e0, nee 06-ba-02/c0) and RPL-U 2+8 Q0 (06-ba-03/e0, nee 06-ba-03/c0); add footnotes about previous platform mask values. Co-Authored-by: Henrique de Moraes Holschuh <[email protected]> Signed-off-by: Eugene Syromiatnikov <[email protected]>
Release notes for microcode-20250512, microcode-20250211, and microcode-20220809 releases contain trailing white space that seemingly serves no particular purpose; remove it. Signed-off-by: Eugene Syromiatnikov <[email protected]>
…microcode For some reason, information about updates and removals of 06-8f-04 (SPR-SP E0), 06-8f-05 (SPR-SP E2), and 06-8f-06 (SPR-SP E3) microcode files is missing from microcode-20240312, microcode-20241112, and microcode-20250211 release notes. Document those properly. * releasenote.md (microcode-20250211): Mention removal of 06-8f-05 and 06-8f-06 microcode files. (microcode-20241112): Mention update of 06-8f-05 microcode from revision 0x2b0005c0 up to 0x2b000603. (microcode-20240312): Mention removal of 06-8f-04 microcode file. Signed-off-by: Eugene Syromiatnikov <[email protected]>
This microcode file was first appeared as part of microcode-20240312,
was present in the following releases up to microcode-20241112,
and was removed in microcode-20250211. While [1] mentions
that there are no products in production that would use that microcode,
it does not warrant creation of discrepancy between the release notes
and the actually shipped contents; moreover, presence of 60BA8 CPUID
in [2] hints at its possible availability, after all.
NB: This CPUID can still be updated with the latest 06-ba-0* microcode
even despite removal of the microcode file, as it shares the microcode
data with 06-ba-02 and 06-ba-03 microcode files, that still contain
it in the extended signature:
% iucode_tool -L microcode-20250211/intel-ucode/06-ba-02
microcode bundle 1: microcode-20250211/intel-ucode/06-ba-02
001/001: sig 0x000b06a2, pf_mask 0xe0, 2024-07-31, rev 0x4124, size 220160
sig 0x000b06a2, pf_mask 0xe0, 2024-07-31, rev 0x4124
sig 0x000b06a3, pf_mask 0xe0, 2024-07-31, rev 0x4124
sig 0x000b06a8, pf_mask 0xe0, 2024-07-31, rev 0x4124
[1] intel#83 (comment)
[2] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01139.html
* releasenote.md (microcode-20240312): Mention addition of the microcode
at revision 0x4121.
(microcode-20240910): Mention an update to revision 0x4122.
(microcode-20241112)
Signed-off-by: Eugene Syromiatnikov <[email protected]>
* releasenote.md (microcode-20240531): Add missing spaces in the 06-cf-01 and 06-cf-02 (EMR-SP) entries. Signed-off-by: Eugene Syromiatnikov <[email protected]>
Having an empty table (with an additional empty line, compared to non-empty ones) is really inconsistent. * releasenote.md (microcode-20241112, microcode-20241029, microcode-20240813, microcode-20240531, microcode-20240514, microcode-20231114): Replace empty tables in the "New Platforms" sub-section with "None". Signed-off-by: Eugene Syromiatnikov <[email protected]>
…e notes There is little reason to keep those botched. * releasenote.md (microcode-20230512): Add old revisions for 06-8e-09/10 (AML-Y22), 06-8e-09/c0 (KBL-U/Y), 06-55-04/b7 (SKX-D, SKX-SP), and 06-8e-0b/d0 (WHL-U) CPUIDs. Signed-off-by: Eugene Syromiatnikov <[email protected]>
The empty lines are pretty inconsistent in the latest releases. Apply the following rules uniformely throughout the release notes: * two empty lines before the each release section (except the first one); * a single empty line between sub-sections within each section; * a single empty line between security and functional issue lists in the "Purpose" sub-section. Signed-off-by: Eugene Syromiatnikov <[email protected]>
…crocode For some reason, information about removal of 06-55-06 (CLX-SP B0) and 06-cf-01 (EMR-SP A0) microcode file is missing from microcode-20250512 release notes. Document those properly. * releasenote.md (microcode-20250512): Mention removal of 06-55-06 and 06-cf-01 microcode files. Signed-off-by: Eugene Syromiatnikov <[email protected]>
esyr-rh
force-pushed
the
microcode-20250512-releasenote-fixes
branch
from
53b47e3 to
98d372c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR supersedes #95, as it is rebased on top of microcode-20250512 and includes some new cleanups and fixes for various inaccuracies in the recent release notes, as well as the feedback kindly provided @hmh, including the following:
remove excess "Release Notes" first-level headers;