On Thu, Aug 05, 2021, Edgecombe, Rick P wrote: > On Thu, 2021-08-05 at 17:39 +0000, Sean Christopherson wrote: > > If we really want to reduce the memory footprint for the common case (TDP > > MMU), the crud that's used only by indirect shadow pages could be shoved > > into a different struct by abusing the struct layout and and wrapping > > accesses to the indirect-only fields with casts/container_of and helpers, > > e.g. > > > Wow, didn't realize classic MMU was that relegated already. Mostly an > onlooker here, but does TDX actually need classic MMU support? Nice to > have? Gah, bad verbiage on my part. I didn't me _the_ TDP MMU, I meant "MMU that uses TDP". The "TDP MMU" is being enabled by default in upstream, whether or not TDX needs to support the classic/legacy MMU is an unanswered question. From a maintenance perspective, I'd love to say no, but from a "what does Google actually want to use for TDX" perspective, I don't have a defininitive answer yet :-/ > > The role is already factored into the collision logic. > > I mean how aliases of the same gfn don't necessarily collide and the > collisions counter is only incremented if the gfn/stolen matches, but > not if the role is different. Ah. I still think it would Just Work. The collisions tracking is purely for stats, presumably used in the past to see if the hash size was effective. If a hash lookup collides then it should be accounted, _why_ it collided doesn't factor in to the stats. Your comments about the hash behavior being different still stand, though for TDX they wouldn't matter in practice since KVM is hosed if it has both shared and private versions of a shadow page.
