From: Corey Minyard <minyard@acm.org>
To: paulmck@us.ibm.com
Cc: Matt Domsch <Matt_Domsch@dell.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 1/9] ipmi: use refcount in message handler
Date: Mon, 24 Oct 2005 07:52:31 -0500 [thread overview]
Message-ID: <435CD90F.3080108@acm.org> (raw)
In-Reply-To: <20051024062909.GA10337@us.ibm.com>
Paul E. McKenney wrote:
>On Sun, Oct 23, 2005 at 11:42:17PM -0500, Matt Domsch wrote:
>
>
>>On Sun, Oct 23, 2005 at 07:19:32PM -0700, Paul E. McKenney wrote:
>>
>>
>>>My guess is that this read-side critical section can be invoked from and
>>>SMI, and that SMIs can occur even if interrupts are disabled. If my guess
>>>is wrong, please enlighten me. And feel free to ignore the next few
>>>paragraphs in that case, along with a number of my suggested changes,
>>>since they all depend critically on my guess being correct.
>>>
>>>
>>Paul, it took me a bit to figure this out too, but Corey uses the TLA
>>"SMI" to mean "Systems Management Interface", not "Systems Management
>>Interrupt". From Documentation/IPMI.txt:
>>
>>ipmi_msghandler - This is the central piece of software for the IPMI
>>system. It handles all messages, message timing, and responses. The
>>IPMI users tie into this, and the IPMI physical interfaces (called
>>System Management Interfaces, or SMIs) also tie in here.
>>
>>
>>There are at least 4 basic types of physical hardware interfaces (BT,
>>SMIC, KCS, and I2C), which may (or more often, may not) have their own
>>hardware interrupt lines, but these are normal interrupts, not
>>CPU-magic "systems management interrupts". So I think this isn't a
>>problem.
>>
>>
>
>OK, thank you for the tutorial on the "other SMI"!
>
>
Yeah, I've really misnamed this, unfortunately. Too many TLAs.
>The comments about turning synchronize_rcu() into synchronize_sched()
>and rcu_read_lock() into preempt_disable() do not apply, please ignore.
>
>However, I still do not understand how using RCU on cmd_rcvrs helps,
>given that all of the accesses that I could see were already protected
>by cmd_rcvrs_lock.
>
>Any further enlightenment available?
>
>
The calls in handle_ipmb_get_msg_cmd and handle_lan_get_msg_cmd don't
need spinlock protection, just an RCU read lock. Kind of the point of
the RCU list. Thanks for spotting this.
Thanks,
-Corey
next prev parent reply other threads:[~2005-10-24 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 14:49 [PATCH 1/9] ipmi: use refcount in message handler Corey Minyard
2005-10-24 2:19 ` Paul E. McKenney
2005-10-24 4:42 ` Matt Domsch
2005-10-24 6:29 ` Paul E. McKenney
2005-10-24 12:52 ` Corey Minyard [this message]
2005-10-24 22:45 ` Paul E. McKenney
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=435CD90F.3080108@acm.org \
--to=minyard@acm.org \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.