linux-kernel - Re: /dev/mem implementation

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]

Message-ID: <87hbqj4ss3.fsf@basil.nowhere.org>
Date:	Mon, 18 Jan 2010 11:22:04 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Felix Rubinstein <felixru@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: /dev/mem implementation

Arjan van de Ven <arjan@...radead.org> writes:
>
> If you feel that you have a valid use case where you really want do
> muck with such memory, it might be a good idea to explain that
> usecase....

To add to it this only applies to uncacheable pages which don't use
MTRRs. Unless in some special situations (e.g. a lot of GPU 3d data
active) that situation tends to be rare and not apply to most memory.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/