From: Chris Wright <chrisw@sous-sol.org>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.sc.intel.com>,
Johannes Berg <johannes@sipsolutions.net>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Zhu Yi <yi.zhu@intel.com>, Chris Wright <chrisw@sous-sol.org>,
LKML <linux-kernel@vger.kernel.org>,
iommu@lists.linux-foundation.org
Subject: Re: [PATCH]iwlan dma mapping read and write changes
Date: Wed, 11 Feb 2009 10:59:45 -0800 [thread overview]
Message-ID: <20090211185945.GQ27684@sequoia.sous-sol.org> (raw)
In-Reply-To: <20090211182648.GA1661@linux-os.sc.intel.com>
* Fenghua Yu (fenghua.yu@intel.com) wrote:
> When iwlan runs on IOMMU, IOMMU generates a lot of PTE write faults because PTE
> write bit is not set on some of PTE's. This is because iwlan driver calls DMA
> mapping with PCI_DMA_TODEVICE which is read only in mapping PTE. But iwlan device
> actually writes to the mapped page to update its contents. This issue is not
> exposed in swiotlb. But VT-d hardware can capture this fault and stop the fault
> transaction.
>
> The following patch fixes the issue.
Yes, plain old driver bug! This fixes the iwlagn vt-d issue.
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
Tested-by: Chris Wright <chrisw@sous-sol.org>
thanks,
chris
next prev parent reply other threads:[~2009-02-11 19:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 16:56 [PATCH 0/2]Add Variable Page Size and IA64 Support in Intel IOMMU Fenghua Yu
2008-10-03 15:50 ` Bjorn Helgaas
2008-10-06 19:44 ` Yu, Fenghua
2008-10-07 0:01 ` [PATCH V2 0/2] Add " Fenghua Yu
2009-02-11 18:26 ` [PATCH]iwlan dma mapping read and write changes Fenghua Yu
2009-02-11 18:35 ` Bhavesh Davda
2009-02-11 19:29 ` Yu, Fenghua
2009-02-11 18:59 ` Chris Wright [this message]
2009-02-11 21:27 ` Winkler, Tomas
2009-02-11 21:33 ` Johannes Berg
2009-02-11 21:41 ` Winkler, Tomas
2009-02-11 21:47 ` Johannes Berg
2009-02-11 21:50 ` Johannes Berg
2009-02-11 22:10 ` Winkler, Tomas
2009-02-11 22:13 ` Yu, Fenghua
2009-02-11 22:13 ` David Woodhouse
2009-02-12 13:42 ` Winkler, Tomas
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=20090211185945.GQ27684@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=akpm@linux-foundation.sc.intel.com \
--cc=dwmw2@infradead.org \
--cc=emmanuel.grumbach@intel.com \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tomas.winkler@intel.com \
--cc=yi.zhu@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
Powered by JetHome