netdev - Re: [PATCH V1 net-next 1/2] pgtable: Add API to query if write combining is available

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

Message-Id: <20141007.154425.2156753440391523455.davem@davemloft.net>
Date:	Tue, 07 Oct 2014 15:44:25 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	ogerlitz@...lanox.com
Cc:	netdev@...r.kernel.org, amirv@...lanox.com,
	jackm@....mellanox.co.il, moshel@...lanox.com, talal@...lanox.com,
	yevgenyp@...lanox.com
Subject: Re: [PATCH V1 net-next 1/2] pgtable: Add API to query if write
 combining is available

From: Or Gerlitz <ogerlitz@...lanox.com>
Date: Sun,  5 Oct 2014 11:22:21 +0300

> From: Moshe Lazer <moshel@...lanox.com>
> 
> Currently the kernel write-combining interface provides a best effort
> mechanism in which the caller simply invokes pgprot_writecombine().
> 
> If write combining is available, the region is mapped for it, otherwise
> the region is (silently) mapped as non-cached.
> 
> In some cases, however, the calling driver must know if write combining
> is available, so a silent best effort mechanism is not sufficient.
> 
> Add writecombine_available(), which returns true if the system
> supports write combining and false if it doesn't.
> 
> Signed-off-by: Moshe Lazer <moshel@...lanox.com>
> Signed-off-by: Jack Morgenstein <jackm@....mellanox.co.il>
> Signed-off-by: Or Gerlitz <ogerlitz@...lanox.com>

This needs some ACKs from MM developers.

But also the situation is more complicated than a simple boolean test.

On some platforms you have to test first whether the range you are
trying to write combine can legally be marked in that way.  The DRM
layer has all of these per-arch tests to do this properly.

#if defined(__i386__) || defined(__x86_64__)
	if (map->type == _DRM_REGISTERS && !(map->flags & _DRM_WRITE_COMBINING))
		tmp = pgprot_noncached(tmp);
	else
		tmp = pgprot_writecombine(tmp);
#elif defined(__powerpc__)
	pgprot_val(tmp) |= _PAGE_NO_CACHE;
	if (map->type == _DRM_REGISTERS)
		pgprot_val(tmp) |= _PAGE_GUARDED;
#elif defined(__ia64__)
	if (efi_range_is_wc(vma->vm_start, vma->vm_end -
				    vma->vm_start))
		tmp = pgprot_writecombine(tmp);
	else
		tmp = pgprot_noncached(tmp);
#elif defined(__sparc__) || defined(__arm__) || defined(__mips__)
	tmp = pgprot_noncached(tmp);
#endif
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html