[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251107155704.GM1732817@nvidia.com>
Date: Fri, 7 Nov 2025 11:57:04 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Wei Wang <wei.w.wang@...mail.com>
Cc: "alex@...zbot.org" <alex@...zbot.org>,
"suravee.suthikulpanit@....com" <suravee.suthikulpanit@....com>,
"thomas.lendacky@....com" <thomas.lendacky@....com>,
"joro@...tes.org" <joro@...tes.org>,
"kevin.tian@...el.com" <kevin.tian@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>
Subject: Re: [PATCH v2 2/2] vfio/type1: Set IOMMU_MMIO in dma->prot for
MMIO-backed addresses
On Fri, Nov 07, 2025 at 03:49:17PM +0000, Wei Wang wrote:
> > (are you aware of any real examples in use?)
> > VM_IO should indicate MMIO, yes, but we don't actually check that in
> > this type 1 path..
> Is it because VFIO type1 didn’t need to check for MMIO before?
> (not sure how this impacts this patch adding the VM_IO check for MMIO
> :) )
Okay, but it still doesn't mean it has to be decrypted..
Jason
Powered by blists - more mailing lists