From: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
To: "hch@lst.de" <hch@lst.de>,
"eugeniy.paltsev@synopsys.com" <eugeniy.paltsev@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
"linux-m68k@lists.linux-m68k.org"
<linux-m68k@lists.linux-m68k.org>,
"vineet.gupta1@synopsys.com" <vineet.gupta1@synopsys.com>,
"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"openrisc@lists.librecores.org" <openrisc@lists.librecores.org>,
"ashutosh.dixit@intel.com" <ashutosh.dixit@intel.com>,
"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
"linux-c6x-dev@linux-c6x.org" <linux-c6x-dev@linux-c6x.org>,
"monstr@monstr.eu" <monst>
Subject: Re: ensure dma_alloc_coherent always returns zeroed memory
Date: Thu, 20 Dec 2018 14:39:20 +0000 [thread overview]
Message-ID: <1545316759.14089.22.camel@synopsys.com> (raw)
In-Reply-To: <20181220143415.GA17726@lst.de>
On Thu, 2018-12-20 at 15:34 +0100, hch@lst.de wrote:
> On Thu, Dec 20, 2018 at 02:32:52PM +0000, Eugeniy Paltsev wrote:
> > Hi Christoph,
> >
> > I test kernel from your 'dma-alloc-always-zero' branch, and as
> > I can see we have DMA peripherals (like USB) broken.
>
> I would be really surprised if that is caused by the patch to add
> the zeroing.
Me too :)
> Can you check which commit caused the issue by bisecting
> from a known good baseline?
Yep. At least kernel build from v4.20-rc4 (which is base for your branch)
seems to work fine.
--
Eugeniy Paltsev
next prev parent reply other threads:[~2018-12-20 14:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 8:25 ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-14 8:25 ` [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_* Christoph Hellwig
[not found] ` <20181214082515.14835-2-hch-jcswGhMUV9g@public.gmane.org>
2018-12-14 9:54 ` Geert Uytterhoeven
[not found] ` <CAMuHMdWOr0EsgFQF8tjJYLxKVXx+Jwn73N8SVKt8AQGLKQ8V-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-14 9:55 ` Geert Uytterhoeven
2018-12-14 11:47 ` Christoph Hellwig
2018-12-14 12:36 ` Geert Uytterhoeven
2018-12-14 14:14 ` Greg Ungerer
2018-12-17 11:59 ` Christoph Hellwig
2018-12-14 12:12 ` Eugeniy Paltsev
[not found] ` <1544789518.3270.34.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2018-12-14 12:21 ` hch-jcswGhMUV9g
2018-12-14 18:10 ` Sam Ravnborg
2018-12-14 18:35 ` Christoph Hellwig
2018-12-14 8:25 ` [PATCH 2/2] dma-mapping: deprecate dma_zalloc_coherent Christoph Hellwig
2018-12-14 13:33 ` ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
2018-12-20 14:32 ` Eugeniy Paltsev
2018-12-20 14:34 ` hch
2018-12-20 14:39 ` Eugeniy Paltsev [this message]
2018-12-20 14:46 ` hch
2018-12-20 17:37 ` hch
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=1545316759.14089.22.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=ashutosh.dixit@intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=openrisc@lists.librecores.org \
--cc=vineet.gupta1@synopsys.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;
as well as URLs for NNTP newsgroup(s).