linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dwmw2@infradead.org (David Woodhouse)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] iommu: Kill off pgsize_bitmap field from struct iommu_ops
Date: Wed, 01 Apr 2015 16:46:10 +0200	[thread overview]
Message-ID: <1427899570.22236.14.camel@infradead.org> (raw)
In-Reply-To: <20150401143904.GL1552@arm.com>

On Wed, 2015-04-01 at 15:39 +0100, Will Deacon wrote:
> 
> However, once we have that, we run into the same problem that we've got
> with the current pgsize_bitmap. Namely, that it needs to be a per-domain
> property to avoid it changing dynamically following an initial map request
> or a probe of a new IOMMU device.

That's not so much of a problem, surely? When adding devices to a new
domain without any mappings, the minimum page size of the domain is the
largest of all the IOMMUs participating in that domain.

And if you try to add new devices after you've already started making
mappings, we refuse the addition if it would raise the minimum page size
higher than the page sizes you're already using.

In VT-d we already have very similar logic for superpage and snooping
support.

-- 
dwmw2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5745 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150401/a29d5818/attachment-0001.bin>

  reply	other threads:[~2015-04-01 14:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 17:19 [GIT PULL] iommu: Kill off pgsize_bitmap field from struct iommu_ops Will Deacon
2015-03-31 14:24 ` Joerg Roedel
2015-03-31 14:49   ` Will Deacon
2015-03-31 15:50     ` Alex Williamson
2015-04-01 11:53       ` Will Deacon
2015-04-01 15:53         ` Joerg Roedel
2015-04-01 16:45         ` Alex Williamson
2015-04-01 15:38     ` Joerg Roedel
2015-04-01 17:03       ` Will Deacon
2015-04-01 21:24         ` Joerg Roedel
2015-03-31 16:07   ` Robin Murphy
2015-04-01 13:14 ` David Woodhouse
2015-04-01 13:39   ` Will Deacon
2015-04-01 13:52     ` David Woodhouse
2015-04-01 14:05       ` Will Deacon
2015-04-01 14:28         ` David Woodhouse
2015-04-01 14:39           ` Will Deacon
2015-04-01 14:46             ` David Woodhouse [this message]
2015-04-01 16:36               ` Will Deacon
2015-04-01 21:28                 ` joro at 8bytes.org
2015-04-02  8:58                   ` Will Deacon
2015-04-01 16:51       ` Alex Williamson
2015-04-01 17:50         ` Will Deacon
2015-04-01 18:18           ` Alex Williamson

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=1427899570.22236.14.camel@infradead.org \
    --to=dwmw2@infradead.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).