From: ohaugan@codeaurora.org (Olav Haugan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/1] iommu-api: Add map_sg/unmap_sg functions
Date: Tue, 12 Aug 2014 09:56:11 -0700 [thread overview]
Message-ID: <53EA472B.3020900@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGvZUanVtPxAt76+AAdOaNwyMJ3cmcJ1srsEYBeG7ELkBQ@mail.gmail.com>
On 8/12/2014 3:48 AM, Rob Clark wrote:
> On Mon, Aug 11, 2014 at 9:51 PM, Hiroshi Doyu <hdoyu@nvidia.com> wrote:
>> Hi Olav,
>>
>> Olav Haugan <ohaugan@codeaurora.org> writes:
>>
>>> @@ -93,6 +94,10 @@ enum iommu_attr {
>>> * @detach_dev: detach device from an iommu domain
>>> * @map: map a physically contiguous memory region to an iommu domain
>>> * @unmap: unmap a physically contiguous memory region from an iommu domain
>>> + * @map_sg: map a scatter-gather list of physically contiguous memory chunks
>>> + * to an iommu domain
>>> + * @unmap_sg: unmap a scatter-gather list of physically contiguous memory
>>> + * chunks from an iommu domain
>>> * @iova_to_phys: translate iova to physical address
>>> * @domain_has_cap: domain capabilities query
>>> * @add_device: add device to iommu grouping
>>> @@ -110,6 +115,11 @@ struct iommu_ops {
>>> phys_addr_t paddr, size_t size, int prot);
>>> size_t (*unmap)(struct iommu_domain *domain, unsigned long iova,
>>> size_t size);
>>> + int (*map_sg)(struct iommu_domain *domain, unsigned long iova,
>>> + struct scatterlist *sg, unsigned int nents, int prot,
>>> + unsigned long flags);
>>> + int (*unmap_sg)(struct iommu_domain *domain, unsigned long iova,
>>> + size_t size, unsigned long flags);
>>
>> Do you have any exmaple/explanation for the above "flags"?
>>
>> Is this going to be used for iommu global/standard attribute or SoC
>> spcific one?
>
> iirc, one plan for 'flags' was some sort of DONT_FLUSH_TLB flag for
> drivers which wanted to map/unmap N buffers with a single flush at the
> end. There might have been some other usages envisioned.
>
Yes, that was the original intent of the flags for now. I am sure we can
find other uses for this in the future.
Thanks,
Olav
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-08-12 16:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 22:45 [PATCH v5 0/1] Add iommu map_sg/unmap_sg API Olav Haugan
2014-08-11 22:45 ` [PATCH v5 1/1] iommu-api: Add map_sg/unmap_sg functions Olav Haugan
2014-08-12 1:35 ` Konrad Rzeszutek Wilk
2014-08-12 16:53 ` Olav Haugan
2014-08-12 1:51 ` Hiroshi Doyu
2014-08-12 10:48 ` Rob Clark
2014-08-12 16:56 ` Olav Haugan [this message]
2014-08-18 14:07 ` joro at 8bytes.org
2014-08-18 18:32 ` Rob Clark
2014-08-18 20:48 ` Olav Haugan
2014-08-18 21:26 ` joro at 8bytes.org
2014-08-18 21:32 ` Olav Haugan
2014-08-12 16:55 ` Laurent Pinchart
2014-08-12 17:10 ` Olav Haugan
2014-08-18 21:55 ` Joerg Roedel
2014-08-18 22:47 ` Olav Haugan
2014-08-19 11:59 ` Joerg Roedel
2014-08-19 16:11 ` Laurent Pinchart
2014-08-19 18:40 ` Olav Haugan
2014-08-19 20:52 ` Laurent Pinchart
2014-08-20 5:21 ` Thierry Reding
2014-08-20 13:02 ` Konrad Rzeszutek Wilk
2014-08-20 14:15 ` Laurent Pinchart
2014-08-19 18:37 ` Olav Haugan
2014-09-25 17:01 ` Joerg Roedel
2014-10-06 19:02 ` Olav Haugan
2014-10-15 9:16 ` Thierry Reding
2014-10-16 17:23 ` Olav Haugan
2014-10-17 9:09 ` Joerg Roedel
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=53EA472B.3020900@codeaurora.org \
--to=ohaugan@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).