Home
last modified time | relevance | path

Searched full:requester (Results 1 – 25 of 263) sorted by relevance

1234567891011

/openbmc/pldm/oem/ibm/requester/
H A Ddbus_to_file_handler.hpp4 #include "requester/handler.hpp"
14 namespace requester namespace
23 * as a pldm requester in oem-ibm path.
44 pldm::requester::Handler<pldm::requester::Request>* handler);
93 pldm::requester::Handler<pldm::requester::Request>* handler;
97 } // namespace requester
/openbmc/pldm/host-bmc/
H A Ddbus_to_event_handler.hpp5 #include "requester/handler.hpp"
42 * @param[in] requester - reference to Requester object
47 pldm::requester::Handler<pldm::requester::Request>* handler);
100 pldm::requester::Handler<pldm::requester::Request>* handler;
/openbmc/docs/designs/
H A Dpldm-stack.md93 - The BMC should be able to act as a PLDM responder as well as a PLDM requester.
94 As a PLDM requester, the BMC can monitor/control other devices. As a PLDM
98 - As a PLDM requester, the BMC must be able to discover other PLDM enabled
101 - As a PLDM requester, the BMC must be able to send simultaneous messages to
104 - As a PLDM requester, the BMC must be able to handle out of order responses.
122 The design aims at having a single PLDM daemon serve both the requester and
126 The design enables concurrency aspects of the requester and responder functions,
186 #### Requester subsubsection
188 Designing the BMC as a PLDM requester is interesting. We haven't had this with
189 IPMI, because the BMC was typically an IPMI server. PLDM requester functions
[all …]
/openbmc/pldm/oem/ibm/host-bmc/
H A Dhost_lamp_test.hpp4 #include "requester/handler.hpp"
56 pldm::requester::Handler<pldm::requester::Request>* handler) : in HostLampTest()
106 pldm::requester::Handler<pldm::requester::Request>* handler;
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DComponentIntegrity.v1_3_1.json156 …egrityType` contains `SPDM`, a value of `false` shall prohibit the SPDM Requester from using SPDM …
213 … "description": "Integrity information about the SPDM Responder as reported by an SPDM Requester.",
214 … identified by the `TargetComponentURI` property as reported by an SPDM Requester. This property …
372 …Requester shall issue one or more SPDM 'GET_MEASUREMENTS' requests for each of the requested measu…
384 …SPDM Requester shall generate the nonce. The value should be unique and generated using a random …
390 …provided by the client, the value shall be assumed to be `0`. The SPDM Requester shall send this …
448 …roperty shall contain the hashing algorithm negotiated between the SPDM Requester and the SPDM Res…
459 …idate the signature. This property shall only be present when the SPDM Requester was pre-provisio…
465 …Requester and the SPDM Responder. If SPDM version is 1.0 or 1.1, this value shall be a concatenat…
471 …ll contain the asymmetric signing algorithm negotiated between the SPDM Requester and the SPDM Res…
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DComponentIntegrity.v1_3_1.json156 …egrityType` contains `SPDM`, a value of `false` shall prohibit the SPDM Requester from using SPDM …
213 … "description": "Integrity information about the SPDM Responder as reported by an SPDM Requester.",
214 … identified by the `TargetComponentURI` property as reported by an SPDM Requester. This property …
372 …Requester shall issue one or more SPDM 'GET_MEASUREMENTS' requests for each of the requested measu…
384 …SPDM Requester shall generate the nonce. The value should be unique and generated using a random …
390 …provided by the client, the value shall be assumed to be `0`. The SPDM Requester shall send this …
448 …roperty shall contain the hashing algorithm negotiated between the SPDM Requester and the SPDM Res…
459 …idate the signature. This property shall only be present when the SPDM Requester was pre-provisio…
465 …Requester and the SPDM Responder. If SPDM version is 1.0 or 1.1, this value shall be a concatenat…
471 …ll contain the asymmetric signing algorithm negotiated between the SPDM Requester and the SPDM Res…
[all …]
/openbmc/pldm/fw-update/
H A Dupdate_manager.hpp8 #include "requester/handler.hpp"
46 pldm::requester::Handler<pldm::requester::Request>& handler, in UpdateManager()
94 pldm::requester::Handler<pldm::requester::Request>& handler;
H A Dinventory_manager.hpp5 #include "requester/handler.hpp"
44 pldm::requester::Handler<pldm::requester::Request>& handler, in InventoryManager()
163 pldm::requester::Handler<pldm::requester::Request>& handler;
H A Dmanager.hpp8 #include "requester/handler.hpp"
9 #include "requester/mctp_endpoint_discovery.hpp"
41 requester::Handler<requester::Request>& handler, in Manager()
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/
H A DComponentIntegrity_v1.xml65 <Annotation Term="OData.LongDescription" String="This action shall generate a cryptographic signed statement over the given nonce and measurements corresponding to the SPDM Responder. This action shall not be present if the `ComponentIntegrityType` property does not contain the value `SPDM`. The SPDM Requester shall issue one or more SPDM 'GET_MEASUREMENTS' requests for each of the requested measurement indices to the SPDM Responder. When the SPDM 'GET_MEASUREMENTS' requests are made for version 1.2, the parameter 'RawBitStreamRequested' shall contain `0`. The SPDM Requester shall provide the nonce for the action to the SPDM Responder in the last SPDM 'GET_MEASUREMENTS' request. The SPDM Requester shall request a signature in the last SPDM 'GET_MEASUREMENTS' request."/>
69 <Annotation Term="OData.LongDescription" String="This parameter shall contain a 32-byte hex-encoded string that is signed with the measurements. If not provided by the client, the SPDM Requester shall generate the nonce. The value should be unique and generated using a random or a pseudo-random generator. The SPDM Requester shall send this value to the SPDM Responder in the SPDM 'GET_MEASUREMENTS' request."/>
74 <Annotation Term="OData.LongDescription" String="This parameter shall contain the SPDM slot identifier for the certificate containing the private key to generate the signature over the measurements. If not provided by the client, the value shall be assumed to be `0`. The SPDM Requester shall send this value to the SPDM Responder in the SPDM 'GET_MEASUREMENTS' request."/>
144 <Annotation Term="OData.LongDescription" String="This property shall indicate whether security protocols are enabled for the component. If `ComponentIntegrityType` contains `SPDM`, a value of `false` shall prohibit the SPDM Requester from using SPDM to communicate with the component identified by the `TargetComponentURI` property. If `ComponentIntegrityType` contains `TPM`, a value of `false` shall disable the TPM component identified by the `TargetComponentURI` property entirely. If `false`, services shall not provide the TPM and SPDM properties in response payloads for this resource. If `false`, services shall reject action requests to this resource. If `true`, services shall allow security protocols with the component identified by the `TargetComponentURI` property."/>
163 <Annotation Term="OData.Description" String="Integrity information about the SPDM Responder as reported by an SPDM Requester."/>
164 <Annotation Term="OData.LongDescription" String="This property shall contain integrity information about the SPDM Responder identified by the `TargetComponentURI` property as reported by an SPDM Requester. This property shall be present if `ComponentIntegrityType` contains `SPDM` and if `ComponentIntegrityEnabled` contains `true`. For other cases, this property shall be absent."/>
239 <Annotation Term="OData.Description" String="Integrity information about an SPDM Responder as reported by an SPDM Requester
[all...]
/openbmc/pldm/oem/ampere/
H A Doem_ampere.hpp10 #include "../../requester/request.hpp"
59 pldm::requester::Handler<pldm::requester::Request>* reqHandler) : in OemAMPERE()
162 /** @brief pointer to the requester class*/
163 requester::Handler<requester::Request>* reqHandler = nullptr;
/openbmc/pldm/requester/test/
H A Dmock_request.hpp4 #include "requester/request.hpp"
14 namespace requester namespace
30 } // namespace requester
/openbmc/pldm/oem/ibm/libpldmresponder/
H A Dplatform_oem_ibm.hpp4 #include "requester/handler.hpp"
30 pldm::requester::Handler<pldm::requester::Request>* handler);
H A Dfile_io.hpp4 #include "oem/ibm/requester/dbus_to_file_handler.hpp"
7 #include "requester/handler.hpp"
171 pldm::requester::Handler<pldm::requester::Request>* handler) : in Handler()
280 std::make_unique<pldm::requester::oem_ibm:: in Handler()
318 pldm::requester::oem_ibm:: in Handler()
453 std::unique_ptr<pldm::requester::oem_ibm::DbusToFileHandler>
462 std::vector<std::unique_ptr<pldm::requester::oem_ibm::DbusToFileHandler>>
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DComponentIntegrity_v1.xml65 …Requester shall issue one or more SPDM 'GET_MEASUREMENTS' requests for each of the requested measu…
69 …SPDM Requester shall generate the nonce. The value should be unique and generated using a random …
74 …provided by the client, the value shall be assumed to be `0`. The SPDM Requester shall send this …
144 …egrityType` contains `SPDM`, a value of `false` shall prohibit the SPDM Requester from using SPDM …
163 …iption" String="Integrity information about the SPDM Responder as reported by an SPDM Requester."/>
164 … identified by the `TargetComponentURI` property as reported by an SPDM Requester. This property …
239 …ription" String="Integrity information about an SPDM Responder as reported by an SPDM Requester."/>
240 …ct shall contain integrity information about an SPDM Responder as reported by an SPDM Requester."/>
241 <NavigationProperty Name="Requester" Type="Resource.Item" Nullable="false">
252 …Description" String="Identity authentication information about the SPDM Requester and SPDM Respond…
[all …]
/openbmc/libpldm/
H A DCHANGELOG.md42 - requester: Remove related deprecated APIs
127 - requester: add null check for instance db object in pldm_instance_id_alloc()
128 - requester: add null check for instance db object in pldm_instance_id_free()
431 - requester: instance-id: Release read lock on conflict
527 - All the existing "requester" APIs from `libpldm/pldm.h` (also known as
528 `libpldm/requester/pldm.h`):
614 - requester: Fix response buffer cast in pldm_send_recv()
630 - requester: Mark pldm_close() as LIBPLDM_ABI_TESTING
631 - requester: Expose pldm_close() in header
755 - requester: Return PLDM_REQUESTER_OPEN_FAIL from pldm_open() on error
[all …]
/openbmc/pldm/pldmd/
H A Doem_ibm.hpp13 #include "requester/request.hpp"
65 pldm::requester::Handler<pldm::requester::Request>* reqHandler) : in OemIBM()
193 /** @brief pointer to the requester class*/
194 requester::Handler<requester::Request>* reqHandler;
H A Dpldmd.cpp10 #include "requester/handler.hpp"
11 #include "requester/mctp_endpoint_discovery.hpp"
12 #include "requester/request.hpp"
104 requester::Handler<requester::Request>& handler, in processRxMsg()
192 // Setup PLDM requester transport in main()
210 requester::Handler<requester::Request> reqHandler(&pldmTransport, event, in main()
/openbmc/linux/Documentation/devicetree/bindings/pci/
H A Dpci-iommu.txt4 Each PCI(e) device under a root complex is uniquely identified by its Requester
5 ID (AKA RID). A Requester ID is a triplet of a Bus number, Device number, and
17 Requester ID. While a given PCI device can only master through one IOMMU, a
35 - iommu-map: Maps a Requester ID to an IOMMU and associated IOMMU specifier
44 - iommu-map-mask: A mask to be applied to each Requester ID prior to being
H A Dpci-msi.txt4 Each PCI device under a root complex is uniquely identified by its Requester ID
5 (AKA RID). A Requester ID is a triplet of a Bus number, Device number, and
18 Requester ID. A mechanism is required to associate a device with both the MSI
32 - msi-map: Maps a Requester ID to an MSI controller and associated
49 - msi-map-mask: A mask to be applied to each Requester ID prior to being mapped
/openbmc/pldm/requester/
H A DREADME.md3 PLDM requester infrastructure enables the requester code in PLDM daemon to meet
20 The requester code needs to use the `registerRequest` API to register the PLDM
/openbmc/ipmbbridge/
H A Dipmbdefines.hpp40 uint8_t rqSA; /// @brief requester's target address, LS bit=0
41 uint8_t rqSeqLUN; /// @brief requester's sequence number and logical
51 uint8_t rqNetFnLUN; /// @brief requester's net function and logical
/openbmc/linux/drivers/infiniband/hw/hfi1/
H A Dopfn.h39 * parameters, which will be sent to the requester QP once all
41 * Once the requester QP receives the OPFN request, it will
44 * QP receives the response packet and keeps a copy of the requester
/openbmc/pldm/utilities/
H A Dmeson.build5 'requester/set_state_effecter.cpp',
16 'requester/set_state_effecter_async.cpp',
/openbmc/linux/Documentation/trace/
H A Dhisi-ptt.rst115 Link. You can choose to filter the traced headers by either Requester ID,
137 The TLP headers to trace can be filtered by the Root Ports or the Requester ID
141 1 for Root Port filter and 0 for Requester filter. Bit[15:0] indicates the
143 calculated from its PCI Slot ID as (slotid & 7) * 2. The value for a Requester
144 is the Requester ID (Device ID of the PCIe function). Bit[18:16] is currently
151 The driver also presents every supported Root Port and Requester filter through
154 under $(PTT PMU dir)/root_port_filters and files of Requester filters

1234567891011