From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
peterx@redhat.com, Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PATCH 0/5] intel_iommu: fix windows svvp verification, and trivial cleanups
Date: Mon, 17 Dec 2018 15:31:09 +0800 [thread overview]
Message-ID: <20181217073114.11984-1-peterx@redhat.com> (raw)
Patch 1-2: mostly for debugging purpose, either on continuous
converting tracepoints into error reports, or fix incorrect
debug messages.
Patch 3: enable dma read/write draining support for vt-d emulation.
The major reason is to pass Windows SVVP verification.
Patch 4-5: some tunes on existing VT-d parameters, either name or
default value. This turns IR on by default for 4.0 or later.
Please review. Thanks.
Peter Xu (5):
intel_iommu: dump correct iova when failed
intel_iommu: convert invalid traces into error reports
intel_iommu: dma read/write draining support
intel_iommu: remove "x-" prefix for "aw-bits"
intel_iommu: turn on IR by default
hw/i386/intel_iommu.c | 66 +++++++++++++++++++++++++---------
hw/i386/intel_iommu_internal.h | 3 ++
hw/i386/trace-events | 6 ----
hw/i386/x86-iommu.c | 2 +-
include/hw/i386/intel_iommu.h | 1 +
include/hw/i386/pc.h | 9 +++++
6 files changed, 63 insertions(+), 24 deletions(-)
--
2.17.1
next reply other threads:[~2018-12-17 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 7:31 Peter Xu [this message]
2018-12-17 7:31 ` [Qemu-devel] [PATCH 1/5] intel_iommu: dump correct iova when failed Peter Xu
2018-12-17 7:31 ` [Qemu-devel] [PATCH 2/5] intel_iommu: convert invalid traces into error reports Peter Xu
2018-12-17 7:31 ` [Qemu-devel] [PATCH 3/5] intel_iommu: dma read/write draining support Peter Xu
2018-12-17 7:31 ` [Qemu-devel] [PATCH 4/5] intel_iommu: remove "x-" prefix for "aw-bits" Peter Xu
2018-12-17 7:31 ` [Qemu-devel] [PATCH 5/5] intel_iommu: turn on IR by default Peter Xu
2018-12-18 3:07 ` Peter Xu
2018-12-18 12:30 ` Paolo Bonzini
2018-12-19 5:21 ` Peter Xu
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=20181217073114.11984-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).