Async request to create PEL
To avoid any deadlocks between phosphor-logging and vpd-manager
service a wrapper around request to create PEL is created
which enables vpd-manager to make async requests to create PEL.
It also implements a new exception type to throw any GPIO
related exception. This was required to throw specific
exception.
Test:
Scenario 1:
While vpd-manager logs a pel with call out to an inventory
item.
It should be checked that both the services do not enter into
a deadlock situation.
Scenario 2:
Any third process is requesting to log PEL with call out
to an inventory item in a loop.
In the mean time vpd-manager also requests to log a PEL
with or without call out to inventory item.
All the pels should be logged correctly in the system.
No deadlock should appear.
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: I0efaf6918e679ca94808fc70d747c843a50eaf78
diff --git a/vpd_exceptions.hpp b/vpd_exceptions.hpp
index 2ea2cd5..f3473e5 100644
--- a/vpd_exceptions.hpp
+++ b/vpd_exceptions.hpp
@@ -134,6 +134,30 @@
}; // class VpdJSonException
+/** @class GpioException
+ * @brief This class extends Exceptions class and define
+ * type for GPIO related exception in VPD
+ */
+class GpioException : public VPDException
+{
+ public:
+ // deleted methods
+ GpioException() = delete;
+ GpioException(const GpioException&) = delete;
+ GpioException(GpioException&&) = delete;
+ GpioException& operator=(const GpioException&) = delete;
+
+ // default destructor
+ ~GpioException() = default;
+
+ /** @brief constructor
+ * @param[in] msg - string to define exception
+ */
+ explicit GpioException(const std::string& msg) : VPDException(msg)
+ {
+ }
+};
+
} // namespace exceptions
} // namespace vpd
} // namespace openpower
\ No newline at end of file