From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, David Woodhouse <dwmw2@infradead.org>
Cc: ashok.raj@intel.com, jacob.jun.pan@intel.com,
kevin.tian@intel.com, Zhenyu Wang <zhenyuw@linux.intel.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH 0/2] iommu/vt-d: Small fixes for 5.2-rc1
Date: Thu, 2 May 2019 09:34:24 +0800 [thread overview]
Message-ID: <20190502013426.16989-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
This includes two small fixes for virtual IOMMU running in
qemu enviroment. On bare metal, we always have an dedicated
IOMMU for Intel integrated graphic device. And some aspects
of the driver was designed according to this. Unfortunately,
in qemu environment, the virtual IOMMU has only a single
include-all IOMMU engine, as the result some interfaces don't
work as expected anymore. This includes two fixes for this.
Best regards,
Lu Baolu
Lu Baolu (2):
iommu/vt-d: Set intel_iommu_gfx_mapped correctly
iommu/vt-d: Make kernel parameter igfx_off work with vIOMMU
drivers/iommu/intel-iommu.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, David Woodhouse <dwmw2@infradead.org>
Cc: kevin.tian@intel.com, ashok.raj@intel.com,
linux-kernel@vger.kernel.org,
Zhenyu Wang <zhenyuw@linux.intel.com>,
iommu@lists.linux-foundation.org, jacob.jun.pan@intel.com
Subject: [PATCH 0/2] iommu/vt-d: Small fixes for 5.2-rc1
Date: Thu, 2 May 2019 09:34:24 +0800 [thread overview]
Message-ID: <20190502013426.16989-1-baolu.lu@linux.intel.com> (raw)
Message-ID: <20190502013424.P-pzuwt517KXuFgcP7LKtNz4P4n1zq94zPk5hz_CwdA@z> (raw)
Hi Joerg,
This includes two small fixes for virtual IOMMU running in
qemu enviroment. On bare metal, we always have an dedicated
IOMMU for Intel integrated graphic device. And some aspects
of the driver was designed according to this. Unfortunately,
in qemu environment, the virtual IOMMU has only a single
include-all IOMMU engine, as the result some interfaces don't
work as expected anymore. This includes two fixes for this.
Best regards,
Lu Baolu
Lu Baolu (2):
iommu/vt-d: Set intel_iommu_gfx_mapped correctly
iommu/vt-d: Make kernel parameter igfx_off work with vIOMMU
drivers/iommu/intel-iommu.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
--
2.17.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2019-05-02 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 1:34 Lu Baolu [this message]
2019-05-02 1:34 ` [PATCH 0/2] iommu/vt-d: Small fixes for 5.2-rc1 Lu Baolu
2019-05-02 1:34 ` [PATCH 1/2] iommu/vt-d: Set intel_iommu_gfx_mapped correctly Lu Baolu
2019-05-02 1:34 ` Lu Baolu
2019-05-02 1:34 ` [PATCH 2/2] iommu/vt-d: Make kernel parameter igfx_off work with vIOMMU Lu Baolu
2019-05-02 1:34 ` Lu Baolu
2019-05-03 15:31 ` [PATCH 0/2] iommu/vt-d: Small fixes for 5.2-rc1 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=20190502013426.16989-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenyuw@linux.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