diff options
| author | Michael Shen <gpgpgp@google.com> | 2023-02-13 05:29:04 +0300 |
|---|---|---|
| committer | Ed Tanous <ed@tanous.net> | 2023-02-28 06:00:40 +0300 |
| commit | b9d679d1ce64141342e8a845533ce6af9901aae8 (patch) | |
| tree | 3ef3e69e3d65ec08d8e106156485690822276a7a /AGGREGATION.md | |
| parent | 6c068982d54d20476fd04ae7ef893b153015762e (diff) | |
| download | bmcweb-b9d679d1ce64141342e8a845533ce6af9901aae8.tar.xz | |
processor: Change `Step` default value to USHRT_MAX
Change `Step` default value to USHRT_MAX due to
https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/60717
For a new processor, it's possible that the stepping is really `0`. In
this case, the `Step` will still be ignored which is not expected.
https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/60717
changes the `Step` default value to `maxint`. Thus the `Step` can
correctly display 0 on redfish.
Tested:
1. Redfish service validator passing.
2. bmcweb works fine without errors.
3. Step was hidden when its value is 65535 (max uint16_t).
4. Step also displayed even the value is `0`.
```
root@machine:~# curl localhost/redfish/v1/Systems/system/Processors/cpu0
...
"Step": "0x0000"
...
```
Change-Id: I1857fc597ef2ab13256dc60e534c23d452e5d695
Signed-off-by: Michael Shen <gpgpgp@google.com>
Diffstat (limited to 'AGGREGATION.md')
0 files changed, 0 insertions, 0 deletions