All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Olav Haugan <ohaugan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	will.deacon-5wv7dgnIgG8@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Thierry Reding
	<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2 1/1] iommu-api: Add map_range/unmap_range functions
Date: Thu, 24 Jul 2014 11:34:27 +0200	[thread overview]
Message-ID: <20140724093427.GH14017@8bytes.org> (raw)
In-Reply-To: <53CFF5C3.5060600-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>

On Wed, Jul 23, 2014 at 10:49:55AM -0700, Olav Haugan wrote:
> Joerg, can you comment on what you envisioned when you suggested that we
> add the fallback?
> 

The problem is that we already have tons of IOMMU drivers in the tree
which don't provide these call-backs. So adding this API extension
without a fall-back that works for these drivers too would fragment the
functionality between different IOMMU drivers in an inacceptable way and
undermine the purpose of a generic API.


	Joerg

  parent reply	other threads:[~2014-07-24  9:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  1:01 [PATCH v2 0/1] Add iommu map_range/unmap_range calls Olav Haugan
2014-07-17  1:01 ` [PATCH v2 1/1] iommu-api: Add map_range/unmap_range functions Olav Haugan
     [not found]   ` <1405558917-7597-2-git-send-email-ohaugan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-17  8:21     ` Thierry Reding
2014-07-22  0:59       ` Olav Haugan
     [not found]         ` <53CDB76A.5090602-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-22  7:45           ` Thierry Reding
2014-07-23 17:49             ` Olav Haugan
     [not found]               ` <53CFF5C3.5060600-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-24  9:34                 ` Joerg Roedel [this message]
     [not found]                   ` <20140724093427.GH14017-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-07-24 10:07                     ` Thierry Reding
2014-07-24 10:14                 ` Thierry Reding
2014-07-22 15:07         ` Rob Clark

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=20140724093427.GH14017@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ohaugan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=will.deacon-5wv7dgnIgG8@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.