public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Corey Minyard <minyard@acm.org>
Cc: openipmi-developer@lists.sourceforge.net, bjorn.helgaas@hp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] ipmi: Only register one si per bmc
Date: Wed, 21 Apr 2010 21:10:48 +0100	[thread overview]
Message-ID: <20100421201048.GA25030@srcf.ucam.org> (raw)
In-Reply-To: <4BCF5A09.80404@acm.org>

On Wed, Apr 21, 2010 at 03:03:21PM -0500, Corey Minyard wrote:

> However, IBM makes some systems that can plug together for scalability.   
> Each individual system has a BMC, and when you plug them together into  
> an SMP system, all the BMCs are still there.  At least that's how I  
> understand it.  I'm not sure if the other BMCs become satellite MCs in  
> that case, which would be legit, sort of.  So I guess the answer to you  
> question would be: "Yes, the world is not compatible with the spec".

Hm. Ok. In that case we seem to be in a difficult position - we're not 
supposed to register multiple SIs per BMC, but we're also not supposed 
to send anything other than GetDeviceID to an SI before we decide to use 
it. The options here would seem to be to disambiguate by either 
registering all SIs of a type (on the assumption that if we have 
multiple BMCs, they'll all present their SIs in the same way, and we 
won't have multiple SIs of the same type if we don't have multiple 
BMCs), or taking a risk on that bit of the spec by getting the GUID for 
each SI.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

      reply	other threads:[~2010-04-21 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 18:40 [PATCH 1/3] ipmi: Split device discovery and registration Matthew Garrett
2010-04-20 18:40 ` [PATCH 2/3] ipmi: Only register one si per bmc Matthew Garrett
2010-04-20 18:40   ` [PATCH 3/3] ipmi: Change device discovery order Matthew Garrett
2010-04-21 18:09   ` [PATCH 2/3] ipmi: Only register one si per bmc Corey Minyard
2010-04-21 18:21     ` Matthew Garrett
2010-04-21 20:03       ` Corey Minyard
2010-04-21 20:10         ` Matthew Garrett [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=20100421201048.GA25030@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox