IPMI: Run to completion fixes
PATCH 3/8 IPMI: Run to completion fixes
From: Corey Minyard <[email protected]>
The "run_to_completion" mode was somewhat broken. Locks need to be avoided in run_to_completion mode, and it shouldn't be used by normal users, just internally for panic situations.
This patch removes locks in run_to_completion mode and removes the user call for setting the mode. The only user was the poweroff code, but it was easily converted to use the polling interface.
---
drivers/char/ipmi/ipmi_msghandler.c +0 -8
@@ -1197,13 +1197,6 @@ int ipmi_unregister_for_cmd(ipmi_user_treturn rv; } -void ipmi_user_set_run_to_completion (ipmi_user_t user,int val) -{ -ipmi_smi_t intf = user->intf; -if (intf->handlers) - intf->handlers->set_run_to_completion (intf->send_info, val); -} -static unsigned char ipmb_checksum (unsigned char *data,int size) {
@@ -4201,5 +4194,4 @@ EXPORT_SYMBOL(ipmi_get_my_address);EXPORT_SYMBOL (ipmi_set_my_LUN);EXPORT_SYMBOL (ipmi_get_my_LUN);EXPORT_SYMBOL (ipmi_smi_add_proc_entry); -EXPORT_SYMBOL (ipmi_user_set_run_to_completion);EXPORT_SYMBOL (ipmi_free_recv_msg);
drivers/char/ipmi/ipmi_poweroff.c +16 -4
@@ -99,11 +99,14 @@ static unsigned char ipmi_version;allocate them, since we may be in a panic situation. The whole thing is single-threaded, anyway, so multiple messages are not required. */ +static atomic_t dummy_count =ATOMIC_INIT (0 );static void dummy_smi_free (struct ipmi_smi_msg *msg) { +atomic_dec (&dummy_count); }static void dummy_recv_free (struct ipmi_recv_msg *msg) { +atomic_dec (&dummy_count); }static struct ipmi_smi_msg halt_smi_msg = {
@@ -152,17 +155,28 @@ static int ipmi_request_wait_for_responsreturn halt_recv_msg.msg.data[0 ]; } -/* We are in run-to-completion mode, no completion is desired. */ +/* Wait for message to complete, spinning. */ static int ipmi_request_in_rc_mode (ipmi_user_t user,struct ipmi_addr *addr,struct kernel_ipmi_msg *send_msg) {int rv; +atomic_set (&dummy_count,2 ); rv =ipmi_request_supply_msgs (user, addr,0 , send_msg,NULL , &halt_smi_msg, &halt_recv_msg,0 ); -if (rv) +if (rv) { +atomic_set (&dummy_count,0 );return rv; + } + +/* +* Spin until our message is done. +*/ +while (atomic_read (&dummy_count) >0 ) { +ipmi_poll_interface (user); +barrier (); + }return halt_recv_msg.msg.data[0 ]; }
@@ -531,9 +545,7 @@ static void ipmi_poweroff_function (voidreturn ;/* Use run-to-completion mode, since interrupts may be off. */ -ipmi_user_set_run_to_completion (ipmi_user,1 );specific_poweroff_func (ipmi_user); -ipmi_user_set_run_to_completion (ipmi_user,0 ); }/* Wait for an IPMI interface to be installed, the first one installed
drivers/char/ipmi/ipmi_si_intf.c +19 -23
83 lines not on this page · raw message
include/linux/ipmi.h +2 -9
@@ -368,9 +368,8 @@ int ipmi_request_supply_msgs(ipmi_user_t* Poll the IPMI interface for the user. This causes the IPMI code to * do an immediate check for information from the driver and handle * anything that is immediately pending. This will not block in any -* way. This is useful if you need to implement polling from the user -* for things like modifying the watchdog timeout when a panic occurs -* or disabling the watchdog timer on a reboot. +* way. This is useful if you need to spin waiting for something to +* happen in the IPMI driver. */ void ipmi_poll_interface (ipmi_user_t user);
@@ -422,12 +421,6 @@ int ipmi_get_maintenance_mode(ipmi_user_int ipmi_set_maintenance_mode (ipmi_user_t user,int mode);/* -* Allow run-to-completion mode to be set for the interface of -* a specific user. -*/ -void ipmi_user_set_run_to_completion (ipmi_user_t user,int val); - -/* * When the user is created, it will not receive IPMI events by * default. The user must set this to TRUE to get incoming events. * The first user that sets this to TRUE will receive all events that
Quoted 10 lines · On Wed, 13 Feb 2008 10:23:42 -0600 Corey Minyard <[email protected]> wrote:
From: Corey Minyard <[email protected]>
The "
run_to_completion" mode was somewhat broken. Locks need to be avoided inrun_to_completionmode, and it shouldn't be used by normal users, just internally for panic situations.This patch removes locks in
run_to_completionmode and removes the user call for setting the mode. The only user was the poweroff code, but it was easily converted to use the polling interface.
drivers/char/ipmi/ipmi_poweroff.c static int ipmi_request_wait_for_respons · line 179
Quoted 7 lines
drivers/char/ipmi/ipmi_poweroff.c +7
-0+/* +* Spin until our message is done. +*/ +while (atomic_read (&dummy_count) >0 ) { +ipmi_poll_interface (user); +barrier (); + }
we'd normally use cpu_relax() here.
Quoted 14 lines · Andrew Morton
Quoted 10 lines · On Wed, 13 Feb 2008 10:23:42 -0600 Corey Minyard <[email protected]> wrote:
From: Corey Minyard <[email protected]>
The "
run_to_completion" mode was somewhat broken. Locks need to be avoided inrun_to_completionmode, and it shouldn't be used by normal users, just internally for panic situations.This patch removes locks in
run_to_completionmode and removes the user call for setting the mode. The only user was the poweroff code, but it was easily converted to use the polling interface.
Quoted 11 lines
drivers/char/ipmi/ipmi_poweroff.c static int ipmi_request_wait_for_respons · line 179
Quoted 8 lines
drivers/char/ipmi/ipmi_poweroff.c +7
-0+/* +* Spin until our message is done. +*/ +while (atomic_read (&dummy_count) >0 ) { +ipmi_poll_interface (user); +barrier (); + }we'd normally use
cpu_relax()here.
Yes, that's what I should have used. I'll submit a new patch to fix this.
-corey