From: Oleg Orel <oorel@vmware.com>
To: "ashok.raj@intel.com" <ashok.raj@intel.com>,
"shaohua.li@intel.com" <shaohua.li@intel.com>,
"anil.s.keshavamurthy@intel.com" <anil.s.keshavamurthy@intel.com>,
"fenghua.yu@intel.com" <fenghua.yu@intel.com>,
"avi@qumranet.com" <avi@qumranet.com>,
"yaniv@qumranet.com" <yaniv@qumranet.com>,
Bhavesh Davda <bhavesh@vmware.com>,
Mallik Mahalingam <mallik@vmware.com>,
Jagannath Krishnan <krishnan@vmware.com>,
Adar Dembo <adar@vmware.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Intel IOMMU on Dell Latitude E6400, Lenovo X200 & Dell Precision T5400
Date: Thu, 29 Jan 2009 14:01:28 -0800 [thread overview]
Message-ID: <49822738.5060103@vmware.com> (raw)
Folks from Intel whi was working on IOMMU support in linux kernel and
KVM folks who presumably been able to use it successfully, your
input/comments will be very appriciated.
We are trying to make iommu working on laptops and desctop mentioned in
the subject line. However, we on all three computers have exactly the
same problem. We getting interrupt with 2 type of errors reported:
However, we are running into random device DMA issues on all three computers. We are getting MSI-X interrupts from the IOMMUs with 3 types of error reported:
a) PTE doesn't have write bit set
b) PTE doesn't have read bit set
c) Present bit in root entry is clear
We had reported more details @
https://bugzilla.redhat.com/show_bug.cgi?id=479996 and
http://bugzilla.kernel.org/show_bug.cgi?id=11821
Please advice us a way to debug it, what peaces should we look at,
print/check, etc...
1. Could we blame BIOS for that?
2. Is it possible that we build kernel with options what conflicting
with iommu implementation in some way? If so, could you share your
binary/source/config what works for you?
3. What desktop/laptops been tested and you aware that it works?
4. KVM folks, is it KVM+IOMMU works?
5. We have been seeing this issue with the latest Linus' git kernel as
well as 2.6.29-rc3 from kernel.org.
Oleg
next reply other threads:[~2009-01-29 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 22:01 Oleg Orel [this message]
2009-01-30 1:25 ` Intel IOMMU on Dell Latitude E6400, Lenovo X200 & Dell Precision T5400 Yu, Fenghua
2009-01-30 1:28 ` Oleg Orel
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=49822738.5060103@vmware.com \
--to=oorel@vmware.com \
--cc=adar@vmware.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashok.raj@intel.com \
--cc=avi@qumranet.com \
--cc=bhavesh@vmware.com \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=krishnan@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mallik@vmware.com \
--cc=shaohua.li@intel.com \
--cc=yaniv@qumranet.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