[Hotplug_sig] Reminder Hotplug SIG Con Call 06/21 11am Pacific

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




This is a reminder and agenda of the HotPlug SIG conference call
tomorrow, Tuesday June 21st 2005 at 11:00am Pacific (2:00pm East Coast).

Phone information:
Toll-Free:1-800-211-0633
Toll:1-719-867-0485
Participant Code: 902493 
 
This is a moderated line. Conference will not start until the moderator
enters with a special pass code.

Agenda:

* Discussion on the hotplug CPU test cases (update/revisit), please look
at 
http://developer.osdl.org/dev/hotplug/documentation/cpu_test_cases.php
and
http://developer.osdl.org/maryedie/HOTPLUG/planning/hotplug_cpu_test_pla
n_status.html

* Discussion on OpenHPI's ability to control in addition to monitoring.
We'll use Renier's input as a starting point to the discussion:
"OpenHPI, being an implementation of the HPI spec, provides both control
and monitoring (through sensors) intefaces to hardware as described in
the HPI spec.  The best way to learn which sensors and controls are
available (in an ipmi system, for example) is to install openhpi and run
the hpitree clients. This will show all sensors and controls (and then
some) that the plugin has detected on that hardware. 
Managed hotswap is implemented and handled in OpenHPI. There are two
ways, depending on the plugin, that this is managed. This is described
in the spec. The ipmi plugins use the full hotswap state model. The
BladeCenter plugin uses the simplified hotswap state model. Both models
are valid and compliant with the HPI spec. 

When you talk about hotswap in HPI, you are talking about hotswap
events. So the HPI user receives hotswap events, and if the
corresponding resource supports the full hotswap model, it can intervene
in some ways on the hotswap cycle that that resource is going through.
Inherently, there is no command that the user must type to access these
events. OpenHPI is a library (an API), so a user application links to
OpenHPI and invokes the API to query the state of things and events
(including hotswap events)."

* Status of memory testing plan
* Last meeting's ARs
* Other topics: do we need to discuss what num CPUs to use for things
like top?

Thanks for your participation. 
Martine J. Silbermann








[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux