From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org
Subject: [PULL REQUEST] iommu/vt-d: patches for v5.6 - 2nd wave
Date: Wed, 15 Jan 2020 11:03:54 +0800 [thread overview]
Message-ID: <20200115030359.13471-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
Below patches have been piled up for v5.6 since v5.5-rc3. They
are mostly misc changes and cleanups.
- Instead of aborting DMAR processing, mark firmware tainted
if any RMRRs fail sanity check.
- Check host bridge type correctly.
- Allow devices with RMRRs to use identity domain.
- Remove duplicated default identity domain treatment.
Please consider them for the iommu/vt-d branch.
Best regards,
-baolu
Barret Rhoden (2):
iommu/vt-d: Mark firmware tainted if RMRR fails sanity check
iommu/vt-d: Add RMRR base and end addresses sanity check
Lu Baolu (2):
iommu/vt-d: Allow devices with RMRRs to use identity domain
iommu/vt-d: Unnecessary to handle default identity domain
jimyan (1):
iommu/vt-d: Don't reject Host Bridge due to scope mismatch
drivers/iommu/dmar.c | 2 +-
drivers/iommu/intel-iommu.c | 47 ++++++++++++++++++-------------------
2 files changed, 24 insertions(+), 25 deletions(-)
--
2.17.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2020-01-15 3:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 3:03 Lu Baolu [this message]
2020-01-15 3:03 ` [PATCH 1/5] iommu/vt-d: Don't reject Host Bridge due to scope mismatch Lu Baolu
2020-01-15 3:03 ` [PATCH 2/5] iommu/vt-d: Mark firmware tainted if RMRR fails sanity check Lu Baolu
2020-01-15 3:03 ` [PATCH 3/5] iommu/vt-d: Add RMRR base and end addresses " Lu Baolu
2020-01-15 3:03 ` [PATCH 4/5] iommu/vt-d: Allow devices with RMRRs to use identity domain Lu Baolu
2020-01-15 3:03 ` [PATCH 5/5] iommu/vt-d: Unnecessary to handle default " Lu Baolu
2020-01-17 9:58 ` [PULL REQUEST] iommu/vt-d: patches for v5.6 - 2nd wave Joerg Roedel
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=20200115030359.13471-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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.