public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/1] iommu-api: Add map_sg/unmap_sg functions
Date: Wed, 15 Oct 2014 11:16:53 +0200	[thread overview]
Message-ID: <20141015091652.GB13162@ulmo> (raw)
In-Reply-To: <5432E757.10201@codeaurora.org>

On Mon, Oct 06, 2014 at 12:02:47PM -0700, Olav Haugan wrote:
> On 9/25/2014 10:01 AM, Joerg Roedel wrote:
> >On Mon, Aug 11, 2014 at 03:45:50PM -0700, Olav Haugan wrote:
> >>+static inline int iommu_map_sg(struct iommu_domain *domain, unsigned long iova,
> >>+			       struct scatterlist *sg, unsigned int nents,
> >>+			       int prot, unsigned long flags)
> >>+{
> >>+	return domain->ops->map_sg(domain, iova, sg, nents, prot, flags);
> >>+}
> >>+
> >>+static inline int iommu_unmap_sg(struct iommu_domain *domain,
> >>+				 unsigned long iova, size_t size,
> >>+				 unsigned long flags)
> >>+{
> >>+	return domain->ops->unmap_sg(domain, iova, size, flags);
> >>+}
> >
> >I have thought a little bit more about this interface and think that it
> >would be better to just return a size_t from iommu_map_sg().  The
> >function returns the amount of address space mapped by it, 0 in the
> >worst case.
> >
> >This makes it easy to unmap the region just with
> >iommu_unmap(domain, iova, size) in the end and removing the need for a
> >new iommu_unmap_sg() function. Also the error-path of the map_sg
> >call-backs becomes easier as the function then just returns the amount
> >of address-space already mapped before the error happened.
> >
> >So the prototype would be:
> >
> >	size_t iommu_map_sg(struct iommu_domain *domain,
> >			    unsigned long iova,
> >			    struct scatterlist *sg,
> >			    unsigned int nents,
> >			    int prot);
> >
> >(as I said before, the flags parameter should not be added by this
> >  patch-set).
> >
> 
> Ok, sounds good. I'll post v6 soon.

Perhaps make the return value ssize_t so that we can propagate errors?

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141015/7248bdde/attachment-0001.sig>

  reply	other threads:[~2014-10-15  9:16 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
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 [this message]
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=20141015091652.GB13162@ulmo \
    --to=thierry.reding@gmail.com \
    --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