[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-devel] KCS Driver & SMS_ATN Register

From: Matt Jerdonek
Subject: Re: [Freeipmi-devel] KCS Driver & SMS_ATN Register
Date: Mon, 1 Mar 2010 06:34:05 -0800 (PST)


Thanks for the clarification.  I see your point and I updated the patch to address it.  As with the previous patch, this compiles, but I didn't run it on hardware yet because my customer has not yet sent me the KCS hardware.

Thanks again,

--- On Thu, 2/25/10, Al Chu <address@hidden> wrote:

From: Al Chu <address@hidden>
Subject: Re: [Freeipmi-devel] KCS Driver & SMS_ATN Register
To: "Matt Jerdonek" <address@hidden>
Cc: "Anand Babu Periasamy" <address@hidden>, address@hidden
Date: Thursday, February 25, 2010, 10:33 AM

Hi Matt,

I don't see it that way.  I could see someone programming a single
thread and only wanting to poll the SMS_ATN bit, and process events as
they occur.  Not doing any other KCS. e.g.


   while (1) {

Maybe I didn't describe it well.  The concern I have with your patch (if
I'm reading it correctly, correct me if I'm wrong) is that the only time
the SMS ATN bit is checked is in _ipmi_kcs_get_status().
_ipmi_kcs_get_status() will only be called through other KCS functions
like ipmi_kcs_read() and ipmi_kcs_write().

So in order for the SMS ATN bit to be checked, ipmi_kcs_read() and
ipmi_kcs_write() have to be called, either by your application or other
IPMI going on in the system, otherwise the SMS_ATN bit will never be
checked.  Correct?  Under your patch, in the above code snippet,
kcs_wait_for_sms() will never return, b/c no other KCS calls are going
on (unless they are other KCS IPMI going on in the system elsewhere).

Perhaps within your patch, you assumed other IPMI going on in other
parts of the system?


Albert Chu
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory

Attachment: ipmi_kcs_sms_atn.patch
Description: Binary data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]