On Tue, Jul 19, 2022 at 01:25:14PM -0600, Alex Williamson wrote: > > We don't really expect user space to hit this limit, the RAM in QEMU is > > divided today to around ~12 ranges as we saw so far in our evaluation. > > There can be far more for vIOMMU use cases or non-QEMU drivers. Not really, it isn't dynamic so vIOMMU has to decide what it wants to track up front. It would never make sense to track based on what is currently mapped. So it will be some small list, probably a big linear chunk of the IOVA space. No idea why non-qemu cases would need to be so different? > We're looking at a very narrow use case with implicit assumptions about > the behavior of the user driver. Some of those assumptions need to be > exposed via the uAPI so that userspace can make reasonable choices. I think we need to see a clear use case for more than a few 10's of ranges before we complicate things. I don't see one. If one does crop up someday it is easy to add a new query, or some other behavior. Remember, the devices can't handle huge numbers of ranges anyhow, so any userspace should not be designed to have more than a few tens in the first place. Jason
