mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Derrick <jonathan.derrick@intel.com>
To: Robin Murphy <robin.murphy@arm.com>,
	linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Keith Busch <keith.busch@intel.com>,
	Bjorn Helgaas <helgaas@kernel.org>,
	David Fugate <david.fugate@intel.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Scott Bauer <scott.bauer@intel.com>
Subject: Re: [PATCH 3/3] iommu: prevent VMD child devices from being remapping targets
Date: Wed, 9 Aug 2017 11:13:30 -0600	[thread overview]
Message-ID: <e1ead7c8-0891-f1b2-e5b0-d601d1af80e0@intel.com> (raw)
In-Reply-To: <fda8e2c5-11da-7189-794c-59a68273e4d8@arm.com>

Hi Robin, thanks for the reply.

On 08/11/2017 12:25 PM, Robin Murphy wrote:
> On 07/08/17 20:57, Jon Derrick wrote:
>> VMD child devices must use the VMD endpoint's ID as the DMA source.
>> Because of this, there needs to be a way to link the parent VMD
>> endpoint's DMAR domain to the VMD child devices' DMAR domain such that
>> attaching and detaching child devices modify the endpoint's DMAR mapping
>> and prevents early detaching.
> > That sounds like either pci_device_group() needs modifying, or perhaps
> that intel-iommu needs its own extended iommu_ops::device_group
> implementation, to ensure that VMD child devices get put in the same
> group as their parent - if they share requester IDs they can't feasibly
> be attached to different domains anyway.
> 
> Robin.
Yes it seems like that to me too. I have a high-level understanding of
the changes required but not too much in the nitty-gritty details. It's
a bit more complicated anyways because VMD emerges a set of root ports,
and AFAICT, PCI ACS end at the root ports and iommu groups rely on ACS
to group devices. Either way it's not within the scope of VMD.

  reply	other threads:[~2017-08-11 18:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 19:57 [PATCH 1/3] MAINTAINERS: Add Jonathan Derrick as VMD maintainer Jon Derrick
2017-08-07 19:57 ` [PATCH 2/3] pci: Generalize is_vmd behavior Jon Derrick
2017-08-11 17:03   ` Bjorn Helgaas
2017-08-09 17:02     ` Jon Derrick
2017-08-07 19:57 ` [PATCH 3/3] iommu: prevent VMD child devices from being remapping targets Jon Derrick
2017-08-11 17:17   ` Bjorn Helgaas
2017-08-11 18:25   ` Robin Murphy
2017-08-09 17:13     ` Jon Derrick [this message]
2017-08-11 17:20 ` [PATCH 1/3] MAINTAINERS: Add Jonathan Derrick as VMD maintainer Bjorn Helgaas
2017-08-11 18:23 ` Keith Busch

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=e1ead7c8-0891-f1b2-e5b0-d601d1af80e0@intel.com \
    --to=jonathan.derrick@intel.com \
    --cc=david.fugate@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=helgaas@kernel.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=scott.bauer@intel.com \
    /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

all inboxes | Powered by JetHome®