> From: Jason Gunthorpe <jgg@xxxxxxxxxx> > Sent: Tuesday, October 10, 2023 7:34 PM > > On Tue, Oct 10, 2023 at 08:42:13AM +0000, Tian, Kevin wrote: > > > From: ankita@xxxxxxxxxx <ankita@xxxxxxxxxx> > > > Sent: Sunday, October 8, 2023 4:23 AM > > > > > > PCI BAR are aligned to the power-of-2, but the actual memory on the > > > device may not. A read or write access to the physical address from the > > > last device PFN up to the next power-of-2 aligned physical address > > > results in reading ~0 and dropped writes. > > > > > > > my question to v10 was not answered. posted again: > > -- > > Though the variant driver emulates the access to the offset beyond > > the available memory size, how does the userspace driver or the guest > > learn to know the actual size and avoid using the invalid hole to hold > > valid data? > > The device FW knows and tells the VM. > This driver reads the size info from ACPI and records it as nvdev->memlength. But nvdev->memlength is not exposed to the userspace. How does the virtual FW acquires this knowledge and then report it to the VM? One option is to indirectly decide the size based on sparse mmap info. But that is kind of a misuse of sparse mmap then such misuse better fits to be a device specific region as Alex suggested. Did I overlook an important fact in the overall picture?
