archive mirror
 help / color / mirror / Atom feed
From: Troy Lee <>
To: "Chris Chen (TPI)" <>,
	"" <>
Subject: RE: [phosphor-host-ipmid] Questions about IPMI (OEM) command development
Date: Mon, 6 Sep 2021 10:03:28 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


Using ```journalctl -o json-pretty```, you will see other entries in each log.

Troy Lee

From: openbmc <> On Behalf Of Chris Chen (TPI)
Sent: Monday, September 6, 2021 5:41 PM
Subject: 回覆: [phosphor-host-ipmid] Questions about IPMI (OEM) command development

Hi all,

I guess this mail was got overwhelmed by bunches of emails, so please let me resend it and hope someone could help me. Another, I add one more question marked #5 below.

Thank you.

Chris Chen

寄件者: openbmc <> 代表 Chris Chen (TPI) <>
寄件日期: 2021年9月2日 下午 06:34
收件者: <>
主旨: [phosphor-host-ipmid] Questions about IPMI (OEM) command development 
Hi all,

I have studied "phosphor-host-ipmid" package for a couple of weeks and got understanding that it has implemented some mandatory and optional commands already. And I also knew that I'm able to leverage "intel-ipmi-oem" package to get more command handlers. But there're some questions raised in my mind, I hope someone could give me some suggestions.
1. What's the normal development procedure in case I want to make our own OEM commands? I mean do you guys encourage me to create a new "xxx-ipmi-oem" package or to leverage "intel-ipmi-oem" and then add our own commands in it?
2. I for now added "intel-ipmi-oem" package only for using its "<Chassis>:<Set Front Panel Enables>" command because I figured out the same command in the "phosphor-host-ipmid" is not able to match the d-bus interface in the "x86-power-control". I'm not sure if I will need other commands in the "intel-ipmi-oem", but what if I don't need other commands, how to remove them? to use the whitelist mechanism?
3. Is it okay to add more than 1 xxx-ipmi-ome packages? If yes, how to manage the whitelist between these 2 OEM packages?
4. Am I able to use "intel-ipmi-oem" on a platform that is using AMD CPU?
5. How to print the "entry("SENDER=%s", sender.c_str())" parts? I mean I for now can print out "Set up ipmi context" string after following the instruction listed in "", but I don't see "SENDER=" when I executed "journalctl -t ipmid" command.
6. log<level::DEBUG>("Set up ipmi context", entry("SENDER=%s", sender.c_str()), 
                      entry("NETFN=0x%X", netFn), entry("LUN=0x%X", lun),
                      entry("CMD=0x%X", cmd), entry("CHANNEL=%u", channel),
                      entry("USERID=%u", userId),
                      entry("SESSIONID=0x%X", sessionId),
                      entry("PRIVILEGE=%u", static_cast<uint8_t>(privilege)),
                      entry("RQSA=%x", rqSA));

Thank you.

Chris Chen
Legal Disclaimer :
The information contained in this message may be privileged and confidential. 
It is intended to be read only by the individual or entity to whom it is addressed 
or by their designee. If the reader of this message is not the intended recipient, 
you are on notice that any distribution of this message, in any form, 
is strictly prohibited. If you have received this message in error, 
please immediately notify the sender and delete or destroy any copy of this message!

  reply	other threads:[~2021-09-06 10:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 10:34 [phosphor-host-ipmid] Questions about IPMI (OEM) command development Chris Chen (TPI)
2021-09-06  9:40 ` 回覆: " Chris Chen (TPI)
2021-09-06 10:03   ` Troy Lee [this message]
2021-09-07  0:25     ` Chris Chen (TPI)
2021-09-06 10:15   ` Andrei Kartashev
2021-09-07  0:35     ` 回覆: " Chris Chen (TPI)
2021-09-07  9:52       ` Chris Chen (TPI)
2021-09-07 11:45         ` Chris Chen (TPI)
2021-09-09 20:15   ` Vernon Mauery
2021-09-11  3:56     ` 回覆: " Chris Chen (TPI)
2021-09-15  2:35       ` Vernon Mauery
2021-09-17  0:13         ` Chris Chen (TPI)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).