tree 6569dcf2249c7b81814156d448f1957d7821d97f
parent 788362ce51d45977292e34c28c27d03523b14024
author Vernon Mauery <vernon.mauery@linux.intel.com> 1550266732 -0800
committer Vernon Mauery <vernon.mauery@linux.intel.com> 1555971578 -0700

look up channel from D-Bus connection

With a single IPMI execution queue and multiple bridges, it is important
for the queue to be able to map the incoming D-Bus message to a channel.
Each bridge should request a well-known name of the form
"xyz.openbmc_project.Ipmi.Channel.<name>" where name is the name field
in the /usr/share/ipmi-providers/channel_config.json file.

The mapping is done by registering a name change listener on D-Bus and
then doing some name lookups via the D-Bus interface to match well-known
names to unique names. Then, each incoming messages comes from a
unique-named sender and can be resolved to which channel it came from.

For now, any unmapped channels will show up as INTRABMC, which is not
ideal, but should not break things until the bridges can be converted to
the correct name and D-Bus API.

Tested-by: run ipmid, start and stop bridges named
           xyz.openbmc_project.Ipmi.Channel.<NAME> and see the messages
           show that a new channel has been mapped. Then, with commands
           that use the ipmi::Context, the correct channel shows up.

Change-Id: I3e6bbfbf2e068020e07eeafe64eb09d70c03dc65
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>