From: Dave Hansen <dave.hansen@intel.com>
To: Nadav Amit <namit@vmware.com>, Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFC PATCH v2 0/3] x86/mm/tlb: Defer TLB flushes with PTI
Date: Tue, 3 Sep 2019 08:17:30 -0700 [thread overview]
Message-ID: <f63027ae-2e3a-fac0-69f8-bb11c1b680b0@intel.com> (raw)
In-Reply-To: <20190823225248.15597-1-namit@vmware.com>
On 8/23/19 3:52 PM, Nadav Amit wrote:
> n_pages concurrent +deferred-pti change
> ------- ---------- ------------- ------
> 1 2119 1986 -6.7%
> 10 6791 5417 -20%
>
> Please let me know if I missed something that affects security or
> performance.
Hi Nadav,
Is this in a VM or on bare metal? Could you also share the bare
/proc/cpuinfo for one of the CPU threads? I want to make sure that any
oddities in the stepping or microcode are known.
next prev parent reply other threads:[~2019-09-03 15:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 22:52 [RFC PATCH v2 0/3] x86/mm/tlb: Defer TLB flushes with PTI Nadav Amit
2019-08-23 22:52 ` [RFC PATCH v2 1/3] x86/mm/tlb: Change __flush_tlb_one_user interface Nadav Amit
2019-08-26 7:51 ` Juergen Gross
2019-08-26 16:38 ` Nadav Amit
2019-08-27 5:53 ` Juergen Gross
2019-08-23 22:52 ` [RFC PATCH v2 2/3] x86/mm/tlb: Defer PTI flushes Nadav Amit
2019-08-27 18:28 ` Dave Hansen
2019-08-27 19:46 ` Nadav Amit
2019-08-27 23:13 ` Andy Lutomirski
2019-08-27 23:55 ` Nadav Amit
2019-08-28 0:30 ` Andy Lutomirski
2019-08-23 22:52 ` [RFC PATCH v2 3/3] x86/mm/tlb: Avoid deferring PTI flushes on shootdown Nadav Amit
2019-08-27 23:07 ` Andy Lutomirski
2019-08-27 23:57 ` Nadav Amit
2019-08-28 0:30 ` Andy Lutomirski
2019-08-27 18:17 ` [RFC PATCH v2 0/3] x86/mm/tlb: Defer TLB flushes with PTI Dave Hansen
2019-09-03 15:17 ` Dave Hansen [this message]
2019-09-03 16:13 ` Nadav Amit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f63027ae-2e3a-fac0-69f8-bb11c1b680b0@intel.com \
--to=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).