On Tue, 2025-09-16 at 22:06 +0200, Thomas Hellström wrote: > On Mon, 2025-09-15 at 00:21 -0700, Vivek Kasireddy wrote: > > To properly import a dmabuf that is associated with a VF (or that > > originates in a Guest VM that includes a VF), we need to know where > > in LMEM the VF's allocated regions exist. Therefore, introduce a > > new helper to return the object that backs the VF's regions in > > LMEM. > > > > v2: > > - Make the helper return the LMEM object instead of the start > > address > > > > v3: > > - Move the declaration of the helper under other lmem helpers > > (Michal) > > In XeKMD we're typically using VRAM instead of LMEM, IMO we should > try > to be consistent with this.
I actually notice that most of the SRIOV code uses LMEM instead of VRAM, so I discussed with the other maintainers what would be the best way moving forward here. So if you could try as a general rule to avoid using "lmem" in other files than the SRIOV files. Also if SRIOV functions or variable names or fields mandate it, "lmem" is OK. But in other files, functions and variable names, pleas use VRAM. Thanks, Thomas
