All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alistair Popple <alistair@popple.id.au>
Cc: openipmi-developer@lists.sourceforge.net,
	linuxppc-dev@lists.ozlabs.org, Jeremy Kerr <jk@ozlabs.org>,
	minyard@acm.org
Subject: Re: [PATCH 0/2] Add IPMI support for powernv powerpc machines
Date: Mon, 10 Nov 2014 17:57:08 +1100	[thread overview]
Message-ID: <1415602628.5769.17.camel@kernel.crashing.org> (raw)
In-Reply-To: <11418996.omepm2UeRF@mexican>

On Mon, 2014-11-10 at 17:01 +1100, Alistair Popple wrote:
> Ben,
> 
> > 
> > Our OPAL interface can only do one at a time ? Because our underlying FW
> > driver already has a queue ..
> 
> The OPAL interface supports sending more than one message at a time using the 
> underlying FW queue as you suggest. However in theory the interface doesn't 
> make any response order guarantees, but in practice they should be ordered as 
> our BMC doesn't send out-of-order responses.

Can't we put some ID in the response message ? OPAL messages have
room...

Cheers,
Ben.

> Regards,
> 
> Alistair
> 
> > > > I'll look at doing that.  If that is the case, then your NULL check
> > > > for current message should probably be a BUG_ON().
> > > 
> > > OK, I'll update this when the msghandler bit is implemented.
> > > 
> > > > Do you need to handle any BMC flags?  Particularly incoming events?
> > > 
> > > Not at this stage - we may in future though.
> > > 
> > > Cheers,
> > > 
> > > 
> > > Jeremy
> > > _______________________________________________
> > > Linuxppc-dev mailing list
> > > Linuxppc-dev@lists.ozlabs.org
> > > https://lists.ozlabs.org/listinfo/linuxppc-dev
> > 
> > _______________________________________________
> > Linuxppc-dev mailing list
> > Linuxppc-dev@lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2014-11-10  6:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06  3:38 [PATCH 0/2] Add IPMI support for powernv powerpc machines Jeremy Kerr
2014-11-06  3:38 ` [PATCH 2/2] drivers/char/ipmi: Add powernv IPMI driver Jeremy Kerr
2014-11-06  3:38 ` [PATCH 1/2] powerpc/powernv: Add OPAL IPMI interface Jeremy Kerr
2014-11-06 14:15 ` [PATCH 0/2] Add IPMI support for powernv powerpc machines Corey Minyard
2014-11-10  3:26   ` Jeremy Kerr
2014-11-10  5:41     ` Benjamin Herrenschmidt
2014-11-10  6:01       ` Alistair Popple
2014-11-10  6:57         ` Benjamin Herrenschmidt [this message]
2014-11-10  6:41       ` Jeremy Kerr
2014-11-11 21:07     ` Corey Minyard
2014-11-12  6:10   ` Michael Ellerman
2014-11-12  7:37     ` Jeremy Kerr
2014-11-12  7:41     ` [PATCH v2] drivers/char/ipmi: Add powernv IPMI driver Jeremy Kerr
2014-11-14  1:42       ` Corey Minyard
2014-11-14  2:00         ` Jeremy Kerr
2014-11-14  2:04         ` Michael Ellerman

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=1415602628.5769.17.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=alistair@popple.id.au \
    --cc=jk@ozlabs.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=minyard@acm.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 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.