linux-kernel - Re: [PATCH 23/29] memstick: jmb38x_ms: use DMA for all TPCs with len greater that 8 by default

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Oct 2010 09:12:51 -0700 (PDT)
From:	Alex Dubov <oakad@...oo.com>
To:	Maxim Levitsky <maximlevitsky@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Maxim Levitsky <maximlevitsky@...il.com>
Subject: Re: [PATCH 23/29] memstick: jmb38x_ms: use DMA for all TPCs with len greater that 8 by default

--- On Fri, 22/10/10, Maxim Levitsky <maximlevitsky@...il.com> wrote:

> From: Maxim Levitsky <maximlevitsky@...il.com>
> Subject: [PATCH 23/29] memstick: jmb38x_ms: use DMA for all TPCs with len greater that 8 by default
> To: "Alex Dubov" <oakad@...oo.com>
> Cc: "Andrew Morton" <akpm@...ux-foundation.org>, "LKML" <linux-kernel@...r.kernel.org>, "Maxim Levitsky" <maximlevitsky@...il.com>
> Received: Friday, 22 October, 2010, 4:53 PM
> This is to workaround a wierd
> hardware bug:
> 
> If PIO write is used, and then after it DMA write is used,
> DMA
> engine stops doing writes.
> That condition even persists after device reset.
> 
> To be maxumum safe, we do dma to a scratch page
> and memcpy from/to it.
> 
> Besides this change should just improve performance.
> 
> Signed-off-by: Maxim Levitsky <maximlevitsky@...il.com>
> ---

I have not noticed this one before, and for all I know the driver was
tested at Jmicron.
Can you explain the issue a bit more?



      
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/