From: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
To: "hch@lst.de" <hch@lst.de>,
Vineet Gupta <vineet.gupta1@synopsys.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
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>,
"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.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 14:32:52 +0000 [thread overview]
Message-ID: <1545316369.14089.20.camel@synopsys.com> (raw)
In-Reply-To: <20181219165939.GA26087@lst.de>
Hi Christoph,
I test kernel from your 'dma-alloc-always-zero' branch, and as
I can see we have DMA peripherals (like USB) broken.
There are the errors example I got during USB initializing:
------------------------------>8--------------------------------
usb 1-1: device descriptor read/64, error -110
usb usb1-port1: attempt power cycle
usb 1-1: new high-speed USB device number 4 using ehci-platform
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb 1-1: new high-speed USB device number 5 using ehci-platform
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb usb1-port1: unable to enumerate USB device
usb 2-1: new full-speed USB device number 2 using ohci-platform
usb 2-1: device descriptor read/all, error -84
usb 2-1: new full-speed USB device number 3 using ohci-platform
usb 2-1: device descriptor read/all, error -84
usb usb2-port1: attempt power cycle
usb 2-1: new full-speed USB device number 4 using ohci-platform
usb 2-1: device descriptor read/8, error -62
usb 2-1: device descriptor read/8, error -62
usb 2-1: new full-speed USB device number 5 using ohci-platform
usb 2-1: device descriptor read/8, error -84
usb 2-1: device descriptor read/8, error -84
usb usb2-port1: unable to enumerate USB device
[snip]
------------------------------8<--------------------------------
On Wed, 2018-12-19 at 17:59 +0100, Christoph Hellwig wrote:
> FYI, I've picked this up for dma-mapping for-next now.
>
> _______________________________________________
> linux-snps-arc mailing list
> linux-snps-arc@lists.infradead.org
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.org_mailman_listinfo_linux-2Dsnps-2Darc&d=DwICAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=ZlJN
> 1MriPUTkBKCrPSx67GmaplEUGcAEk9yPtCLdUXI&m=naBCT96A4RSQJLzBWzuCcmptFGiQDfFTOWJpprqDIVk&s=cHF84va89ofP6VlrV683ewENUXdaLW7opamLZSkZBgk&e=
--
Eugeniy Paltsev
WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
To: "hch@lst.de" <hch@lst.de>,
Vineet Gupta <vineet.gupta1@synopsys.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
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>,
"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.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 14:32:52 +0000 [thread overview]
Message-ID: <1545316369.14089.20.camel@synopsys.com> (raw)
In-Reply-To: <20181219165939.GA26087@lst.de>
SGkgQ2hyaXN0b3BoLA0KDQpJIHRlc3Qga2VybmVsIGZyb20geW91ciAnZG1hLWFsbG9jLWFsd2F5
cy16ZXJvJyBicmFuY2gsIGFuZCBhcw0KSSBjYW4gc2VlIHdlIGhhdmUgRE1BIHBlcmlwaGVyYWxz
IChsaWtlIFVTQikgYnJva2VuLg0KDQpUaGVyZSBhcmUgdGhlIGVycm9ycyBleGFtcGxlIEkgZ290
IGR1cmluZyBVU0IgaW5pdGlhbGl6aW5nOg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
PjgtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KdXNiIDEtMTogZGV2aWNlIGRlc2Ny
aXB0b3IgcmVhZC82NCwgZXJyb3IgLTExMA0KdXNiIHVzYjEtcG9ydDE6IGF0dGVtcHQgcG93ZXIg
Y3ljbGUNCnVzYiAxLTE6IG5ldyBoaWdoLXNwZWVkIFVTQiBkZXZpY2UgbnVtYmVyIDQgdXNpbmcg
ZWhjaS1wbGF0Zm9ybQ0KdXNiIDEtMTogZGV2aWNlIGRlc2NyaXB0b3IgcmVhZC82NCwgZXJyb3Ig
LTExMA0KdXNiIDEtMTogZGV2aWNlIGRlc2NyaXB0b3IgcmVhZC82NCwgZXJyb3IgLTExMA0KdXNi
IDEtMTogbmV3IGhpZ2gtc3BlZWQgVVNCIGRldmljZSBudW1iZXIgNSB1c2luZyBlaGNpLXBsYXRm
b3JtDQp1c2IgMS0xOiBkZXZpY2UgZGVzY3JpcHRvciByZWFkLzY0LCBlcnJvciAtMTEwDQp1c2Ig
MS0xOiBkZXZpY2UgZGVzY3JpcHRvciByZWFkLzY0LCBlcnJvciAtMTEwDQp1c2IgdXNiMS1wb3J0
MTogdW5hYmxlIHRvIGVudW1lcmF0ZSBVU0IgZGV2aWNlDQp1c2IgMi0xOiBuZXcgZnVsbC1zcGVl
ZCBVU0IgZGV2aWNlIG51bWJlciAyIHVzaW5nIG9oY2ktcGxhdGZvcm0NCnVzYiAyLTE6IGRldmlj
ZSBkZXNjcmlwdG9yIHJlYWQvYWxsLCBlcnJvciAtODQNCnVzYiAyLTE6IG5ldyBmdWxsLXNwZWVk
IFVTQiBkZXZpY2UgbnVtYmVyIDMgdXNpbmcgb2hjaS1wbGF0Zm9ybQ0KdXNiIDItMTogZGV2aWNl
IGRlc2NyaXB0b3IgcmVhZC9hbGwsIGVycm9yIC04NA0KdXNiIHVzYjItcG9ydDE6IGF0dGVtcHQg
cG93ZXIgY3ljbGUNCnVzYiAyLTE6IG5ldyBmdWxsLXNwZWVkIFVTQiBkZXZpY2UgbnVtYmVyIDQg
dXNpbmcgb2hjaS1wbGF0Zm9ybQ0KdXNiIDItMTogZGV2aWNlIGRlc2NyaXB0b3IgcmVhZC84LCBl
cnJvciAtNjINCnVzYiAyLTE6IGRldmljZSBkZXNjcmlwdG9yIHJlYWQvOCwgZXJyb3IgLTYyDQp1
c2IgMi0xOiBuZXcgZnVsbC1zcGVlZCBVU0IgZGV2aWNlIG51bWJlciA1IHVzaW5nIG9oY2ktcGxh
dGZvcm0NCnVzYiAyLTE6IGRldmljZSBkZXNjcmlwdG9yIHJlYWQvOCwgZXJyb3IgLTg0DQp1c2Ig
Mi0xOiBkZXZpY2UgZGVzY3JpcHRvciByZWFkLzgsIGVycm9yIC04NA0KdXNiIHVzYjItcG9ydDE6
IHVuYWJsZSB0byBlbnVtZXJhdGUgVVNCIGRldmljZQ0KIFtzbmlwXQ0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tODwtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNCk9u
IFdlZCwgMjAxOC0xMi0xOSBhdCAxNzo1OSArMDEwMCwgQ2hyaXN0b3BoIEhlbGx3aWcgd3JvdGU6
DQo+IEZZSSwgSSd2ZSBwaWNrZWQgdGhpcyB1cCBmb3IgZG1hLW1hcHBpbmcgZm9yLW5leHQgbm93
Lg0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4gbGludXgtc25wcy1hcmMgbWFpbGluZyBsaXN0DQo+IGxpbnV4LXNucHMtYXJjQGxpc3RzLmlu
ZnJhZGVhZC5vcmcNCj4gaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91
PWh0dHAtM0FfX2xpc3RzLmluZnJhZGVhZC5vcmdfbWFpbG1hbl9saXN0aW5mb19saW51eC0yRHNu
cHMtMkRhcmMmZD1Ed0lDQWcmYz1EUEw2X1hfNkprWEZ4N0FYV3FCMHRnJnI9WmxKTg0KPiAxTXJp
UFVUa0JLQ3JQU3g2N0dtYXBsRVVHY0FFazl5UHRDTGRVWEkmbT1uYUJDVDk2QTRSU1FKTHpCV3p1
Q2NtcHRGR2lRRGZGVE9XSnBwcnFESVZrJnM9Y0hGODR2YTg5b2ZQNlZsclY2ODNld0VOVVhkYUxX
N29wYW1MWlNrWkJnayZlPQ0KLS0gDQogRXVnZW5peSBQYWx0c2V2
WARNING: multiple messages have this Message-ID (diff)
From: eugeniy.paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: ensure dma_alloc_coherent always returns zeroed memory
Date: Thu, 20 Dec 2018 14:32:52 +0000 [thread overview]
Message-ID: <1545316369.14089.20.camel@synopsys.com> (raw)
In-Reply-To: <20181219165939.GA26087@lst.de>
Hi Christoph,
I test kernel from your 'dma-alloc-always-zero' branch, and as
I can see we have DMA peripherals (like USB) broken.
There are the errors example I got during USB initializing:
------------------------------>8--------------------------------
usb 1-1: device descriptor read/64, error -110
usb usb1-port1: attempt power cycle
usb 1-1: new high-speed USB device number 4 using ehci-platform
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb 1-1: new high-speed USB device number 5 using ehci-platform
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb usb1-port1: unable to enumerate USB device
usb 2-1: new full-speed USB device number 2 using ohci-platform
usb 2-1: device descriptor read/all, error -84
usb 2-1: new full-speed USB device number 3 using ohci-platform
usb 2-1: device descriptor read/all, error -84
usb usb2-port1: attempt power cycle
usb 2-1: new full-speed USB device number 4 using ohci-platform
usb 2-1: device descriptor read/8, error -62
usb 2-1: device descriptor read/8, error -62
usb 2-1: new full-speed USB device number 5 using ohci-platform
usb 2-1: device descriptor read/8, error -84
usb 2-1: device descriptor read/8, error -84
usb usb2-port1: unable to enumerate USB device
[snip]
------------------------------8<--------------------------------
On Wed, 2018-12-19@17:59 +0100, Christoph Hellwig wrote:
> FYI, I've picked this up for dma-mapping for-next now.
>
> _______________________________________________
> linux-snps-arc mailing list
> linux-snps-arc at lists.infradead.org
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.org_mailman_listinfo_linux-2Dsnps-2Darc&d=DwICAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=ZlJN
> 1MriPUTkBKCrPSx67GmaplEUGcAEk9yPtCLdUXI&m=naBCT96A4RSQJLzBWzuCcmptFGiQDfFTOWJpprqDIVk&s=cHF84va89ofP6VlrV683ewENUXdaLW7opamLZSkZBgk&e=
--
Eugeniy Paltsev
next prev parent reply other threads:[~2018-12-20 14:33 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 [this message]
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
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=1545316369.14089.20.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=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.