From: Kishon Vijay Abraham I <kishon@ti.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: pci-usb/pci-sata broken with LPAE config after "reduce use of block bounce buffers"
Date: Fri, 31 Jan 2020 17:14:01 +0530 [thread overview]
Message-ID: <f76af743-dcb5-f59d-b315-f2332a9dc906@ti.com> (raw)
In-Reply-To: <20200130164235.GA6705@lst.de>
Hi Christoph,
On 30/01/20 10:12 pm, Christoph Hellwig wrote:
> On Thu, Jan 30, 2020 at 01:39:58PM +0530, Kishon Vijay Abraham I wrote:
>> Hi Christoph,
>>
>> On 30/01/20 1:28 pm, Christoph Hellwig wrote:
>>> On Fri, Nov 15, 2019 at 04:29:31PM +0530, Kishon Vijay Abraham I wrote:
>>>> Hi Christoph,
>>>>
>>>> I think we are encountering a case where the connected PCIe card (like PCIe USB
>>>> card) supports 64-bit addressing and the ARM core supports 64-bit addressing
>>>> but the PCIe controller in the SoC to which PCIe card is connected supports
>>>> only 32-bits.
>>>>
>>>> Here dma APIs can provide an address above the 32 bit region to the PCIe card.
>>>> However this will fail when the card tries to access the provided address via
>>>> the PCIe controller.
>>>
>>> What kernel version do you test? The classic arm version of dma_capable
>>> doesn't take the bus dma mask into account. In Linux 5.5 I switched
>>> ARM to use the generic version in
>>>
>>> 130c1ccbf55 ("dma-direct: unify the dma_capable definitions")
>>>
>>> so with that this case is supposed to work, without that it doesn't
>>> have much of a chance.
>>
>> I got into a new issue in 5.5 kernel with NVMe card wherein I get the
>> below warn dump. This is different from the issue I initially posted
>> seen with USB and SATA cards (I was getting a data mismatch then). With
>> 5.5 kernel I don't see those issues anymore in USB card. I only see the
>> below warn dump with NVMe card.
>
> Can you throw in a little debug printk if this comes from
> dma_direct_possible or swiotlb_map?
I could see swiotlb_tbl_map_single() returning DMA_MAPPING_ERROR.
Kernel with debug print:
https://github.com/kishon/linux-wip.git nvm_dma_issue
Full log: https://pastebin.ubuntu.com/p/Xf2ngxc3kB/
Thanks
Kishon
next prev parent reply other threads:[~2020-01-31 11:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 10:59 pci-usb/pci-sata broken with LPAE config after "reduce use of block bounce buffers" Kishon Vijay Abraham I
2019-11-15 13:06 ` Christoph Hellwig
2019-11-15 14:18 ` Kishon Vijay Abraham I
2019-11-16 16:35 ` Christoph Hellwig
2019-11-18 17:21 ` Robin Murphy
2019-11-25 5:43 ` Kishon Vijay Abraham I
2020-01-27 13:10 ` Kishon Vijay Abraham I
2020-01-27 13:22 ` Robin Murphy
2020-01-29 6:24 ` Kishon Vijay Abraham I
2020-01-30 7:58 ` Christoph Hellwig
2020-01-30 8:09 ` Kishon Vijay Abraham I
2020-01-30 16:42 ` Christoph Hellwig
2020-01-31 11:44 ` Kishon Vijay Abraham I [this message]
2020-02-03 14:21 ` Christoph Hellwig
2020-02-05 5:15 ` Kishon Vijay Abraham I
2020-02-05 7:47 ` Christoph Hellwig
2020-02-05 8:32 ` Kishon Vijay Abraham I
2020-02-05 8:48 ` Christoph Hellwig
2020-02-05 9:18 ` Kishon Vijay Abraham I
2020-02-05 9:19 ` Christoph Hellwig
2020-02-05 9:33 ` Kishon Vijay Abraham I
2020-02-05 16:05 ` Christoph Hellwig
2020-02-17 14:23 ` Christoph Hellwig
2020-02-18 12:15 ` Kishon Vijay Abraham I
2020-04-02 12:01 ` Kishon Vijay Abraham I
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=f76af743-dcb5-f59d-b315-f2332a9dc906@ti.com \
--to=kishon@ti.com \
--cc=hch@lst.de \
--cc=linux-pci@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).