linux-kernel - Re: Microblaze, DMA and cache: Lack of sync functions?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4E490F8A.3090702@petalogix.com>
Date:	Mon, 15 Aug 2011 14:22:34 +0200
From:	Michal Simek <michal.simek@...alogix.com>
To:	Eli Billauer <eli@...lauer.co.il>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Microblaze, DMA and cache: Lack of sync functions?

Eli Billauer wrote:
> Hello,
> 
> 
> Before I make a needless hack, please correct me if I'm wrong: in 
> arch/microblaze/kernel/dma.c, the sync_single_for_cpu, 
> sync_single_for_device and friends are not set in the dma_direct_ops 
> structure (and not implemented), so calls from drivers to the 
> corresponding functions will do nothing. Since the Microblaze cache 
> doesn't update automatically on DMA operations, this looks like a bug to 
> me: The driver thinks the cache has been flushed or updated, but it 
> actually hasn't.
> 
> 
> Map and unmap methods are indeed implemented and registered, and they 
> both call an internal function to sync the cache. So why are there no 
> sync functions?
> 

It is not the bug just unimplemented feature and I haven't had any problem
that these functions are not implemented.
Implementation should be pretty straight forward. Patches welcomed.

Thanks,
Michal




-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
--
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/