smbios-mdrv2: Support deviceLocator as Dimm object on config update
The use-device-locator-as-dimm-object-path feature is only handling the
scenario when creating the obejcts for the first time. But if the smbios
config gets updated and ther order of dimm in smbios is different from
before then it will look for the content from previous index which will
cause the content to be wrong.
The scenario can happen if we are updating BIOS which has different
order for DIMMs in the Smbios. When smbios-mdr2 first starts it will
process the old smbios data since the bios has not completed it's
process yet. After Bios sends the smbios with different dimm order, now
the smbios-mdr will try to update the properties of each dimm assuming
the previous index is still same but which may not be true.
Tested: Updated BMC with different BIOS order and checked the DIMMs are
showing correct value.
Platforms-Affected: All; specially platform15 and platform21
Fusion-Link: fusion2 link in comment
Google-Bug-Id: 442451039
Change-Id: Ib1689f6e074b929ad20b5d734a0b98445e81c701
Signed-off-by: Munawar Hussain <munawarhussain@google.com>
(cherry picked from commit 1ef4248c58240c55aca47a51399b2f27c8ed206b)
1 file changed
