From: Christoph Hellwig <hch@infradead•org>
To: Jean-Philippe Brucker <jean-philippe@linaro•org>
Cc: ashok.raj@intel•com, linux-pci@vger•kernel.org, joro@8bytes•org,
alex.williamson@redhat•com, iommu@lists•linux-foundation.org,
bhelgaas@google•com, baolu.lu@linux•intel.com, will@kernel•org,
dwmw2@infradead•org, linux-arm-kernel@lists•infradead.org,
robin.murphy@arm•com
Subject: Re: [PATCH 0/4] PCI, iommu: Factor 'untrusted' check for ATS enablement
Date: Fri, 15 May 2020 08:43:51 -0700 [thread overview]
Message-ID: <20200515154351.GA6546@infradead.org> (raw)
In-Reply-To: <20200515104359.1178606-1-jean-philippe@linaro.org>
Can you please lift the untrusted flag into struct device? It really
isn't a PCI specific concept, and we should not have code poking into
pci_dev all over the iommu code.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-15 15:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 10:43 [PATCH 0/4] PCI, iommu: Factor 'untrusted' check for ATS enablement Jean-Philippe Brucker
2020-05-15 10:43 ` [PATCH 1/4] PCI/ATS: Only enable ATS for trusted devices Jean-Philippe Brucker
2020-05-15 11:57 ` Joerg Roedel
2020-05-15 21:18 ` Bjorn Helgaas
2020-05-15 10:44 ` [PATCH 2/4] iommu/amd: Use pci_ats_supported() Jean-Philippe Brucker
2020-05-15 12:01 ` Joerg Roedel
2020-05-15 12:11 ` Jean-Philippe Brucker
2020-05-15 12:21 ` Joerg Roedel
2020-05-15 10:44 ` [PATCH 3/4] iommu/arm-smmu-v3: " Jean-Philippe Brucker
2020-05-18 15:37 ` Will Deacon
2020-05-15 10:44 ` [PATCH 4/4] iommu/vt-d: " Jean-Philippe Brucker
2020-05-15 15:43 ` Christoph Hellwig [this message]
2020-05-15 17:19 ` [PATCH 0/4] PCI, iommu: Factor 'untrusted' check for ATS enablement Raj, Ashok
2020-05-15 17:21 ` Will Deacon
2020-05-18 15:47 ` David Woodhouse
2020-05-18 16:29 ` Raj, Ashok
2020-05-18 16:36 ` Jean-Philippe Brucker
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=20200515154351.GA6546@infradead.org \
--to=hch@infradead$(echo .)org \
--cc=alex.williamson@redhat$(echo .)com \
--cc=ashok.raj@intel$(echo .)com \
--cc=baolu.lu@linux$(echo .)intel.com \
--cc=bhelgaas@google$(echo .)com \
--cc=dwmw2@infradead$(echo .)org \
--cc=iommu@lists$(echo .)linux-foundation.org \
--cc=jean-philippe@linaro$(echo .)org \
--cc=joro@8bytes$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=robin.murphy@arm$(echo .)com \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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