From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Kun Yi <kunyi@google.com>, Emily Shaffer <emilyshaffer@google.com>
Cc: tomjose@linux.vnet.ibm.com, vernon.mauery@linux.intel.com,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
bradleyb@us.ibm.com
Subject: Re: IPMI SOL performance
Date: Tue, 20 Mar 2018 08:20:08 -0700 [thread overview]
Message-ID: <87vadqlqon.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAGMNF6XP7Pq4A=cxPps9K7OYHEnFE2Ge2u-7nOpng5kwzZWMhQ@mail.gmail.com>
Kun Yi <kunyi@google.com> writes:
> SOL performance issue aside, there is also an IPMI command for selecting
> the boot device. Is that command currently supported in the client in any
> way? That might be a more reliable solution than relying on console
> alone.
There is, and any reasonable automation kit is going to do that, except
for when it's something like my firmware test suite that executes a
bunch of commands in the petitboot shell environment, for which there's
no way to set "exit to shell" via IPMI, so we just use expect on the
console. We've worked around this in op-test by just using the ssh
console instead (and try not to pump too much data through it too
quickly so we don't hit the bug where we lose console output).
It'd be nice to be able to run the test suite over IPMI though, if only
for completeness.
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2018-03-20 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 11:13 IPMI SOL performance Tom Joseph
2018-03-19 11:17 ` Tom Joseph
2018-03-19 15:39 ` Emily Shaffer
2018-03-19 16:27 ` Stewart Smith
2018-03-19 18:47 ` Emily Shaffer
2018-03-19 19:03 ` Tom Joseph
2018-03-19 19:08 ` Emily Shaffer
2018-03-19 19:34 ` Kun Yi
2018-03-20 15:20 ` Stewart Smith [this message]
2018-03-19 19:35 ` Rob Lippert
2018-03-20 0:35 ` Jeremy Kerr
2018-03-20 10:36 ` Tom Joseph
2018-03-20 10:58 ` Jeremy Kerr
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=87vadqlqon.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=bradleyb@us.ibm.com \
--cc=emilyshaffer@google.com \
--cc=kunyi@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tomjose@linux.vnet.ibm.com \
--cc=vernon.mauery@linux.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.