IPMCTL-DELETE-GOAL(1)
π IPMCTL-DELETE-GOAL π
okay bestie, gather round, because this is the ipmctl manual page for the delete goal command β it lives in the ipmctl manual, and it's literally the "undo button" for your memory allocation goal. let's get into it π«Ά
β¨ NAME β¨
ipmctl-delete-goal β deletes the memory allocation goal from PMem modules π§Ή
πΈ SYNOPSIS πΈ
ipmctl delete [OPTIONS] -goal [TARGETS]
that's it. that's the whole vibe. β¨
π¦ DESCRIPTION π¦
so what this does: it deletes the memory allocation goal from one or more PMem modules. no cap.
but here's the tea, and it's important tea: this command only deletes a memory allocation goal request that has not yet been processed by platform firmware (BIOS). if BIOS already ate it, this isn't the move. π
and now the scary part, listen up:
if you use the PMem module target and the PMem modules you specify do not include all PMem modules that are part of a memory allocation goal request, the result will be PMem modules (the ones you didn't include) that have a broken request β which platform firmware (BIOS) will reject upon the next reboot. π
so yeah. include all of them. don't leave your modules hanging. fr fr.
π OPTIONS π
-h,-helpβ shows you the help for this command. classic. π«Ά-ddrtβ used to specify DDRT as the desired transport protocol for the current invocation ofipmctl.-smbusβ used to specify SMBUS as the desired transport protocol for the current invocation ofipmctl.
Note β the-ddrtand-smbusoptions are mutually exclusive and may not be used together. pick one, bestie, you can't have both π
-lpmbβ used to specify large transport payload size for the current invocation ofipmctl.-spmbβ used to specify small transport payload size for the current invocation ofipmctl.
Note β the-lpmband-spmboptions are mutually exclusive and may not be used together. again: one. not both. π
-o (text|nvmxml),-output (text|nvmxml)β changes the output format. one of:"text"(default) or"nvmxml". yes the default istext, she's the moment β¨
π TARGETS π
-dimm [DimmIDs]β deletes the memory allocation goal from specific PMem modules by optionally supplying one or more comma separated PMem module identifiers. the default is to delete the memory allocation goals from all manageable PMem modules.-socket [SocketIDs]β deletes the memory allocation goal from the PMem modules on specific sockets by supplying the socket target and one or more comma separated socket identifiers. the default is to delete the memory allocation goals from manageable PMem modules on all sockets.
π EXAMPLES π
deletes the memory allocation goal from all PMem modules on all sockets. the full send π
ipmctl delete -goal
π₯ LIMITATIONS π₯
in order to successfully execute this command (aka for it to actually slay):
- the caller must have the appropriate privileges. π
- the specified PMem modules must be manageable by the host software and unlocked if security is enabled.
- given socket and all specified PMem modules must contain a memory allocation goal.
π RETURN DATA π
for each PMem module, the CLI will indicate the status of the operation.
and if a failure occurs when deleting the memory allocation goals from multiple PMem modules, the process will output a failure message for those PMem modules that failed and a success message for those that succeeded. so you get the receipts either way π
β SAMPLE OUTPUT β
Delete memory allocation goal from PMem module (DimmID): Success
Delete memory allocation goal from PMem module (DimmID): Error (Code) - (Description)
okay and that's the whole page!! π¦ this one's from the ipmctl manual, dated 2024-04-22, and it's the IPMCTL-DELETE-GOAL(1) page β now go delete those goals responsibly, bestie, and remember: include all the modules in the goal or BIOS will be so mad at you next reboot. mwah πβ¨π
π¦ where this page comes from
- ubuntu noble: ipmctl 03.00.00.0485-1build1 Β· BSD-2-Clause AND BSD-3-Clause
- ubuntu questing: ipmctl 03.00.00.0485-1build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms