lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 21 Apr 2010 15:03:21 -0500
From:	Corey Minyard <minyard@....org>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	openipmi-developer@...ts.sourceforge.net, bjorn.helgaas@...com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] ipmi: Only register one si per bmc

Matthew Garrett wrote:
> On Wed, Apr 21, 2010 at 01:09:45PM -0500, Corey Minyard wrote:
>
>   
>> If I understand this correctly, this would really be "Only register one  
>> si per system".  Unfortunately, there are systems that have more than  
>> one BMC each with their own interface.
>>     
>
> The spec explicitly says that while a system may have multiple BMCs, 
> only one BMC may respond to GetDeviceID (6.11 of the 2.0 spec). Is the 
> real world irritatingly incompatible with this?
>   
That section is quite misleading.  There may be management controllers 
that are not BMCs, and they may have system interfaces.  There may only 
be on BMC in a system, though, per the spec.  That really has more to do 
with event handling and the main SDR repository, though.

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".

-corey
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ