[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9cfe6042-f0fb-ea5e-e134-f6f5bb9eb7b0@linux.intel.com>
Date: Tue, 24 Sep 2019 09:38:53 +0800
From: Lu Baolu <baolu.lu@...ux.intel.com>
To: "Raj, Ashok" <ashok.raj@...el.com>
Cc: baolu.lu@...ux.intel.com, Joerg Roedel <joro@...tes.org>,
David Woodhouse <dwmw2@...radead.org>,
Alex Williamson <alex.williamson@...hat.com>,
sanjay.k.kumar@...el.com, jacob.jun.pan@...ux.intel.com,
kevin.tian@...el.com, yi.l.liu@...el.com, yi.y.sun@...el.com,
iommu@...ts.linux-foundation.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Yi Sun <yi.y.sun@...ux.intel.com>
Subject: Re: [RFC PATCH 2/4] iommu/vt-d: Add first level page table interfaces
Hi Ashok,
On 9/24/19 4:31 AM, Raj, Ashok wrote:
> On Mon, Sep 23, 2019 at 08:24:52PM +0800, Lu Baolu wrote:
>> This adds functions to manipulate first level page tables
>> which could be used by a scalale mode capable IOMMU unit.
>
> s/scalale/scalable
Yes.
>
>>
>> intel_mmmap_range(domain, addr, end, phys_addr, prot)
>
> Maybe think of a different name..? mmmap seems a bit weird :-)
Yes. I don't like it either. I've thought about it and haven't
figured out a satisfied one. Do you have any suggestions?
Best regards,
Baolu
>
>> - Map an iova range of [addr, end) to the physical memory
>> started at @phys_addr with the @prot permissions.
>>
>> intel_mmunmap_range(domain, addr, end)
>> - Tear down the map of an iova range [addr, end). A page
>> list will be returned which will be freed after iotlb
>> flushing.
>>
>> Cc: Ashok Raj <ashok.raj@...el.com>
>> Cc: Jacob Pan <jacob.jun.pan@...ux.intel.com>
>> Cc: Kevin Tian <kevin.tian@...el.com>
>> Cc: Liu Yi L <yi.l.liu@...el.com>
>> Cc: Yi Sun <yi.y.sun@...ux.intel.com>
>> Signed-off-by: Lu Baolu <baolu.lu@...ux.intel.com>
>
Powered by blists - more mailing lists