From: Jason Gunthorpe <jgg@ziepe.ca>
To: Wencheng Yang <east.moutain.yang@gmail.com>
Cc: alex.williamson@redhat.com, iommu@lists.linux.dev,
joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, robin.murphy@arm.com,
suravee.suthikulpanit@amd.com, will@kernel.org
Subject: Re: [PATCH v3 1/3] uapi/linux/vfio:Add VFIO_DMA_MAP_FLAG_MMIO flag
Date: Tue, 21 Jan 2025 10:05:53 -0400 [thread overview]
Message-ID: <20250121140553.GP674319@ziepe.ca> (raw)
In-Reply-To: <20250121112836.525046-1-east.moutain.yang@gmail.com>
On Tue, Jan 21, 2025 at 07:28:34PM +0800, Wencheng Yang wrote:
> The flag will be used by VFIO to map DMA for device MMIO on IOMMU page table.
Definitely not, the kernel needs to know and protect the memory type
itself. Userspace cannot be allowed to override things
Jason
next prev parent reply other threads:[~2025-01-21 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 7:14 [PATCH v2] drviers/iommu/amd: support P2P access through IOMMU when SME is enabled Wencheng Yang
2025-01-17 13:44 ` Alex Williamson
2025-01-21 11:07 ` Wencheng Yang
2025-01-21 11:28 ` [PATCH v3 1/3] uapi/linux/vfio:Add VFIO_DMA_MAP_FLAG_MMIO flag Wencheng Yang
2025-01-21 11:28 ` [PATCH v3 2/3] vfio/vfio_iommu_type1:convert VFIO_DMA_MAP_FLAG_MMIO to IOMMU_MMIO flag Wencheng Yang
2025-01-21 11:28 ` [PATCH v3 3/3] iommu/amd:Clear encryption bit if the mapping is for device MMIO Wencheng Yang
2025-01-21 14:05 ` Jason Gunthorpe [this message]
2025-01-21 15:34 ` [PATCH v2] drviers/iommu/amd: support P2P access through IOMMU when SME is enabled Alex Williamson
2025-01-21 20:47 ` Jason Gunthorpe
2025-01-20 13:59 ` Jason Gunthorpe
2025-01-21 9:27 ` Wencheng Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250121140553.GP674319@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alex.williamson@redhat.com \
--cc=east.moutain.yang@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox