Right, src/event.c is the file to look at plus any instance of
oh_evt_queue_push() at the plugin. Plugins use oh_evt_queue_push() to push
resource events (which contain the rpt entry) into the core library's
processing queue. The core library takes the event from there and adds it
to the domain's RPT if appropiate.
Saludos,
--Renier
[EMAIL PROTECTED] wrote on 10/18/2007 10:01:57
AM:
>
> Addition and removal of resources in the "real" RPT is done through
> SAHPI_ET_HOTSWAP events - see process_resource_events() function in
> src/event.c file.
>
> Pierre
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
[mailto:openhpi-devel-
> > [EMAIL PROTECTED] On Behalf Of Audet, Jean-Michel
> > Sent: Thursday, October 18, 2007 15:54
> > To: [email protected]
> > Subject: [Openhpi-devel] rpt table in openhpid vs rptcache in
> > ipmidirectplugin
> >
> > Hi,
> > I have a hard time to understand how the RPT entry gets into the
> > "rpt" table.
> >
> > If I follow the code from the discovery of resources, found that, upon
> > discovery of a new IPMC from the ipmidirect plugin, a new resource
(RPT
> > Entry) is added to the "rptcache" within the ipmidirect plugin.
> >
> > If I follow the code from the call to saHpiRptEntryGet, I found that
the
> > code search (hash) through the RPT list "rpt". However, I cannot
found
> > where the transfer of RPT is made from the openhpid "rpt" list to the
> > ipmidirect "rptcache" list. It looks like it is not the same list
since
> > memory is allocated for each list.
> >
> > ipmidirect rptcache is probably a copy in memory for faster access to
> > rpt but my question is:
> >
> > How the rpt is transferred (synchronise) between the "real" rpt and
the
> > ipmidirect plugin rpt "cache"?
> >
> > Thanks for helping me understand this!
> >
> > Jean-Michel Audet
> >
> >
-------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a
browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Openhpi-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel
>
>
>
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Openhpi-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openhpi-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
