From: Corey Minyard <minyard@acm.org>
To: Srinivas_G_Gowda@Dell.com
Cc: tcminyard@gmail.com, linux-kernel@vger.kernel.org, openipmi@mvista.com
Subject: Re: [PATCH 1/1] ipmi: setting mod_timer for read_event_msg buffer cmd
Date: Mon, 02 Dec 2013 15:03:38 -0600 [thread overview]
Message-ID: <529CF5AA.5040700@acm.org> (raw)
In-Reply-To: <529C9C99.2010108@dell.com>
On 12/02/2013 08:49 AM, Srinivas_G_Gowda@Dell.com wrote:
> Thanks for the patch Corey.
> I am afraid that the system does not have interrupts enabled. It uses polling mode.
>
> When the error is seen, I know for a fact that in function ipmi_thread() smi_result is SI_SM_CALL_WITH_DELAY,
> I have some logs where in busy_wait always reads as 1. Not sure if it was ever set to 0. (ill check this again).
> Ill anyway run the test using the patch that you have shared.
>
> b/w would it harm if we were to do to something like this ?
Unfortunately, that would start the timer unnecessarily. You don't want
to start timers unnecessarily in the kernel or the power management
police will come after you.
The patch I sent did have this call in the non-idle portion of the
kernel thread and that should have done the same thing. Plus, if you
are using the kernel thread, it's going to run periodically and should
kick things off again if they get stuck. I'm suspicious now that
something else is going on.
-corey
>
> Signed-off-by: Srinivas Gowda <srinivas_g_gowda@dell.com>
> ---
> drivers/char/ipmi/ipmi_si_intf.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/char/ipmi/ipmi_si_intf.c b/drivers/char/ipmi/ipmi_si_intf.c
> index 15e4a60..e23484f 100644
> --- a/drivers/char/ipmi/ipmi_si_intf.c
> +++ b/drivers/char/ipmi/ipmi_si_intf.c
> @@ -1008,6 +1008,7 @@ static int ipmi_thread(void *data)
> spin_unlock_irqrestore(&(smi_info->si_lock), flags);
> busy_wait = ipmi_thread_busy_wait(smi_result, smi_info,
> &busy_until);
> + ipmi_start_timer_if_necessary(smi_info);
> if (smi_result == SI_SM_CALL_WITHOUT_DELAY)
> ; /* do nothing */
> else if (smi_result == SI_SM_CALL_WITH_DELAY && busy_wait)
next prev parent reply other threads:[~2013-12-02 21:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 9:51 [PATCH 1/1] ipmi: setting mod_timer for read_event_msg buffer cmd Srinivas_G_Gowda
2013-11-26 17:26 ` Corey Minyard
[not found] ` <75F7F7632819D94BA80703D8B1F10B6D29CEE95A1D@BLRX7MCDC201.AMER.DELL.COM>
2013-11-30 0:19 ` Corey Minyard
2013-12-02 14:49 ` Srinivas_G_Gowda
2013-12-02 21:03 ` Corey Minyard [this message]
2013-12-03 6:18 ` Srinivas_G_Gowda
2013-12-03 17:10 ` Corey Minyard
2013-12-04 11:58 ` Srinivas_G_Gowda
2013-12-05 12:40 ` Srinivas_G_Gowda
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=529CF5AA.5040700@acm.org \
--to=minyard@acm.org \
--cc=Srinivas_G_Gowda@Dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi@mvista.com \
--cc=tcminyard@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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