Re: Full-time developer available

[Robert Millan]

Hi Samuel,

El 17/09/15 a les 17:35, Samuel Thibault ha escrit:
> For me, the idea could be that you run a rump translator per PCI device,

That doesn't fit very well with the way Rump works. With Rump you select
drivers rather than specific devices. So for example if you start a Rump
instance and load the librumpdev_pci_auich driver, auich driver scans the
PCI bus for ICH audio devices and registers them as /dev/audio* in the
internal vfs namespace of this instance.

As for the rest of PCI devices, AFAICT they're free to be used by whoever
wants them. My understanding is there's no need for an arbiter / multiplexer
as long as all the code playing with PCI devices is well-aware of its limits.

> We'd need a common PCI translator to multiplex accesses to the config space,

Rump accesses the PCI config space using libpciaccess. Are there coherency 
issues
with separate processes doing this concurrently? AFAIK it shouldn't be a problem
because hardware-mapped memory is excluded from processor caches.

--
Robert Millan