From: Paul Fertser <fercerpav@gmail.com>
To: Johnathan Mantey <johnathanx.mantey@intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
Konstantin Klubnichkin <kitsok@yandex-team.ru>
Subject: Re: SATA hotplug notifications for BMC inventory updates
Date: Wed, 7 Sep 2022 17:26:01 +0300 [thread overview]
Message-ID: <Yxip+Yyd8TPWhRft@home.paul.comp> (raw)
In-Reply-To: <a18faae2-7efe-42ab-4a85-215afbaaf89b@intel.com>
(skipped discussion about SMI, as I guess an SMI handler can't
meaningfully communicate with the BMC anyway since that would add an
unacceptable delay to the host operation; I can imagine SMI sending
data to ME and then BMC retrieving it via IPMB but, again, I can't
find any good reference about ME facilities...)
On Wed, Sep 07, 2022 at 07:04:48AM -0700, Johnathan Mantey wrote:
> A back of envelope thought I had is perhaps the host side could interact with
> the BMC via a mailbox. The issue being you'd have to have SW running during the
> BIOS time, and when the OS was in control an OS helper app pushing the data. I'm
> not sure how feasible that idea is.
Some kind of agent running on host can certainly do that. But
apparently no popular GNU/Linux distros package anything like that, so
it must be a rare need.
I asked experienced VMWare ESXi admins and they told me even SATA
drives show in BMC properly without any additional vendor "vibs"
installed on the host system so there must be some side channel
present on many production server systems.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
next prev parent reply other threads:[~2022-09-07 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 11:11 SATA hotplug notifications for BMC inventory updates Paul Fertser
2022-09-06 15:53 ` Johnathan Mantey
[not found] ` <17841662532977@mail.yandex-team.ru>
2022-09-07 14:04 ` Johnathan Mantey
2022-09-07 14:26 ` Paul Fertser [this message]
2022-09-07 14:16 ` Paul Fertser
2022-09-07 14:36 ` Johnathan Mantey
2022-09-09 8:32 ` Paul Fertser
2022-09-09 14:12 ` Johnathan Mantey
2022-09-09 21:19 ` Bills, Jason M
2022-09-15 15:32 ` Paul Fertser
2022-09-15 15:05 ` Paul Fertser
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=Yxip+Yyd8TPWhRft@home.paul.comp \
--to=fercerpav@gmail.com \
--cc=johnathanx.mantey@intel.com \
--cc=kitsok@yandex-team.ru \
--cc=openbmc@lists.ozlabs.org \
/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.