All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Patrick Venture <venture@google.com>
Cc: Corey Minyard <cminyard@mvista.com>, qemu-devel@nongnu.org
Subject: Re: IPMI Smbus
Date: Tue, 6 Apr 2021 13:34:05 -0500	[thread overview]
Message-ID: <20210406183405.GA7166@minyard.net> (raw)
In-Reply-To: <CAO=noty0eTbxf0OXLgqVVv4he2mwXJTRtZWBM2-1Os8zAjXMvQ@mail.gmail.com>

On Tue, Apr 06, 2021 at 10:06:09AM -0700, Patrick Venture wrote:
> On Tue, Apr 6, 2021 at 9:54 AM Corey Minyard <cminyard@mvista.com> wrote:
> >
> > On Tue, Apr 06, 2021 at 09:04:35AM -0700, Patrick Venture wrote:
> > > Corey;
> > >
> > > I saw you have a branch that is working on adding smbus IPMI support
> > > (the ssif approach).
> > >
> > > Can you provide details on the status of this work?
> >
> > There is already an SMBus BMC device that can sit on the I2C bus.  It's
> > in mainstream qemu now.
> 
> This device:
> 
> github.com/qemu/qemu/blob/master/hw/ipmi/smbus_ipmi.c
> 
> So this device gets added to the BMC's i2c, and it's just that there's
> no host-side support to then master this device?  in a multi-node
> simulation.

This works two ways, there is an internal, simple BMC simulator, or it
can make a connection to an external BMC.

> 
> I'm asking because my team is currently working on implementing ssif
> support (between two nodes).

Ah, there is already a protocol that I developed for this that others
are using already.  At Google I think, among others.  It's described in:
https://sourceforge.net/p/openipmi/code/ci/master/tree/lanserv/README.vm

The rest of that directory is a BMC simulator that can connect to qemu
and manage a qemu session, starting, stopping, monitoring, etc.  The
idea was to use IPMI to manage qemu, and some people are using it for
that.

There is obviously already a bridge on the host side to handle taking
the SSIF messages and transporting them over the wire to something else.
I know people were working on the BMC side, but I don't know the status.

-corey

> 
> >
> > It does not have smbus alert support, though.  I have patches for that,
> > but qemu doesn't have a flexibly general interrupt infrastructure, so I
> > hacked something in, and it's likely to be contentious.  The trouble is
> > that the interrupt is disconnected from any real device, and qemu
> > doesn't handle that very well.  And like the other things, I really only
> > created it for my testing.
> >
> > For doing what you are trying to do, I don't think you need any special
> > support on either side for SSIF to work.
> >
> > -corey
> >
> > >
> > > Patrick
> 


      reply	other threads:[~2021-04-06 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 16:04 IPMI Smbus Patrick Venture
2021-04-06 16:54 ` Corey Minyard
2021-04-06 17:06   ` Patrick Venture
2021-04-06 18:34     ` Corey Minyard [this message]

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=20210406183405.GA7166@minyard.net \
    --to=minyard@acm.org \
    --cc=cminyard@mvista.com \
    --cc=qemu-devel@nongnu.org \
    --cc=venture@google.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.