linux-kernel - Re: [PATCH] x86/mm: Tracking linear mapping split events since boot

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:   Mon, 25 Jan 2021 15:32:29 -0500
From:   Tejun Heo <tj@...nel.org>
To:     Dave Hansen <dave.hansen@...el.com>
Cc:     Saravanan D <saravanand@...look.com>, x86@...nel.org,
        dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org,
        linux-kernel@...r.kernel.org, kernel-team@...com
Subject: Re: [PATCH] x86/mm: Tracking linear mapping split events since boot

Hello,

On Mon, Jan 25, 2021 at 12:15:51PM -0800, Dave Hansen wrote:
> > DirectMap4k:     3505112 kB
> > DirectMap2M:    19464192 kB
> > DirectMap1G:    12582912 kB
> > DirectMap2MSplits:  1705
> > DirectMap1GSplits:    20
> 
> This seems much more like something we'd want in /proc/vmstat or as a
> tracepoint than meminfo.  A tracepoint would be especially nice because
> the trace buffer could actually be examined if an admin finds an
> excessive number of these.

Adding a TP sure can be helpful but I'm not sure how that'd make counters
unnecessary given that the accumulated number of events since boot is what
matters.

Thanks.

-- 
tejun