From: Robin Murphy <robin.murphy@arm.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Christoph Hellwig <hch@infradead.org>
Cc: kevin.tian@intel.com, mika.westerberg@linux.intel.com,
ashok.raj@intel.com, alan.cox@intel.com,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
pengfei.xu@intel.com, jacob.jun.pan@intel.com,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v1 4/9] iommu/vt-d: Add bounce buffer API for domain map/unmap
Date: Tue, 19 Mar 2019 11:21:35 +0000 [thread overview]
Message-ID: <04703ea4-58e5-f833-5b39-1b68df2839ca@arm.com> (raw)
In-Reply-To: <c1ffee0a-24d2-df53-0689-23b0d8ef065d@linux.intel.com>
On 19/03/2019 07:59, Lu Baolu wrote:
> Hi Christoph,
>
> On 3/14/19 12:10 AM, Christoph Hellwig wrote:
>> On Wed, Mar 13, 2019 at 10:31:52AM +0800, Lu Baolu wrote:
>>> Hi again,
>>>
>>> On 3/13/19 10:04 AM, Lu Baolu wrote:
>>>> Hi,
>>>>
>>>> On 3/13/19 12:38 AM, Christoph Hellwig wrote:
>>>>> On Tue, Mar 12, 2019 at 02:00:00PM +0800, Lu Baolu wrote:
>>>>>> This adds the APIs for bounce buffer specified domain
>>>>>> map() and unmap(). The start and end partial pages will
>>>>>> be mapped with bounce buffered pages instead. This will
>>>>>> enhance the security of DMA buffer by isolating the DMA
>>>>>> attacks from malicious devices.
>>>>>
>>>>> Please reuse the swiotlb code instead of reinventing it.
>>>>>
>>>
>>> Just looked into the code again. At least we could reuse below
>>> functions:
>>>
>>> swiotlb_tbl_map_single()
>>> swiotlb_tbl_unmap_single()
>>> swiotlb_tbl_sync_single()
>>>
>>> Anything else?
>>
>> Yes, that is probably about the level you want to reuse, given that the
>> next higher layer already has hooks into the direct mapping code.
>>
>
> I am trying to change my code to reuse swiotlb. But I found that swiotlb
> might not be suitable for my case.
>
> Below is what I got with swiotlb_map():
>
> phy_addr size tlb_addr
> --------------------------------
> 0x167eec330 0x8 0x85dc6000
> 0x167eef5c0 0x40 0x85dc6800
> 0x167eec330 0x8 0x85dc7000
> 0x167eef5c0 0x40 0x85dc7800
>
> But what I expected to get is:
>
> phy_addr size tlb_addr
> --------------------------------
> 0x167eec330 0x8 0xAAAAA330
> 0x167eef5c0 0x40 0xBBBBB5c0
> 0x167eec330 0x8 0xCCCCC330
> 0x167eef5c0 0x40 0xDDDDD5c0
>
> , where 0xXXXXXX000 is the physical address of a bounced page.
>
> Basically, I want a bounce page to replace a leaf page in the vt-d page
> table, which maps a buffer with size less than a PAGE_SIZE.
I'd imagine the thing to do would be to factor out the slot allocation
in swiotlb_tbl_map_single() so that an IOMMU page pool/allocator can be
hooked in as an alternative.
However we implement it, though, this should absolutely be a common
IOMMU thing that all relevant DMA backends can opt into, and not
specific to VT-d. I mean, it's already more or less the same concept as
the PowerPC secure VM thing.
Robin.
next prev parent reply other threads:[~2019-03-19 11:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 5:59 [PATCH v1 0/9] Bounce buffer for untrusted devices Lu Baolu
2019-03-12 5:59 ` [PATCH v1 1/9] iommu/vt-d: Add trace events for domain map/unmap Lu Baolu
2019-03-12 5:59 ` [PATCH v1 2/9] iommu/vt-d: Add helpers for domain mapping/unmapping Lu Baolu
2019-03-12 5:59 ` [PATCH v1 3/9] iommu/vt-d: Add address walk helper Lu Baolu
2019-03-12 6:00 ` [PATCH v1 4/9] iommu/vt-d: Add bounce buffer API for domain map/unmap Lu Baolu
2019-03-12 16:38 ` Christoph Hellwig
2019-03-13 2:04 ` Lu Baolu
2019-03-13 2:31 ` Lu Baolu
2019-03-13 16:10 ` Christoph Hellwig
2019-03-14 1:01 ` Lu Baolu
2019-03-19 7:59 ` Lu Baolu
2019-03-19 11:21 ` Robin Murphy [this message]
2019-03-12 6:00 ` [PATCH v1 5/9] iommu/vt-d: Add bounce buffer API for dma sync Lu Baolu
2019-03-12 6:00 ` [PATCH v1 6/9] iommu/vt-d: Check whether device requires bounce buffer Lu Baolu
2019-03-12 6:00 ` [PATCH v1 7/9] iommu/vt-d: Add dma sync ops for untrusted devices Lu Baolu
2019-03-12 6:00 ` [PATCH v1 8/9] iommu/vt-d: Flush IOTLB for untrusted device in time Lu Baolu
2019-03-12 6:00 ` [PATCH v1 9/9] iommu/vt-d: Use bounce buffer for untrusted devices Lu Baolu
2019-03-12 6:07 ` [PATCH v1 0/9] Bounce " Lu Baolu
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=04703ea4-58e5-f833-5b39-1b68df2839ca@arm.com \
--to=robin.murphy@arm.com \
--cc=alan.cox@intel.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pengfei.xu@intel.com \
/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
all inboxes | Powered by JetHome®