From: "hch@lst.de" <hch@lst.de>
To: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
Cc: "hch@lst.de" <hch@lst.de>,
"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" <monstr@monstr.eu>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>
Subject: Re: ensure dma_alloc_coherent always returns zeroed memory
Date: Thu, 20 Dec 2018 15:46:04 +0100 [thread overview]
Message-ID: <20181220144604.GA18034@lst.de> (raw)
In-Reply-To: <1545316759.14089.22.camel@synopsys.com>
On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote:
> > 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.
Well, the branch has quite a few commits. Can you check the commit
just before the zeroing to start, and if that is already broken (which
I suspect) bisect the offending commit?
WARNING: multiple messages have this Message-ID (diff)
From: "hch@lst.de" <hch@lst.de>
To: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
Cc: "hch@lst.de" <hch@lst.de>,
"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>
Subject: Re: ensure dma_alloc_coherent always returns zeroed memory
Date: Thu, 20 Dec 2018 15:46:04 +0100 [thread overview]
Message-ID: <20181220144604.GA18034@lst.de> (raw)
In-Reply-To: <1545316759.14089.22.camel@synopsys.com>
On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote:
> > 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.
Well, the branch has quite a few commits. Can you check the commit
just before the zeroing to start, and if that is already broken (which
I suspect) bisect the offending commit?
WARNING: multiple messages have this Message-ID (diff)
From: "hch@lst.de" <hch@lst.de>
To: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
Cc: "hch@lst.de" <hch@lst.de>,
"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>
Subject: Re: ensure dma_alloc_coherent always returns zeroed memory
Date: Thu, 20 Dec 2018 14:46:04 +0000 [thread overview]
Message-ID: <20181220144604.GA18034@lst.de> (raw)
In-Reply-To: <1545316759.14089.22.camel@synopsys.com>
On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote:
> > 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.
Well, the branch has quite a few commits. Can you check the commit
just before the zeroing to start, and if that is already broken (which
I suspect) bisect the offending commit?
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (hch@lst.de)
To: linux-snps-arc@lists.infradead.org
Subject: ensure dma_alloc_coherent always returns zeroed memory
Date: Thu, 20 Dec 2018 15:46:04 +0100 [thread overview]
Message-ID: <20181220144604.GA18034@lst.de> (raw)
In-Reply-To: <1545316759.14089.22.camel@synopsys.com>
On Thu, Dec 20, 2018@02:39:20PM +0000, Eugeniy Paltsev wrote:
> > 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.
Well, the branch has quite a few commits. Can you check the commit
just before the zeroing to start, and if that is already broken (which
I suspect) bisect the offending commit?
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de <hch@lst.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] ensure dma_alloc_coherent always returns zeroed memory
Date: Thu, 20 Dec 2018 15:46:04 +0100 [thread overview]
Message-ID: <20181220144604.GA18034@lst.de> (raw)
In-Reply-To: <1545316759.14089.22.camel@synopsys.com>
On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote:
> > 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.
Well, the branch has quite a few commits. Can you check the commit
just before the zeroing to start, and if that is already broken (which
I suspect) bisect the offending commit?
next prev parent reply other threads:[~2018-12-20 14:46 UTC|newest]
Thread overview: 95+ 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 ` [OpenRISC] " Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_* Christoph Hellwig
2018-12-14 8:25 ` [OpenRISC] " Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 9:54 ` Geert Uytterhoeven
2018-12-14 9:54 ` [OpenRISC] " Geert Uytterhoeven
2018-12-14 9:54 ` Geert Uytterhoeven
2018-12-14 9:54 ` Geert Uytterhoeven
2018-12-14 9:54 ` Geert Uytterhoeven
2018-12-14 9:55 ` Geert Uytterhoeven
2018-12-14 9:55 ` [OpenRISC] " Geert Uytterhoeven
2018-12-14 9:55 ` Geert Uytterhoeven
2018-12-14 9:55 ` Geert Uytterhoeven
2018-12-14 9:55 ` Geert Uytterhoeven
2018-12-14 11:47 ` Christoph Hellwig
2018-12-14 11:47 ` [OpenRISC] " Christoph Hellwig
2018-12-14 11:47 ` Christoph Hellwig
2018-12-14 11:47 ` Christoph Hellwig
2018-12-14 11:47 ` Christoph Hellwig
2018-12-14 12:36 ` Geert Uytterhoeven
2018-12-14 12:36 ` [OpenRISC] " Geert Uytterhoeven
2018-12-14 12:36 ` Geert Uytterhoeven
2018-12-14 12:36 ` Geert Uytterhoeven
2018-12-14 14:14 ` Greg Ungerer
2018-12-14 14:14 ` [OpenRISC] " Greg Ungerer
2018-12-14 14:14 ` Greg Ungerer
2018-12-14 14:14 ` Greg Ungerer
2018-12-14 14:14 ` Greg Ungerer
2018-12-14 14:14 ` Greg Ungerer
2018-12-17 11:59 ` Christoph Hellwig
2018-12-17 11:59 ` [OpenRISC] " Christoph Hellwig
2018-12-17 11:59 ` Christoph Hellwig
2018-12-17 11:59 ` Christoph Hellwig
2019-01-11 6:09 ` Greg Ungerer
2018-12-14 12:12 ` Eugeniy Paltsev
2018-12-14 12:12 ` [OpenRISC] " Eugeniy Paltsev
2018-12-14 12:12 ` Eugeniy Paltsev
2018-12-14 12:12 ` Eugeniy Paltsev
2018-12-14 12:12 ` Eugeniy Paltsev
2018-12-14 12:21 ` hch
2018-12-14 12:21 ` [OpenRISC] " hch
2018-12-14 12:21 ` hch-jcswGhMUV9g
2018-12-14 12:21 ` hch
2018-12-14 12:21 ` hch
2018-12-14 18:10 ` Sam Ravnborg
2018-12-14 18:10 ` [OpenRISC] " Sam Ravnborg
2018-12-14 18:10 ` Sam Ravnborg
2018-12-14 18:10 ` Sam Ravnborg
2018-12-14 18:35 ` Christoph Hellwig
2018-12-14 18:35 ` [OpenRISC] " Christoph Hellwig
2018-12-14 18:35 ` Christoph Hellwig
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 8:25 ` [OpenRISC] " Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 8:25 ` Christoph Hellwig
2018-12-14 13:33 ` ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-14 13:33 ` [OpenRISC] " Christoph Hellwig
2018-12-14 13:33 ` Christoph Hellwig
2018-12-14 13:33 ` Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
2018-12-19 16:59 ` [OpenRISC] " Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
2018-12-20 14:32 ` Eugeniy Paltsev
2018-12-20 14:32 ` Eugeniy Paltsev
2018-12-20 14:32 ` Eugeniy Paltsev
2018-12-20 14:32 ` Eugeniy Paltsev
2018-12-20 14:34 ` hch
2018-12-20 14:34 ` [OpenRISC] " hch
2018-12-20 14:34 ` hch
2018-12-20 14:34 ` hch
2018-12-20 14:34 ` hch
2018-12-20 14:39 ` Eugeniy Paltsev
2018-12-20 14:39 ` Eugeniy Paltsev
2018-12-20 14:39 ` Eugeniy Paltsev
2018-12-20 14:39 ` Eugeniy Paltsev
2018-12-20 14:46 ` hch [this message]
2018-12-20 14:46 ` [OpenRISC] " hch
2018-12-20 14:46 ` hch
2018-12-20 14:46 ` hch
2018-12-20 14:46 ` hch
2018-12-20 17:37 ` hch
2018-12-20 17:37 ` [OpenRISC] " hch
2018-12-20 17:37 ` hch
2018-12-20 17:37 ` hch
2018-12-20 17:37 ` hch
[not found] <1546019189.2822.23.camel@synopsys.com>
[not found] ` <20181228175806.GA16929@lst.de>
2019-01-24 21:25 ` Vineet Gupta
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=20181220144604.GA18034@lst.de \
--to=hch@lst.de \
--cc=ashutosh.dixit@intel.com \
--cc=eugeniy.paltsev@synopsys.com \
--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=monstr@monstr.eu \
--cc=openrisc@lists.librecores.org \
--cc=sparclinux@vger.kernel.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 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.