Question of Redfish PCIe

Question of Redfish PCIe

[Spencer Ku (古世瑜)]

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]

Hi All,
We are interested in how to get PCIe relative info via redfish, like PCIeDevice, PCIeSlot and so on.

In my opinion, package “peci-pcie” is used to collect the PCIe info and filled them into the PCIe D-bus, after that the bmcweb can get relative info through the D-bus.
Then I look into the gerrit’s active patches and find that the D-bus interface is changed, and here are some example:

Original interface implement by peci-pcie:
xyz.openbmc_project.PCIe.Device

Current interface used in the patches:
xyz.openbmc_project.Inventory.Item.PCIeDevice
xyz.openbmc_project.Inventory.Item.PCIeSlot

Does it means that peci-pcie will be updated to cover the D-bus changes or I need to add the D-bus by myself under the xyz.openbmc_project.Inventory.Item?
Just want to know the current status of redfish PCIe, thanks!

Sincerely,
Spencer Ku

[-- Attachment #2: Type: text/html, Size: 3835 bytes --]

Re: Question of Redfish PCIe

[Bills, Jason M]

On 3/24/2021 1:45 AM, Spencer Ku (古世瑜) wrote:
> Hi All,
> 
> We are interested in how to get PCIe relative info via redfish, like 
> PCIeDevice, PCIeSlot and so on.
> 
> In my opinion, package “peci-pcie” is used to collect the PCIe info and 
> filled them into the PCIe D-bus, after that the bmcweb can get relative 
> info through the D-bus.
> 
> Then I look into the gerrit’s active patches and find that the D-bus 
> interface is changed, and here are some example:
> 
> Original interface implement by peci-pcie:
> 
> xyz.openbmc_project.PCIe.Device
> 
> Current interface used in the patches:
> 
> xyz.openbmc_project.Inventory.Item.PCIeDevice
> 
> xyz.openbmc_project.Inventory.Item.PCIeSlot
> 
> Does it means that peci-pcie will be updated to cover the D-bus changes 
> or I need to add the D-bus by myself under the 
> xyz.openbmc_project.Inventory.Item?
Yes, if there is now an official phosphor-dbus-interface for PCIe 
Devices that bmcweb will start using, then peci-pcie will need to be 
updated to use that interface.

When that change merges into bmcweb, I'll plan to push an update to 
peci-pcie
> 
> Just want to know the current status of redfish PCIe, thanks!
> 
> Sincerely,
> 
> Spencer Ku
> 

RE: Question of Redfish PCIe

[Spencer Ku (古世瑜)]

Hi Bill,
Okay, I see. I will wait the update of the PCIe interface and peci-pcie.
Thanks for your reply!

Sincerely,
Spencer Ku

> -----Original Message-----
> From: openbmc
> <openbmc-bounces+spencer.ku=quantatw.com@lists.ozlabs.org> On Behalf Of
> Bills, Jason M
> Sent: Thursday, March 25, 2021 2:42 AM
> To: openbmc@lists.ozlabs.org
> Subject: Re: Question of Redfish PCIe
> 
> 
> 
> On 3/24/2021 1:45 AM, Spencer Ku (古世瑜) wrote:
> > Hi All,
> >
> > We are interested in how to get PCIe relative info via redfish, like
> > PCIeDevice, PCIeSlot and so on.
> >
> > In my opinion, package “peci-pcie” is used to collect the PCIe info
> > and filled them into the PCIe D-bus, after that the bmcweb can get
> > relative info through the D-bus.
> >
> > Then I look into the gerrit’s active patches and find that the D-bus
> > interface is changed, and here are some example:
> >
> > Original interface implement by peci-pcie:
> >
> > xyz.openbmc_project.PCIe.Device
> >
> > Current interface used in the patches:
> >
> > xyz.openbmc_project.Inventory.Item.PCIeDevice
> >
> > xyz.openbmc_project.Inventory.Item.PCIeSlot
> >
> > Does it means that peci-pcie will be updated to cover the D-bus
> > changes or I need to add the D-bus by myself under the
> > xyz.openbmc_project.Inventory.Item?
> Yes, if there is now an official phosphor-dbus-interface for PCIe Devices that
> bmcweb will start using, then peci-pcie will need to be updated to use that
> interface.
> 
> When that change merges into bmcweb, I'll plan to push an update to peci-pcie
> >
> > Just want to know the current status of redfish PCIe, thanks!
> >
> > Sincerely,
> >
> > Spencer Ku
> >