linux-kernel - understanding DMA cache maint

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>] [day] [month] [year] [list]

Message-ID: <912ec82a1002140732g946e9b1id8b56d7df7517480@mail.gmail.com>
Date:	Sun, 14 Feb 2010 17:32:17 +0200
From:	Neshama Parhoti <pneshama@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: understanding DMA cache maint

in the following function,
what's the different between the inner_op (dmac_*) and outer_op (outer_*) ?
why do we need two functions to do the cache operation ?
isn't this an action on the cache hardware itself ? are there 2
hardwares involved ?

void dma_cache_maint(const void *start, size_t size, int direction)
{
   ...
	switch (direction) {
	case DMA_FROM_DEVICE:		/* invalidate only */
		inner_op = dmac_inv_range;
		outer_op = outer_inv_range;
		break;
	case DMA_TO_DEVICE:		/* writeback only */
		inner_op = dmac_clean_range;
		outer_op = outer_clean_range;
		break;
	case DMA_BIDIRECTIONAL:		/* writeback and invalidate */
		inner_op = dmac_flush_range;
		outer_op = outer_flush_range;


thank you!
--
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/