On Tue, 2025-07-08 at 08:29 -0700, Vishal Annapurve wrote: > > The original seamcall wrapper patches used "u64 hpa", etc everywhere. The > > feedback was that it was too error prone to not have types. We looked at > > using > > kvm types (hpa_t, etc), but the type checking was still just surface level > > [0]. > > > > So the goal is to reduce errors and improve code readability. We can > > consider > > breaking symmetry if it is better that way. In this case though, why not use > > struct folio? > > My vote would be to prefer using "hpa" and not rely on folio/page > structs for guest_memfd allocated memory wherever possible. Is this because you want to enable struct page-less gmemfd in the future? Or other reason?
