From: Patrick Williams <patrick@stwcx.xyz>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: minyard@acm.org, benjaminfair@google.com, clg@kaod.org,
joel@jms.id.au, andrew@aj.id.au,
openipmi-developer@lists.sourceforge.net,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v1 0/4] ipmi_bmc: framework for IPMI on BMCs
Date: Mon, 14 Aug 2017 11:03:12 -0500 [thread overview]
Message-ID: <20170814160312.GA20526@asimov.lan> (raw)
In-Reply-To: <20170808035301.1980-1-brendanhiggins@google.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Mon, Aug 07, 2017 at 08:52:57PM -0700, Brendan Higgins wrote:
> Currently, OpenBMC handles all IPMI message routing and handling in userland;
> the existing drivers simply provide a file interface for the hardware on the
> device. In this patchset, we propose a common file interface to be shared by all
> IPMI hardware interfaces, but also a framework for implementing handlers at the
> kernel level, similar to how the existing OpenIPMI framework supports both
> kernel users, as well as misc device file interface.
Brendan,
Can you expand on why this is a good thing from an OpenBMC perspective?
We have a pretty significant set of IPMI providers that run in the
userspace daemon(s) and I can't picture more than a very small subset
even being possible to run in kernel space without userspace assistance.
We also already have an implementation of a RMCP+ daemon that can, and
does, share most of its providers with the host-side daemon.
--
Patrick Williams
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-14 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 3:52 Brendan Higgins
2017-08-08 3:52 ` [RFC v1 1/4] ipmi_bmc: framework for BT " Brendan Higgins
2017-08-10 13:58 ` Corey Minyard
2017-08-11 1:06 ` Brendan Higgins
2017-08-08 3:52 ` [RFC v1 2/4] ipmi_bmc: device interface to IPMI BMC framework Brendan Higgins
2017-08-08 3:53 ` [RFC v1 3/4] ipmi_bmc: bt-i2c: port driver " Brendan Higgins
2017-08-08 3:53 ` [RFC v1 4/4] ipmi_bmc: bt-aspeed: " Brendan Higgins
2017-08-10 2:31 ` Jeremy Kerr
2017-08-10 5:29 ` Brendan Higgins
2017-08-10 7:20 ` Cédric Le Goater
2017-08-14 16:03 ` Patrick Williams [this message]
2017-08-14 22:28 ` [RFC v1 0/4] ipmi_bmc: framework for IPMI on BMCs Brendan Higgins
2017-08-23 6:12 ` Brendan Higgins
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=20170814160312.GA20526@asimov.lan \
--to=patrick@stwcx.xyz \
--cc=andrew@aj.id.au \
--cc=benjaminfair@google.com \
--cc=brendanhiggins@google.com \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openbmc@lists.ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®