From: Shuah Khan <shuah.khan@hp.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: fujita.tomonori@lab.ntt.co.jp,
LKML <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org, paul.gortmaker@windriver.com,
bhelgaas@google.com, amwang@redhat.com, shuahkhan@gmail.com
Subject: Re: [PATCH RFC] swiotlb: Remove SWIOTLB overflow buffer support
Date: Tue, 10 Jul 2012 10:55:07 -0600 [thread overview]
Message-ID: <1341939307.2502.34.camel@lorien2> (raw)
In-Reply-To: <20120709202505.GA9541@phenom.dumpdata.com>
On Mon, 2012-07-09 at 16:25 -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Jul 06, 2012 at 05:06:12PM -0600, Shuah Khan wrote:
> > Remove SWIOTLB overflow buffer support and return DMA_ERROR_CODE
> > (a value of zero) to make it consistent with iommu implementation
> > on Intel, AMD, and swiotlb-xen.
>
> While this is a good forward step and this needs to be done eventually,
> you should first send out patches for the drivers that don't check
> for the DMA_ERROR_CODE when doing mapping. In other words for the
> drivers that map but don't call dma_mapping_error to check.
>
> When that is fixed and *all the drivers that don't call dma_mapping_error
> are fixed, then this patch makes sense.
The challenge will be catching all the drivers and have confidence that
all of them are covered. I will start looking into this to get a feel
for how many drivers needs fixing.
Also, isn't this problem today with other iommu implementations? All of
the other iommu implementation don't have support for overflow buffers?
-- Shuah
next prev parent reply other threads:[~2012-07-10 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 23:06 [PATCH RFC] swiotlb: Remove SWIOTLB overflow buffer support Shuah Khan
2012-07-09 20:25 ` Konrad Rzeszutek Wilk
2012-07-10 16:33 ` FUJITA Tomonori
2012-07-10 16:55 ` Shuah Khan [this message]
2012-07-10 17:32 ` Konrad Rzeszutek Wilk
2012-07-10 23:06 ` Shuah Khan
2012-07-10 23:13 ` Shuah Khan
2012-07-12 16:17 ` [PATCH RFC] swiotlb: Disable swiotlb overflow support when CONFIG_ISA is enabled Shuah Khan
2012-07-16 14:45 ` Konrad Rzeszutek Wilk
2012-07-16 15:48 ` Shuah Khan
2012-07-16 16:01 ` Konrad Rzeszutek Wilk
2012-07-16 16:47 ` Shuah Khan
2012-07-17 18:27 ` Shuah Khan
2012-07-17 20:13 ` [PATCH] swiotlb: Disable swiotlb overflow support when CONFIG_ISA is disabled Shuah Khan
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=1341939307.2502.34.camel@lorien2 \
--to=shuah.khan@hp.com \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=bhelgaas@google.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=shuahkhan@gmail.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.