On 2 October 2015 at 21:28, Christoffer Dall <christoffer.dall@xxxxxxxxxx> wrote: > We discussed this for the purposes of ARM during SFO15 last week, and > basically arrived at the conclusion that the resonable thing to do is to > rely on sysfs device tree parsing in userspace. We don't have a great > solution for ACPI yet, but we also don't know of any ACPI-only devices > that want platform device passthrough yet. I wasn't hugely happy with that approach though: * it's DT specific and just won't work on ACPI platforms; implementing features with a "needs DT" dependency seems like it will come back to bite us later * I don't really want to build in a lot of infrastructure into QEMU to either build the DTC compiler into it or else introduce a runtime dependency on the dtc binary, if this is just going to be a stopgap solution until somebody says "has to work on ACPI" and we need to do it some other way On the other hand I don't exactly have a better approach to suggest (except "don't do device passthrough for platform devices, insist on a real bus like PCI"...) thanks -- PMM _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
