[redfish/v1/Systems/system/Processors] How does it work on wolf pass?

[Bills, Jason M]

On 10/9/2020 5:57 PM, Zhenfei Tai wrote:
> Hi,
> 
> I've been testing bmcweb and noticed the response from the URI 
> `redfish/v1/Systems/system/Processors` contains an empty collection.
> 
> {
>    "@odata.context": 
> "/redfish/v1/$metadata#ProcessorCollection.ProcessorCollection",
>    "@odata.id <http://odata.id>": "/redfish/v1/Systems/system/Processors/",
>    "@odata.type": "#ProcessorCollection.ProcessorCollection",
>    "Members": [],
>    "Members at odata.count": 0,
>    "Name": "Processor Collection"
> }
> 
> Looking at bmcweb code, it seems to look for dbus interfaces 
> `xyz.openbmc_project.Inventory.Item.Cpu` and 
> `xyz.openbmc_project.Inventory.Item.Accelerator`. However they can't be 
> seen in dbus.
> 
> # busctl tree --no-pager xyz.openbmc_project.Inventory.Item.Cpu
> Failed to introspect object / of service 
> xyz.openbmc_project.Inventory.Item.Cpu: The name is not activatable
> 
> Entity-manager and cpu-sensor are running in addition to bmcweb. The 
> entity-manager config is below and I can see the config is picked up in 
> `xyz.openbmc_project.EntityManager`.
> 
> {
>    "Exposes": [
>      {
>          "Address": "0x30",
>          "Bus": 0,
>          "CpuID": 1,
>          "Name": "CPU 1",
>          "Type": "XeonCPU"
>      },
>      {
>          "Address": "0x31",
>          "Bus": 0,
>          "CpuID": 2,
>          "Name": "CPU 2",
>          "Type": "XeonCPU"
>      }
>    ],
>    "Name": "internal_code_name",
>    "Probe": "xyz.openbmc_project.FruDevice({'BOARD_PRODUCT_NAME': 
> 'internal_product_name'})",
>    "Type": "Board"
> }
> 
> I'm not sure what else is required to have the URI work properly. Could 
> someone familiar with this issue help?
On Intel systems, we currently get most CPU information from the SMBIOS 
tables which are provided to the BMC through something called the MDR. 
That application is available here: https://github.com/Intel-BMC/mdrv2.

When we have seen empty CPU or memory resource collections in Redfish, 
it has usually been caused by a failure to get the SMBIOS data from BIOS.

> 
> Thanks,
> Zhenfei