From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Kevin Tian <kevin.tian@intel.com>, iommu@lists.linux-foundation.org
Subject: [PATCH 0/1] iommu/vt-d: Fixes for v5.18-rc4
Date: Sat, 23 Apr 2022 16:23:29 +0800 [thread overview]
Message-ID: <20220423082330.3897867-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
One fix is queued for v5.18. It aims to fix:
- Handle PCI stop marker messages in IOMMU driver to meet the
requirement of I/O page fault handling framework.
Please consider it for the iommu/fix branch.
Best regards,
Lu Baolu
Lu Baolu (1):
iommu/vt-d: Drop stop marker messages
drivers/iommu/intel/svm.c | 4 ++++
1 file changed, 4 insertions(+)
--
2.25.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2022-04-23 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 8:23 Lu Baolu [this message]
2022-04-23 8:23 ` [PATCH 1/1] iommu/vt-d: Drop stop marker messages Lu Baolu
2022-04-28 9:02 ` [PATCH 0/1] iommu/vt-d: Fixes for v5.18-rc4 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=20220423082330.3897867-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@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