[lkml]   [2024]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 08/16] KVM: x86/mmu: Bug the VM if kvm_zap_gfn_range() is called for TDX
    On Wed, 2024-05-15 at 09:02 -0700, Sean Christopherson wrote:
    > > Or most specifically, we only need this zapping if we *try* to have
    > > consistent
    > > cache attributes between private and shared. In the non-coherent DMA case we
    > > can't have them be consistent because TDX doesn't support changing the
    > > private
    > > memory in this way.
    > Huh?  That makes no sense.  A physical page can't be simultaneously mapped
    > SHARED
    > and PRIVATE, so there can't be meaningful cache attribute aliasing between
    > private
    > and shared EPT entries.
    > Trying to provide consistency for the GPA is like worrying about having
    > matching
    > PAT entires for the virtual address in two different processes.

    No, not matching between the private and shared mappings of the same page. The
    whole private memory will be WB, and the whole shared half will honor PAT.
     \ /
      Last update: 2024-05-15 18:13    [W:5.915 / U:0.040 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site