On Tue, Jul 15, 2014 at 8:04 PM, Jerome Glisse <j.glisse@xxxxxxxxx> wrote: >> Yes although it can be skipped on most systems. We figured that topology >> needed to cover everything that would be handled by a single OS image, so >> in a NUMA system it would need to cover all the CPUs. I think that is still >> the right scope, do you agree ? > > I think it is a idea to duplicate cpu. I would rather have each device > give its afinity against each cpu and for cpu just keep the existing > kernel api that expose this through sysfs iirc. It's all there already if we fix up the hsa dev-node model to expose one dev node per underlying device instead of one for everything: - cpus already expose the full numa topology in sysfs - pci devices have a numa_node file in sysfs to display the link - we can easily add similar stuff for platform devices on arm socs without pci devices. Then the only thing userspace needs to do is follow the device link in the hsa instance node in sysfs and we have all the information exposed. Iff we expose one hsa driver instance to userspace per physical device (which is the normal linux device driver model anyway). I don't see a need to add anything hsa specific here at all (well maybe some description of the cache architecture on the hsa device itself, the spec seems to have provisions for that). -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
