linux-kernel - Re: [PATCH 0/7] [RESEND][v4] x86: rework tlb range flushing code

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: <53DA75C5.5010607@zytor.com>
Date:	Thu, 31 Jul 2014 09:58:45 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Dave Hansen <dave@...1.net>
CC:	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] [RESEND][v4] x86: rework tlb range flushing code

On 07/31/2014 08:40 AM, Dave Hansen wrote:
> x86 Maintainers,
> 
> I've sent this a couple of times and resolved all the feedback
> I've received.  It has sign-offs from Mel and Rik.  Could this
> get picked up in to the x86 tree, please?
> 
> Changes from v3:
>  * Include the patch I was using to gather detailed statistics
>    about the length of the ranged TLB flushes
>  * Fix some documentation typos
>  * Add a patch to rework the remote tlb flush code to plumb the
>    tracepoints in easier, and add missing tracepoints
>  * use __print_symbolic() for the human-readable tracepoint
>    descriptions
>  * change an int to bool in patch 1
>  * Specifically call out that we removed itlb vs. dtlb logic
> 
> Changes from v2:
>  * Added a brief comment above the ceiling tunable
>  * Updated the documentation to mention large pages and say
>    "individual flush" instead of invlpg in most cases.
> 
> I've run this through a variety of systems in the LKP harness,
> as well as running it on my desktop for a few days.  I'm yet to
> see an to see if any perfmance regressions (or gains) show up.
> 

Thanks for the resend.  Applied.

	-hpa


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