Hi Renier, Thanks for the fast answer. Is it true to say that the HPI Plug-in is single in the system? At the first time of calling to the 'SaHpiSessionOpen()' the HPI Infrastructure calls to the 'open()' HPI plug in only in the first time. What append when 'SaHpiSessionClose()' function calls? Does only in the last time the HPI Infra calls to the 'close()' function to delete the data structure that were created at the first 'open()' function?
Ron Savir SW Engineer, hiD6680 Project, R&D Nokia-Siemens Networks 3 Hanagar St. Neve Ne'eman B Hod Hasharon, Israel Tel: +972-9-775-1631 Mob: +972-54-5524824 [EMAIL PROTECTED] http://www.nokiasiemensnetworks.com/global/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Renier Morales Sent: Thursday, June 19, 2008 17:50 To: [email protected] Subject: Re: [Openhpi-devel] Multiple Session with Multiple Event Queue On Thu, 2008-06-19 at 12:35 +0200, Savir, Ron (NSN - IL/Israel - MiniMD) wrote: > However, when looking at the implementation, we see that whenever > OpenSession() is called, it is translated at the end of the flow to > some function call to the plug-in layer. Not quite. What you are seeing is library initialization, which happens only once inside the first saHpiSessionOpen(). Subsequent saHpiSessionOpen()s will not go down this path. > > This imposes some complex implementation on the HW plug-in (i.e. > creating dedicated event queue for each session opened, and sending > notifications to all of these queues for each HW event). > > I was wondering whether we have some misunderstanding of the Standard, > or whether our understanding of the plug-in responsibility and > implementation is wrong. > > Basically, if we can get some answers and clarifications of what is > required from the plug-in in order to implement multiple sessions, and > if multiple sessions are a must from OpenHPI POV (if not, what is the > preferred way to use it). The plugins absolutely need not worry about sessions or event queues. The OpenHPI infrastructure takes care of that automatically. It supports multiple sessions, each with its own queue as per the HPI spec. >From an infrastructure perspective, the plugin has to implement an open call at a minimum (see plugin abi struct in include/oh_handler.h) and put events in the infrastructure's global queue using oh_evt_queue_push(). --Renier -- Renier Morales IBM Software Engineer kStart Team - Ensemble Manager Toll free: (877) 403-3848 Tie line: 349-8774 [EMAIL PROTECTED] ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
