<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/include/linux/ipmi_smi.h, branch linux-4.16.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.16.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.16.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2017-09-28T17:26:03Z</updated>
<entry>
<title>ipmi: Make the IPMI proc interface configurable</title>
<updated>2017-09-28T17:26:03Z</updated>
<author>
<name>Corey Minyard</name>
<email>cminyard@mvista.com</email>
</author>
<published>2017-09-16T20:51:25Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=55f91cb6f1dfc873359674f35a8ffb1e78429d22'/>
<id>urn:sha1:55f91cb6f1dfc873359674f35a8ffb1e78429d22</id>
<content type='text'>
So we can remove it later.

Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>ipmi: Remove the device id from ipmi_register_smi()</title>
<updated>2017-09-27T21:03:45Z</updated>
<author>
<name>Corey Minyard</name>
<email>cminyard@mvista.com</email>
</author>
<published>2017-08-31T21:45:40Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=1e5058ea21010883b1e1d288637f7390bb8d1c61'/>
<id>urn:sha1:1e5058ea21010883b1e1d288637f7390bb8d1c61</id>
<content type='text'>
It's no longer used, dynamic device id handling is in place now.

Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>ipmi: Make ipmi_demangle_device_id more generic</title>
<updated>2017-09-27T21:03:45Z</updated>
<author>
<name>Jeremy Kerr</name>
<email>jk@ozlabs.org</email>
</author>
<published>2017-08-25T07:47:23Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=c468f911b73beb39b20f7e5f97a35d41f038b31b'/>
<id>urn:sha1:c468f911b73beb39b20f7e5f97a35d41f038b31b</id>
<content type='text'>
Currently, ipmi_demagle_device_id requires a full response buffer in its
data argument. This means we can't use it to parse a response in a
struct ipmi_recv_msg, which has the netfn and cmd as separate bytes.

This change alters the definition and users of ipmi_demangle_device_id
to use a split netfn, cmd and data buffer, so it can be used with
non-sequential responses.

Signed-off-by: Jeremy Kerr &lt;jk@ozlabs.org&gt;

Fixed the ipmi_ssif.c and ipmi_si_intf.c changes to use data from the
response, not the data from the message, when passing info to the
ipmi_demangle_device_id() function.

Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>ipmi: Don't flush messages in sender() in run-to-completion mode</title>
<updated>2015-09-03T20:02:28Z</updated>
<author>
<name>Hidehiro Kawai</name>
<email>hidehiro.kawai.ez@hitachi.com</email>
</author>
<published>2015-07-27T05:55:16Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=82802f968bd3118af04eaeb3814c21d9813be527'/>
<id>urn:sha1:82802f968bd3118af04eaeb3814c21d9813be527</id>
<content type='text'>
When flushing queued messages in run-to-completion mode,
smi_event_handler() is recursively called.

flush_messages()
 smi_event_handler()
  handle_transaction_done()
   deliver_recv_msg()
    ipmi_smi_msg_received()
     smi_recv_tasklet()
      sender()
       flush_messages()
        smi_event_handler()
         ...

The depth of the recursive call depends on the number of queued
messages, so it can cause a stack overflow if many messages have
been queued.

To solve this problem, this patch removes flush_messages()
from sender()@ipmi_si_intf.c.  Instead, add flush_messages() to
caller side of sender() if needed.  Additionally, to implement this,
add new handler flush_messages to struct ipmi_smi_handlers.

Signed-off-by: Hidehiro Kawai &lt;hidehiro.kawai.ez@hitachi.com&gt;

Fixed up a comment and some spacing issues.

Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>ipmi: Make some data const that was only read</title>
<updated>2015-09-03T20:02:27Z</updated>
<author>
<name>Corey Minyard</name>
<email>cminyard@mvista.com</email>
</author>
<published>2015-06-13T15:34:25Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=81d02b7f8c507f06299476a0e5b2aa677c5eaecb'/>
<id>urn:sha1:81d02b7f8c507f06299476a0e5b2aa677c5eaecb</id>
<content type='text'>
Several data structures were only used for reading, so make them
const.

Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>ipmi: Remove the now unused priority from SMI sender</title>
<updated>2014-12-11T21:04:11Z</updated>
<author>
<name>Corey Minyard</name>
<email>cminyard@mvista.com</email>
</author>
<published>2014-11-07T13:57:31Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=99ab32f3b5d705be562b8c4d9dca7c1ae3dc2cdf'/>
<id>urn:sha1:99ab32f3b5d705be562b8c4d9dca7c1ae3dc2cdf</id>
<content type='text'>
Since the queue was moved into the message handler, the priority
field is now irrelevant.

Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>ipmi: Remove useless sysfs_name parameters</title>
<updated>2014-12-11T21:04:05Z</updated>
<author>
<name>Corey Minyard</name>
<email>cminyard@mvista.com</email>
</author>
<published>2014-10-11T03:11:05Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=5a0e10ec4a82ec9e1ab9b85a0f2c2893f7ffda25'/>
<id>urn:sha1:5a0e10ec4a82ec9e1ab9b85a0f2c2893f7ffda25</id>
<content type='text'>
It was always "bmc", so just hardcode it.  It makes no sense to
pass that in.

Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
</content>
</entry>
<entry>
<title>ipmi: boolify some things</title>
<updated>2014-04-17T19:30:40Z</updated>
<author>
<name>Corey Minyard</name>
<email>cminyard@mvista.com</email>
</author>
<published>2014-04-14T14:46:56Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=7aefac26fc67158cb8826a5f5bfc2a5086a7d962'/>
<id>urn:sha1:7aefac26fc67158cb8826a5f5bfc2a5086a7d962</id>
<content type='text'>
Convert some ints to bools.

Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>ipmi: Turn off all activity on an idle ipmi interface</title>
<updated>2014-04-17T19:23:07Z</updated>
<author>
<name>Corey Minyard</name>
<email>cminyard@mvista.com</email>
</author>
<published>2014-04-14T14:46:54Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=89986496de141213206d49450ffdd36098d41209'/>
<id>urn:sha1:89986496de141213206d49450ffdd36098d41209</id>
<content type='text'>
The IPMI driver would wake up periodically looking for events and
watchdog pretimeouts.  If there is nothing waiting for these events,
it's really kind of pointless to be checking for them.  So modify the
driver so the message handler can pass down if it needs the lower layer
to be waiting for these.  Modify the system interface lower layer to
turn off all timer and thread activity if the upper layer doesn't need
anything and it is not currently handling messages.  And modify the
message handler to not restart the timer if its timer is not needed.

The timers and kthread will still be enabled if:
 - the SI interface is handling a message.
 - a user has enabled watching for events.
 - the IPMI watchdog timer is in use (since it uses pretimeouts).
 - the message handler is waiting on a remote response.
 - a user has registered to receive commands.

This mostly affects interfaces without interrupts.  Interfaces with
interrupts already don't use CPU in the system interface when the
interface is idle.

Signed-off-by: Corey Minyard &lt;cminyard@mvista.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>various: Fix spelling of "asynchronous" in comments.</title>
<updated>2012-11-19T13:32:13Z</updated>
<author>
<name>Adam Buchbinder</name>
<email>adam.buchbinder@gmail.com</email>
</author>
<published>2012-09-20T01:48:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=b3834be5c42a5d2fd85ff4b819fa38983b1450e6'/>
<id>urn:sha1:b3834be5c42a5d2fd85ff4b819fa38983b1450e6</id>
<content type='text'>
"Asynchronous" is misspelled in some comments. No code changes.

Signed-off-by: Adam Buchbinder &lt;adam.buchbinder@gmail.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
</feed>
