From: Roger Pau Monne <roger.pau@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>, Jan Beulich <jbeulich@suse.com>,
Wei Liu <wl@xen.org>, Andrew Cooper <andrew.cooper3@citrix.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH 0/2] iommu: fixes for interrupt remapping enabling
Date: Thu, 10 Oct 2019 13:03:37 +0200 [thread overview]
Message-ID: <20191010110339.6447-1-roger.pau@citrix.com> (raw)
Hello,
The following series contain two fixes for issues found when enabling
interrupt remapping and the IO-APIC already has unmasked pins. While I'm
not aware of any system malfunctioning (apart from reporting IOMMU
interrupt remapping faults) I think it would be nice to have those in
4.13.
Thanks, Roger.
Roger Pau Monne (2):
x2APIC: translate IO-APIC entries when enabling the IOMMU
iommu: translate IO-APIC pins when enabling interrupt remapping
xen/arch/x86/apic.c | 12 ++-
xen/arch/x86/io_apic.c | 5 +-
xen/drivers/passthrough/amd/iommu_init.c | 11 ++-
xen/drivers/passthrough/amd/iommu_intr.c | 90 +------------------
xen/drivers/passthrough/x86/iommu.c | 34 ++++++-
xen/include/asm-x86/hvm/svm/amd-iommu-proto.h | 1 +
xen/include/asm-x86/io_apic.h | 3 +-
7 files changed, 55 insertions(+), 101 deletions(-)
--
2.23.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-10-10 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 11:03 Roger Pau Monne [this message]
2019-10-10 11:03 ` [Xen-devel] [PATCH 1/2] x2APIC: translate IO-APIC entries when enabling the IOMMU Roger Pau Monne
2019-10-10 11:24 ` Roger Pau Monné
2019-10-10 11:03 ` [Xen-devel] [PATCH 2/2] iommu: translate IO-APIC pins when enabling interrupt remapping Roger Pau Monne
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=20191010110339.6447-1-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).