Excellent, that would be good to give the OpenHPI project more exposure to the whole group. Martine -----Original Message----- From: Mary Edie Meredith [mailto:maryedie@xxxxxxxx] Sent: Thursday, March 31, 2005 11:56 AM To: Silbermann, Martine Cc: hotplug_sig@xxxxxxxxxxxxxx Subject: Re: [Hotplug_sig] FW: MINUTES for Hotplug SIG Con Call 03/29 On Wed, 2005-03-30 at 12:46, Silbermann, Martine wrote: > Summary list of ARs from this meeting: > AR for Mary: > 1. Send to this list the outline recommended to write the use cases and > as an example the use case on PSDN (Persistent Storage Device Naming). See previous email on list. > 2. Send a copy of Chris' presentation on Virtualization to the list. http://www.finux.org/Reprints/Reprint-Wright-OLS2004.pdf (Note to Martine: this one above replaces the one I mailed you earlier.) I'm also working to reserve a few minutes at the next Joint OSDL Working Group Face to Face mid-May to show the OpenHPI support matrix if it is available by then. > ################################# > > Attendees: > Joel Schopp, IBM > Renier Morales, IBM > Mary Meredith, OSDL > Mark Wong, OSDL > Natalie Protasevich, Unisys > Bruce Vessey, Unisys > Martine Silbermann, HP > > > * CPU hotplug testing > We reviewed Mark's scripts. The following comments and suggestions > were > made: > - there should be a check on the status of the CPU to make sure > that it was indeed taken offline, > - add a test that checks that if the CPU should not be allowed > to be taken offline that the return status is failed, > - after confirmation that the CPU was taken offline, make sure > that the process was actually migrated to another CPU > - add tests on affinity checking > - run the scripts in a loop to make sure that no "accumulative" > effect creates a problem. > > Mark ran the scripts against the latest kernel (no against Dave's > patches) on a ppc, the scripts ran fine. > AR for Mark: update the scripts to include suggestions and run them on > the latest kernel and on Dave patches (those submitted up to mm and > those in his own tree). Mark tried to run the database test on Dave's > patches but it crashed and mark could not retrieve significant info to > share the problem w/ the community. He'll keep working on the problem > to get enough info to share w/ developers. > Natalie hasn't gotten any feedback on her patches from the small set of > reviewers she sent it to. > AR for Natalie: Post her CPU hotplug patches on this list to get > feedback from this group. > > * Use Case for Virtualization. > OSDL has identified use cases as a useful vehicle to communicate needs > and requirements to the community. The SIG is considering writing a > use case on Hotplug for Virtualization. Bruce offered to help on > writing the use case. > AR for Mary: Send to this list the outline recommended to write the use > cases and as an example the use case on PSDN (Persistent Storage Device > Naming). > Chris Wright made a presentation on Virtualization from a security > point-of-view. Some of it may be useful to get the use case started. > AR for Mary: Send a copy of Chris' presentation on Virtualization to the > list. > Martine asked if any other topics would be appropriate to generate a use > case and Mary suggested "hotplug from a management point-of-view" > AR to everyone: Send mail to the list if you're interested in a use case > on "hotplug from a management point-of-view". (Rest reassured that > showing interest does NOT equate to volunteering yourself to do the work > ....HOWEVER if you'd like to volunteer you'll be more then welcome :-) > > * Hotplug memory > Dave has submitted a set of patches and has asked for feedback on the > linux-mm@xxxxxxxxx list. Those patches are mostly changes linked to > SPARSEMEM. Not much reaction from the community so far. > On the testing side Mark hasn't had time to work on the latest patches. > AR for Mark: Compile, boot and run the tests using Dave latest patches > submitted (those submitted up to mm and those in his own tree). > Martine shared the list of topics that Dave proposed for LKS, there was > no additional proposal from the SIG members. > AR for everyone: Suggestions for LKS topics are still taken and welcome. > > * Hotplug SIG website update and new wiki > Martine is currently working on changing and adding to the content of > the Hotplug SIG homepage. The new wiki is accessible to everyone (as > long as you remember to use the magic word "hotplug") and is used to > list special test cases and/or edge cases. AR for Martine: Send Mary a > set of changes including terminology and project definition and > updates. > > * OpenHPI update > Renier gave us a brief update on what's been happening with OpenHPI. By > the end of this month (3/31) version 2.1.0 should be released, it > provides many bug fixed and some enhanced ATCA support with IPMI and > IPMIDirect plug-ins. > The wiki now provides a release schedule for OpenHPI, see > http://wiki.openhpi.org/OpenHPIReleaseSchedule and the documentation has > been growing, see http://wiki.openhpi.org/OpenHPI > We asked if it would be possible to have a list of architectures that > OpenHPI supports as well as list of features that are selectively > supported on some architectures (which archs support what pluggins into > HPI?) > AR for Renier: Ask Sean Dague to create a wiki page that would have the > above mentioned info. This would help promote OpenHPI and encourage > people to build pluggins for OpenHPI to fill in their specific needs. > > Next meeting is scheduled for April 12th at 11:00am -12:00pm PST, > 2:00pm > - 3:00pm EST > > Thanks for your participation. > Martine J. Silbermann > > > > > > > > > > > ______________________________________________________________________ > _______________________________________________ > Hotplug_sig mailing list > Hotplug_sig@xxxxxxxxxxxxxx > http://lists.osdl.org/mailman/listinfo/hotplug_sig -- Mary Edie Meredith maryedie@xxxxxxxx 503-906-1942 Open Source Development Labs
