openbmc_project/Dump/Create.interface.yaml

7     /xyz/openbmc_project/dump/<dump type>. On multi-host or on multi-BMC systems
9     /xyz/openbmc_project/dump/<dump type><instance-id>.
12     - name: CreateDump
16           - name: AdditionalData
20                 this case should be an implementation specific enum defined for
21                 the specific type of dump either in xyz or in a domain. The
23                 enum-format string is required to come from a parallel class
24                 with this specific Enum name. All of the Enum strings should be
34           - name: Path
41           - xyz.openbmc_project.Common.File.Error.Open
42           - xyz.openbmc_project.Common.File.Error.Write
43           - xyz.openbmc_project.Dump.Create.Error.Disabled
44           - xyz.openbmc_project.Dump.Create.Error.QuotaExceeded
45           - xyz.openbmc_project.Common.Error.NotAllowed
46           - xyz.openbmc_project.Common.Error.InvalidArgument
47           - xyz.openbmc_project.Common.Error.Unavailable
50     - name: CreateParameters
54           - name: "OriginatorId"
59           - name: "OriginatorType"
64           - name: "DumpType"
67           - name: "FilePath"
70                 core-dump.
71           - name: "ErrorType"
77           - name: "EventId"
79                 The identifier for an event that triggers the BMC dump. When a
80                 BMC dump is initiated as a response to a specific system event,
82                 with that event. By linking the dump to an event ID, the system
86     - name: DumpType
90           - name: "ApplicationCored"
93           - name: "UserRequested"
96           - name: "ErrorLog"
98                 This type of dump is triggered in response to a specific error
102           - name: "Ramoops"
107     - default: xyz.openbmc_project.Dump.Manager
110     - namespace: /xyz/openbmc_project/dump
112           - name: BMC
114           - name: System