talos-skiboot/core/ipmi.c, branch master

ipmi: Log exact NetFn value in OPAL logs

2016-03-07T03:35:54+00:00

As per IPMI message format NetFn value in present in first 6 bits while last 2 bits contain LUN value. This needs to be taken care while printing NetFn value in OPAL logs which is useful while debugging fails. [root@fir01 /]# ipmitool raw 0x0a 0x48 47 b1 d0 56 [root@fir01 /]# >From OPAL Logs --------------- [133969609199,7] BT: seq 0x3d netfn 0x0a cmd 0x48: Message sent to host [133975465455,7] BT: seq 0x3d netfn 0x0a cmd 0x48: IPMI MSG done >From BMC Logs -------------- IPMIMain: [693 WARNING][corecmdselect.c:913] Request: Channel:f; Netfn:a; Cmd:48; IPMIMain: [693 INFO][corecmdselect.c:924] Response: Channel:f; Netfn:a; Cmd:48; Data:0 47 b1 d0 56 Signed-off-by: Vipin K Parashar Reviewed-by: Cyril Bur Signed-off-by: Stewart Smith

core/ipmi: Provide the dequeue message interface

2015-07-03T07:09:43+00:00

Add a wrapper for the client to be able to invoke the backend dequeue message function. Signed-off-by: Neelesh Gupta Cc: Alistair Popple Acked-by: Alistair Popple Signed-off-by: Stewart Smith

ipmi: Check for ipmi backend presence before use

2015-04-17T19:30:03+00:00

Not all ipmi related functions check for a valid backend before attempting to use it. Under normal circumstances this should not happen as the platform should always register an ipmi backend. However a system should be able to boot without a functional ipmi backend, which is sometimes the case during system bringup. This patch adds presence checks for an ipmi backend before attempting to use it, thus allowing a system with a non-functional backend to boot without ipmi. Signed-off-by: Alistair Popple Reviewed-by: Joel Stanley Signed-off-by: Stewart Smith

Remove redundant includes of opal-api.h

2015-04-01T01:16:39+00:00

Now that opal.h includes opal-api.h, there are a bunch of files that include both but don't need to. Signed-off-by: Michael Ellerman Signed-off-by: Stewart Smith

hw/ipmi: Set boot count sensor

2015-03-04T08:02:20+00:00

The boot count sensor is a discrete sensor that is set once the system is up and running. On successful boot, the BMC expects the sensor to be set to 2. Signed-off-by: Joel Stanley

ipmi: Fix locking for synchronous message sending

2015-02-19T04:52:30+00:00

Skiboot now doesn't run the running pollers while holding a lock to avoid dead-locks. The current implementation of ipmi_queue_msg_sync() does exactly that while it waits for the pollers to be called. This patch fixes the problem by releasing the lock prior to calling the pollers. Signed-off-by: Alistair Popple Signed-off-by: Stewart Smith

ipmi/wdt: Add ipmi watchdog timer support

2015-02-09T03:24:58+00:00

Add support for an ipmi watchdog timer. During skiboot initialisation this patch will cause the system to be reset if opal_run_pollers() isn't called for more than 60 seconds. Once the payload is started the watchdog timer will be reset and a pre-timeout interrupt set. The payload should then receive the interrupt and call into skiboot which will disable the watchdog timer. Signed-off-by: Alistair Popple Reviewed-by: Joel Stanley Signed-off-by: Stewart Smith

ipmi: Implement Read Event and SEL parsing

2015-02-09T03:15:57+00:00

The read event mechanism is used when the BMC has an asynchronous message for the host. It sets a flag that we read with Get Message Flags, and then we read the message using Read Event. This event message contains a SEL message. There are two OEM SEL messages we expect from the AMI BMC: - graceful power operations. This is when the BMC wants the host to power down or reboot. - PNOR Locking. When the BMC wants to access the PNOR, it requests that the host not touch it. This patch implements the parsing. Signed-off-by: Joel Stanley Signed-off-by: Stewart Smith

ipmi: handle SMS_ATN events

2015-02-09T03:03:50+00:00

When the bt interface sets the SMS_ATN flag, we perform a Get Message Flags to determine what messages are available. The only message type currently processed is the Event Message Buffer, which provides SEL messages for indicating OEM specific events such as graceful system shutdown and PNOR access requested. These events will be handled by the IPMI layer in skiboot. Signed-off-by: Jeremy Kerr Signed-off-by: Joel Stanley Signed-off-by: Stewart Smith

ipmi: Add support for synchronous message sending

2015-02-09T02:55:26+00:00

This patch adds support for sending ipmi messages synchronously. This is necessary to allow messages to be sent during skiboot initialisation as interrupt servicing/polling is controlled by the host operating system which is not yet running. Signed-off-by: Alistair Popple Reviewed-by: Joel Stanley Signed-off-by: Stewart Smith