Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 14 Feb 2018 11:35:54 -0800
From: Kees Cook <>
To: Laura Abbott <>
Cc: Jann Horn <>, Igor Stoppa <>, 
	Boris Lukashev <>, Christopher Lameter <>, 
	Matthew Wilcox <>, Jerome Glisse <>, 
	Michal Hocko <>, Christoph Hellwig <>, 
	linux-security-module <>, Linux-MM <>, 
	kernel list <>, 
	Kernel Hardening <>, 
	linux-arm-kernel <>
Subject: Re: arm64 physmap (was Re: [PATCH 4/6] Protectable Memory)

On Wed, Feb 14, 2018 at 11:29 AM, Kees Cook <> wrote:
> Why does using finer granularity on the physmap degrade performance? I
> assume TLB pressure, but what is heavily using that area? (I must not
> be understanding what physmap actually gets used for -- I thought it
> was just a convenience to have a 1:1 virt/phys map for some lookups?)

Jann has sorted me out: it's that physmap isn't an _alias_ for the
buddy allocator memory areas; it's used directly.


Kees Cook
Pixel Security

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.