All of lore.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, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/splitlock changes for v5.14
Date: Mon, 28 Jun 2021 09:42:22 +0200	[thread overview]
Message-ID: <YNl9XqC0V+tdJsjI@gmail.com> (raw)

Linus,

Please pull the latest x86/splitlock git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-splitlock-2021-06-28

   # HEAD: d28397eaf4c27947a1ffc720d42e8b3a33ae1e2a Documentation/x86: Add ratelimit in buslock.rst

Changes in this cycle were:

 - Add the "ratelimit:N" parameter to the split_lock_detect= boot option,
   to rate-limit the generation of bus-lock exceptions. This is both
   easier on system resources and kinder to offending applications than
   the current policy of outright killing them.

 - Document the split-lock detection feature and its parameters.

 Thanks,

	Ingo

------------------>
Fenghua Yu (4):
      Documentation/x86: Add buslock.rst
      x86/bus_lock: Set rate limit for bus lock
      Documentation/admin-guide: Add bus lock ratelimit
      Documentation/x86: Add ratelimit in buslock.rst


 Documentation/admin-guide/kernel-parameters.txt |   8 ++
 Documentation/x86/buslock.rst                   | 126 ++++++++++++++++++++++++
 Documentation/x86/index.rst                     |   1 +
 arch/x86/kernel/cpu/intel.c                     |  42 +++++++-
 4 files changed, 175 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/x86/buslock.rst


             reply	other threads:[~2021-06-28  7:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28  7:42 Ingo Molnar [this message]
2021-06-28 20:33 ` [GIT PULL] x86/splitlock changes for v5.14 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=YNl9XqC0V+tdJsjI@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.