linux-kernel - Re: [PATCH] x86: create array based interface to change page attribute

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:	Tue, 08 Apr 2008 08:12:43 +0200
From:	Thomas Hellström <thomas@...gstengraphics.com>
To:	Arjan van de Ven <arjan@...ux.intel.com>
CC:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Andi Kleen <andi@...stfloor.org>,
	Dave Airlie <airlied@...hat.com>, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, mingo@...hat.com
Subject: Re: [PATCH] x86: create array based interface to change page attribute

Arjan van de Ven wrote:
> Thomas Hellström wrote:
>> Ouch, so we'll be needing an ioremap_wc(), I guess. We probably 
>> shouldn't use the linear kernel map for this anyway, since that would 
>> require a chipset flush for each ring commit.  We can actually use 
>> vmap() with a wc page protection for that, but an ioremap_wc() would 
>> certainly save us a lot of trouble.
>
> please don't use vmap() as a hack for mapping IO memory when you 
> should use ioremap_wc()....
I think you've misinterpreted. We must use vmap() if we need to map the 
cpu side of the aperture, (real pages) and ioremap() if we map the 
device side, which is io memory. Some devices accept both, but what I 
was saying was we should try to avoid the vmap() alternative, since it, 
like using the kernel mapping directly, requires a chipset flush after 
update.
> Lets get this thing right rather than finding whichever hack of the day
> happens to work with the implementation from yesterday.
/Thomas



--
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/