The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: iommu@lists.linux-foundation.org, chegu_vinod@hp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] iommu/intel: Exclude devices using RMRRs from IOMMU API domains
Date: Fri, 13 Jun 2014 15:34:08 +0100	[thread overview]
Message-ID: <1402670048.7595.90.camel@i7.infradead.org> (raw)
In-Reply-To: <20140612163402.9108.50209.stgit@bling.home>

[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]

On Thu, 2014-06-12 at 10:35 -0600, Alex Williamson wrote:
> The user of the IOMMU API domain expects to have full control of
> the IOVA space for the domain.  RMRRs are fundamentally incompatible
> with that idea.  We can neither map the RMRR into the IOMMU API
> domain, nor can we guarantee that the device won't continue DMA with
> the area described by the RMRR as part of the new domain.  Therefore
> we must prevent such devices from being used by the IOMMU API.
> 
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
> 
> I didn't see any actionable items from the last posting of this, so
> re-posting unchanged.

That also wants a Cc:stable, I suppose.

I note we now have two copies of the 'device has RMRR and we actually
care' logic, where the latter clause is really just "is it USB".

Is it worth consolidating that into a macro that's used in both places,
in case the check does get more complicated? Are other devices going to
start getting added to the class of "we don't need the RMRRs to persist
and we *do* want to be able to assign them"... or is that just
needlessly overcomplicating it at this stage?

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5745 bytes --]

  reply	other threads:[~2014-06-13 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 16:35 [RESEND PATCH] iommu/intel: Exclude devices using RMRRs from IOMMU API domains Alex Williamson
2014-06-13 14:34 ` David Woodhouse [this message]
2014-06-13 16:35   ` 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=1402670048.7595.90.camel@i7.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=alex.williamson@redhat.com \
    --cc=chegu_vinod@hp.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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