From: Christoph Hellwig <hch@lst.de>
To: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, ath10k@lists.infradead.org,
hch@lst.de, nicoleotsuka@gmail.com,
iommu@lists.linux-foundation.org, tobias.klausmann@freenet.de,
robin.murphy@arm.com, davem@davemloft.net, kvalo@codeaurora.org,
m.szyprowski@samsung.com
Subject: Re: regression in ath10k dma allocation
Date: Fri, 16 Aug 2019 18:43:01 +0200 [thread overview]
Message-ID: <20190816164301.GA3629@lst.de> (raw)
In-Reply-To: <8fe8b415-2d34-0a14-170b-dcb31c162e67@mni.thm.de>
Hi Tobias,
do you have CONFIG_DMA_CMA set in your config? If not please make sure
you have this commit in your testing tree, and if the problem still
persists it would be a little odd and we'd have to dig deeper:
commit dd3dcede9fa0a0b661ac1f24843f4a1b1317fdb6
Author: Nicolin Chen <nicoleotsuka@gmail.com>
Date: Wed May 29 17:54:25 2019 -0700
dma-contiguous: fix !CONFIG_DMA_CMA version of dma_{alloc, free}_contiguous()
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, ath10k@lists.infradead.org,
hch@lst.de, nicoleotsuka@gmail.com,
iommu@lists.linux-foundation.org, tobias.klausmann@freenet.de,
robin.murphy@arm.com, davem@davemloft.net, kvalo@codeaurora.org
Subject: Re: regression in ath10k dma allocation
Date: Fri, 16 Aug 2019 18:43:01 +0200 [thread overview]
Message-ID: <20190816164301.GA3629@lst.de> (raw)
In-Reply-To: <8fe8b415-2d34-0a14-170b-dcb31c162e67@mni.thm.de>
Hi Tobias,
do you have CONFIG_DMA_CMA set in your config? If not please make sure
you have this commit in your testing tree, and if the problem still
persists it would be a little odd and we'd have to dig deeper:
commit dd3dcede9fa0a0b661ac1f24843f4a1b1317fdb6
Author: Nicolin Chen <nicoleotsuka@gmail.com>
Date: Wed May 29 17:54:25 2019 -0700
dma-contiguous: fix !CONFIG_DMA_CMA version of dma_{alloc, free}_contiguous()
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>
Cc: kvalo@codeaurora.org, davem@davemloft.net,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
nicoleotsuka@gmail.com, hch@lst.de, m.szyprowski@samsung.com,
robin.murphy@arm.com, iommu@lists.linux-foundation.org,
tobias.klausmann@freenet.de
Subject: Re: regression in ath10k dma allocation
Date: Fri, 16 Aug 2019 18:43:01 +0200 [thread overview]
Message-ID: <20190816164301.GA3629@lst.de> (raw)
In-Reply-To: <8fe8b415-2d34-0a14-170b-dcb31c162e67@mni.thm.de>
Hi Tobias,
do you have CONFIG_DMA_CMA set in your config? If not please make sure
you have this commit in your testing tree, and if the problem still
persists it would be a little odd and we'd have to dig deeper:
commit dd3dcede9fa0a0b661ac1f24843f4a1b1317fdb6
Author: Nicolin Chen <nicoleotsuka@gmail.com>
Date: Wed May 29 17:54:25 2019 -0700
dma-contiguous: fix !CONFIG_DMA_CMA version of dma_{alloc, free}_contiguous()
next prev parent reply other threads:[~2019-08-16 16:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 16:08 regression in ath10k dma allocation Tobias Klausmann
2019-08-16 16:08 ` Tobias Klausmann
2019-08-16 16:08 ` Tobias Klausmann
2019-08-16 16:43 ` Christoph Hellwig [this message]
2019-08-16 16:43 ` Christoph Hellwig
2019-08-16 16:43 ` Christoph Hellwig
2019-08-16 20:16 ` Tobias Klausmann
2019-08-16 20:16 ` Tobias Klausmann
2019-08-16 20:16 ` Tobias Klausmann
2019-08-16 22:25 ` Nicolin Chen
2019-08-16 22:25 ` Nicolin Chen
2019-08-16 22:25 ` Nicolin Chen
2019-08-16 22:42 ` Tobias Klausmann
2019-08-16 22:42 ` Tobias Klausmann
2019-08-16 22:42 ` Tobias Klausmann
2019-08-18 3:13 ` Hillf Danton
2019-08-18 3:13 ` Hillf Danton
2019-08-18 22:38 ` Tobias Klausmann
2019-08-18 22:38 ` Tobias Klausmann
2019-08-18 22:38 ` Tobias Klausmann
2019-08-20 1:58 ` Nicolin Chen
2019-08-20 1:58 ` Nicolin Chen
2019-08-20 1:58 ` Nicolin Chen
2019-08-20 2:14 ` Christoph Hellwig
2019-08-20 2:14 ` Christoph Hellwig
2019-08-20 2:14 ` Christoph Hellwig
2019-08-20 3:05 ` Christoph Hellwig
2019-08-20 3:05 ` Christoph Hellwig
2019-08-20 3:05 ` Christoph Hellwig
2019-08-20 6:58 ` Hillf Danton
2019-08-20 6:58 ` Hillf Danton
2019-08-20 7:12 ` Christoph Hellwig
2019-08-20 7:12 ` Christoph Hellwig
2019-08-20 7:12 ` Christoph Hellwig
2019-08-20 20:24 ` Tobias Klausmann
2019-08-20 20:24 ` Tobias Klausmann
2019-08-20 20:24 ` Tobias Klausmann
-- strict thread matches above, loose matches on Subject: below --
2019-08-20 2:29 Hillf Danton
2019-08-20 2:29 ` Hillf Danton
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=20190816164301.GA3629@lst.de \
--to=hch@lst.de \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=iommu@lists.linux-foundation.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=robin.murphy@arm.com \
--cc=tobias.johannes.klausmann@mni.thm.de \
--cc=tobias.klausmann@freenet.de \
/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.