public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Borislav Petkov <bp@alien8.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rik van Riel <riel@surriel.com>, Nadav Amit <namit@vmware.com>
Subject: [GIT PULL] x86/mm changes for v5.13
Date: Thu, 29 Apr 2021 10:28:19 +0200	[thread overview]
Message-ID: <20210429082819.GA2827959@gmail.com> (raw)

Linus,

Please pull the latest x86/mm git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-2021-04-29

   # HEAD: a500fc918f7b8dc3dff2e6c74f3e73e856c18248 Merge branch 'locking/core' into x86/mm, to resolve conflict

The x86 MM changes in this cycle were:

 - Implement concurrent TLB flushes, which overlaps the local TLB flush with the
   remote TLB flush. In testing this improved sysbench performance measurably by
   a couple of percentage points, especially if TLB-heavy security mitigations
   are active.

 - Further micro-optimizations to improve the performance of TLB flushes.

 Thanks,

	Ingo

------------------>
Nadav Amit (9):
      smp: Run functions concurrently in smp_call_function_many_cond()
      x86/mm/tlb: Unify flush_tlb_func_local() and flush_tlb_func_remote()
      x86/mm/tlb: Open-code on_each_cpu_cond_mask() for tlb_is_not_lazy()
      x86/mm/tlb: Flush remote and local TLBs concurrently
      x86/mm/tlb: Privatize cpu_tlbstate
      x86/mm/tlb: Do not make is_lazy dirty for no reason
      cpumask: Mark functions as pure
      x86/mm/tlb: Remove unnecessary uses of the inline keyword
      smp: Inline on_each_cpu_cond() and on_each_cpu()

Peter Zijlstra (1):
      smp: Micro-optimize smp_call_function_many_cond()


 arch/x86/hyperv/mmu.c                 |  10 +-
 arch/x86/include/asm/paravirt.h       |   6 +-
 arch/x86/include/asm/paravirt_types.h |   4 +-
 arch/x86/include/asm/tlbflush.h       |  48 ++++----
 arch/x86/include/asm/trace/hyperv.h   |   2 +-
 arch/x86/kernel/alternative.c         |   2 +-
 arch/x86/kernel/kvm.c                 |  11 +-
 arch/x86/kernel/paravirt.c            |   2 +-
 arch/x86/mm/init.c                    |   2 +-
 arch/x86/mm/tlb.c                     | 176 ++++++++++++++++------------
 arch/x86/xen/mmu_pv.c                 |  11 +-
 include/linux/cpumask.h               |   6 +-
 include/linux/smp.h                   |  50 +++++---
 include/trace/events/xen.h            |   2 +-
 kernel/smp.c                          | 212 ++++++++++++++--------------------
 kernel/up.c                           |  38 +-----
 16 files changed, 287 insertions(+), 295 deletions(-)

             reply	other threads:[~2021-04-29  8:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  8:28 Ingo Molnar [this message]
2021-04-29 18:50 ` [GIT PULL] x86/mm changes for v5.13 pr-tracker-bot

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=20210429082819.GA2827959@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namit@vmware.com \
    --cc=riel@surriel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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