From: Corey Minyard <minyard@acm.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: yakui.zhao@intel.com, lenb@kernel.org,
linux-acpi@vger.kernel.org,
openipmi-developer@lists.sourceforge.net
Subject: Re: [PATCH_v8 1/2] IPMI/ACPI: Define acpi_ipmi notifier hook functions
Date: Mon, 26 Jul 2010 20:19:10 -0500 [thread overview]
Message-ID: <4C4E340E.3050003@acm.org> (raw)
In-Reply-To: <201007261052.04772.bjorn.helgaas@hp.com>
On 07/26/2010 11:52 AM, Bjorn Helgaas wrote:
> On Monday, July 26, 2010 08:46:04 am yakui.zhao@intel.com wrote:
>
>> From: Zhao yakui<yakui.zhao@intel.com>
>>
>>
> This needs a changelog.
>
> This seems like a complicated solution to a simple problem.
>
> I don't understand why the ACPI IPMI opregion stuff can't be made an
> optional feature of the ACPI IPMI driver. Trying to completely decouple
> things is just going to add corner cases and weird dependencies.
>
Well, ipmi_si_intf is pretty darn big as it is. I would like to break
it up.
I spent a little time reading the ACPI spec to understand just what the
heck this thing is. So now my head hurts a little. But from what I can
tell, this provides a way for the ACPI system to specify operations that
are done by sending IPMI messages. For instance, if power control was
done via IPMI, the various control methods for power control would work
their way down the to access to opregion interfaces mapping to IPMI
functions, and that's where this piece of code takes over.
If so, this code has nothing to do with the IPMI system interface. It's
really more ACPI than IPMI. It's sending messages at the very top of
the IPMI stack, where it should. The only reason it cares about ipmi_si
at all is the discovery of the IPMI interfaces.
I agree that a notifier framework seems like massive overkill for this
interface. I will note that there are already interfaces for
registering to receive callbacks when an IPMI device is added or
removed. What's missing is a way to ask "Is this an ACPI PNP device?".
Since this same function will be needed for IPMI SMBus interfaces, if
that ever becomes a reality in the kernel, it seems more reasonable to
provide some type of addition to the IPMI interface to be able to store
this in the low-level code and retrieve this from the IPMI user
interface. So you can use the standard mechanisms to watch for devices
being added, and then query to see if they are PNP at that point.
Does that make sense?
-corey
next prev parent reply other threads:[~2010-07-27 1:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 14:46 [PATCH -v8 0/2] IPMI/ACPI: Install the ACPI IPMI opregion yakui.zhao
2010-07-26 14:46 ` [PATCH_v8 1/2] IPMI/ACPI: Define acpi_ipmi notifier hook functions yakui.zhao
2010-07-26 14:46 ` [PATCH_v8 2/2] ACPI: Add the IPMI opregion driver to enable ACPI to access BMC controller yakui.zhao
2010-07-26 16:54 ` Bjorn Helgaas
2010-07-27 0:53 ` ykzhao
2010-07-26 15:11 ` [PATCH_v8 1/2] IPMI/ACPI: Define acpi_ipmi notifier hook functions Matthew Garrett
2010-07-26 15:15 ` Matthew Garrett
2010-07-26 16:52 ` Bjorn Helgaas
2010-07-27 0:35 ` ykzhao
2010-07-27 1:19 ` Corey Minyard [this message]
2010-07-27 13:22 ` Matthew Garrett
2010-07-27 14:04 ` Corey Minyard
2010-07-28 1:09 ` ykzhao
2010-07-28 3:30 ` Corey Minyard
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=4C4E340E.3050003@acm.org \
--to=minyard@acm.org \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=yakui.zhao@intel.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.