On Tue, Aug 06, 2024 at 12:43:02PM -0600, Alex Williamson wrote: > > So we don't leak this too much into the drivers? Why should all the > > VFIO drivers have to be changed to alter how their region indexes work > > just to add a single flag?? > I don't know how you're coming to this conclusion. Ideally we'd want to support the WC option basically everywhere. > > I fear we might need to do this as there may not be room in the pgoff > > space (at least for 32 bit) to duplicate everything.... > We'll root out userspace drivers that hard code region offsets in doing > this, but otherwise it shouldn't be an issue. The issue is running out of pgoff bits on 32 bit. Maybe this isn't an issue for VFIO, but it was for RDMA. We needed tight optimal on-demand packing of actual requested mmaps. Allocating gigabytes of address space for possible mmaps ran out of pgoff bits. :\ > How does an "mmap cookie" not duplicate that a device range is > accessible through multiple offsets of the vfio device file? pgoff duplcation is not really an issue, from an API perspective the driver would call a helper to convert the pgoff into a region index and mmap flags. It wouldn't matter to any driver how many duplicates there are. > Well first, we're not talking about a fixed number of additional > regions, we're talking about defining region identifiers for each BAR > with a WC mapping attribute, but at worst we'd only populate > implemented MMIO BARs. But then we've also mentioned that a device > feature could be used to allow a userspace driver to selectively bring > these regions into existence. In an case, an mmap cookie also consumes > address space from the vfio device file, so I'm still failing to see > how calling them a region vs just an mmap cookie makes a substantive > difference. You'd only allocate the mmap cookie when userspace requests it. My original suggestion was to send a flag to REGION_INFO to specifically ask for the different behavior, that (and only that) would return new mmap cookies. The alternative version of this might be to have a single 'GET_REGION_MMAP' that gives a new mmap cookie for a singular specified region index. Userspace would call REGION_INFO to learn the memory regions and then it could call GET_REGION_MMAP(REQ_WC) and will get back a single dynamic mmap cookie that links the WC flags. No system call, no cookie allocation. Existing apps don't start seeing more regions from REGION_INFO. Drivers keep region indexes 1:1 with HW objects. The uAPI has room to add more mmap flags. Jason
