The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>, Borislav Petkov <bp@alien8.de>
Subject: [GIT PULL] locking changes for v6.11
Date: Mon, 15 Jul 2024 14:11:50 +0200	[thread overview]
Message-ID: <ZpUSBpYTFbyHtQBv@gmail.com> (raw)

Linus,

Please pull the latest locking/core Git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-2024-07-15

   # HEAD: e81859fe64ad42dccefe134d1696e0635f78d763 locking/rwsem: Add __always_inline annotation to __down_write_common() and inlined callers

Locking changes for v6.11:

 - Jump label fixes, including a perf events fix that originally
   manifested as jump label failures, but was a serialization bug
   at the usage site.

 - Mark down_write*() helpers as __always_inline, to improve
   WCHAN debuggability.

 - Misc cleanups and fixes.

 Thanks,

	Ingo

------------------>
Ingo Molnar (1):
      cleanup: Standardize the header guard define's name

John Stultz (1):
      locking/rwsem: Add __always_inline annotation to __down_write_common() and inlined callers

Thomas Gleixner (4):
      perf/x86: Serialize set_attr_rdpmc()
      jump_label: Fix concurrency issues in static_key_slow_dec()
      jump_label: Clarify condition in static_key_fast_inc_not_disabled()
      jump_label: Simplify and clarify static_key_fast_inc_cpus_locked()


 arch/x86/events/core.c  |  3 ++
 include/linux/cleanup.h |  6 ++--
 kernel/jump_label.c     | 74 ++++++++++++++++++++++++++++++-------------------
 kernel/locking/rwsem.c  |  6 ++--
 4 files changed, 55 insertions(+), 34 deletions(-)

             reply	other threads:[~2024-07-15 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 12:11 Ingo Molnar [this message]
2024-07-17  0:49 ` [GIT PULL] locking changes for v6.11 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=ZpUSBpYTFbyHtQBv@gmail.com \
    --to=mingo@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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