Lines Matching full:ipmi
2 The Linux IPMI Driver
7 The Intelligent Platform Management Interface, or IPMI, is a
15 To use this, you need an interface to an IPMI controller in your
17 management software that can use the IPMI system.
19 This document describes how to use the IPMI driver for Linux. If you
20 are not familiar with IPMI itself, see the web site at
21 https://www.intel.com/design/servers/ipmi/index.htm. IPMI is a big
27 The Linux IPMI driver is modular, which means you have to pick several
29 these are available in the 'Character Devices' menu then the IPMI
32 No matter what, you must pick 'IPMI top-level message handler' to use
33 IPMI. What you do beyond that depends on your needs and hardware.
37 from userland, you need to select 'Device interface for IPMI' if you
41 properly provides the SMBIOS info for IPMI, the driver will detect it
44 manual), choose the 'IPMI SI handler' option. A driver also exists
45 for direct I2C access to the IPMI management controller. Some boards
47 this, choose 'IPMI SMBus handler', but be ready to try to do some
52 You should generally enable ACPI on your system, as systems with IPMI
56 their job correctly, the IPMI controller should be automatically
63 IPMI defines a standard watchdog timer. You can enable this with the
64 'IPMI Watchdog Timer' config option. If you compile the driver into
73 IPMI systems can often be powered off using IPMI commands. Select
74 'IPMI Poweroff' to do this. The driver will auto-detect if the system
75 can be powered off by IPMI. It is safe to enable this even if your
77 Radisys CPI1 card, and any IPMI system that supports standard chassis
91 The Linux IPMI driver is designed to be very modular and flexible, you
96 ipmi_msghandler - This is the central piece of software for the IPMI
98 IPMI users tie into this, and the IPMI physical interfaces (called
100 provides the kernelland interface for IPMI, but does not provide an
103 ipmi_devintf - This provides a userland IOCTL interface for the IPMI
105 as an IPMI user.
112 I2C kernel driver's SMBus interfaces to send and receive IPMI messages
117 ipmi_watchdog - IPMI requires systems to have a very capable watchdog
119 interface on top of the IPMI message handler.
122 IPMI commands.
131 IPMI include files are:
133 linux/ipmi.h - Contains the user interface and IOCTL interface for IPMI.
136 (things that interface to IPMI controllers) to use.
138 linux/ipmi_msgdefs.h - General definitions for base IPMI messaging.
144 The IPMI addressing works much like IP addresses, you have an overlay
181 than one channel, it corresponds to the channel as defined in the IPMI
244 view of the IPMI interfaces. It allows multiple SMI interfaces to be
252 When your code comes up, the IPMI driver may or may not have detected
253 if IPMI devices exist. So you might have to defer your setup until
307 the netfn per the IPMI spec) on the IPMB bus, the driver will
309 command. If the response is not receive in the IPMI-specified 5
330 The driver takes care of polling for IPMI events and receiving
421 data used by IPMI is 8-bits wide, but it may be inside a larger
425 Since the register size may be larger than 32 bits, the IPMI data may not
427 the data to get to the actual IPMI data.
429 The slave_addrs specifies the IPMI address of the local BMC. This is
434 (if set to 0) the kernel IPMI daemon. Normally this is auto-detected
459 If your IPMI interface does not support interrupts and is a KCS or
460 SMIC interface, the IPMI driver will start a kernel thread for the
462 thread that constantly polls the IPMI driver while an IPMI operation
529 IPMI messages: 1, driver state: 2, timing: 4, I2C probe: 8
537 The slave_addrs specifies the IPMI address of the local BMC. This is
544 Discovering the IPMI compliant BMC on the SMBus can cause devices on
545 the I2C bus to fail. The SMBus driver writes a "Get Device ID" IPMI
565 this driver cannod to IPMI panic events, extend the watchdog at panic
566 time, or other panic-related IPMI functions without special kernel
576 Get the detailed info related with the IPMI device
580 the address came from or the raw base device for the IPMI interface.
581 You can use the IPMI smi_watcher to catch the IPMI interfaces as they
671 comes from the IPMI controller, so it must assume that if it gets an
672 otherwise unhandled NMI, it must be from IPMI and it will panic
687 one event on a panic in a standard IPMI event format. If you enable
695 * EvM Rev: 0x03 (this event is formatting in IPMI 1.0 format)
703 See the IPMI spec for the details of the event layout. This event is
731 If the poweroff capability is selected, the IPMI driver will install
734 it will send the proper IPMI commands to do this. This is supported on
742 in /proc/sys/dev/ipmi/poweroff_powercycle. Note that if the system