From: "Zhang, Yang Z" <yang.z.zhang@intel.com>
To: Jan Beulich <JBeulich@suse.com>,
"wei.huang2@amd.com" <wei.huang2@amd.com>,
"weiwang.dd@gmail.com" <weiwang.dd@gmail.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: iommu=dom0-passthrough behavior
Date: Tue, 13 Nov 2012 00:11:37 +0000 [thread overview]
Message-ID: <A9667DDFB95DB7438FA9D7D576C3D87E2B0A42@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <5097DB9102000078000A65C7@nat28.tlf.novell.com>
Jan Beulich wrote on 2012-11-05:
> All,
>
> so far it was my understanding that this option is intended to get
> the DMA behavior that Dom0 observes as close as possible to how
> it would be without IOMMU.
Correct. There is a bit in context entry which controlling the DMA request(from this device) to walk or not walk the iommu page table.
As we known, walking page table introduced extra cost, so we use this parameter to make sure the device which owned by dom0 not to walking iommu page table when DMA request is arrived.
> However, we're now dealing with a customer report where a
> single function device is observed to initiate DMA operations
> appearing to originate from function 1, which makes obvious that
> the option above is not making things as transparent as I would
> have expected them to be: Without IOMMU, such requests get
> processed fine, while with IOMMU (due to there not being a
> context entry for the bogus device) the device fails to initialize
> (causing DMA faults, the presence of which I had to convince
> myself of separately, as for whatever reason at least the VT-d
> code doesn't issue any log message in that case).
Sorry, I cannot understand your problem. Is there any bug in current VT-d code?
> So I'm now seeking for alternative workaround suggestions that
> we could pass to that customer (less intrusive than "iommu=off").
Best regards,
Yang
next prev parent reply other threads:[~2012-11-13 0:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 14:30 iommu=dom0-passthrough behavior Jan Beulich
2012-11-13 0:11 ` Zhang, Yang Z [this message]
2012-11-13 8:07 ` Jan Beulich
2012-11-13 8:50 ` Zhang, Xiantao
2012-11-13 9:41 ` Jan Beulich
2012-11-13 11:13 ` Zhang, Yang Z
2012-11-13 11:24 ` Jan Beulich
2012-11-13 15:02 ` Zhang, Xiantao
2012-11-13 15:29 ` Jan Beulich
2012-11-14 0:37 ` Zhang, Xiantao
2012-11-14 13:40 ` Jan Beulich
2012-11-15 8:23 ` Zhang, Xiantao
2012-11-15 9:05 ` Jan Beulich
2012-11-16 6:21 ` Zhang, Xiantao
2012-11-16 8:22 ` Jan Beulich
2012-11-16 9:26 ` Jan Beulich
2012-11-16 9:43 ` Zhang, Xiantao
2012-11-16 9:53 ` Jan Beulich
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=A9667DDFB95DB7438FA9D7D576C3D87E2B0A42@SHSMSX101.ccr.corp.intel.com \
--to=yang.z.zhang@intel.com \
--cc=JBeulich@suse.com \
--cc=wei.huang2@amd.com \
--cc=weiwang.dd@gmail.com \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.