mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: tglx@kernel.org, peterz@infradead.org, bp@alien8.de,
	frederic@kernel.org, tony.luck@intel.com
Cc: reinette.chatre@intel.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] cpu: CPU hotplug lock updates
Date: Wed,  3 Jun 2026 20:38:45 -0700	[thread overview]
Message-ID: <cover.1780543665.git.reinette.chatre@intel.com> (raw)

resctrl would like to use lockdep_is_cpus_held() as the lockdep
expression provided to list_for_each_entry_rcu() but Sashiko pointed out
that lockdep_is_cpus_held() is undefined when CONFIG_HOTPLUG_CPU is unset.

Patch 2 adds stubs for lockdep_is_cpus_held() and lockdep_is_cpus_write_held().

Patch 1 supports this work by adding include/linux/cpuhplock.h to the
MAINTAINERS CPU HOTPLUG area to help ensure patches touching it are routed
correctly.

Applies against tip/master.

Reinette Chatre (2):
  MAINTAINERS: Add include/linux/cpuhplock.h to CPU HOTPLUG area
  cpu: Add lockdep_is_cpus_held()/lockdep_is_cpus_write_held() stubs for
    !CONFIG_HOTPLUG_CPU

 MAINTAINERS               | 1 +
 include/linux/cpuhplock.h | 7 ++++---
 2 files changed, 5 insertions(+), 3 deletions(-)

-- 
2.50.1


             reply	other threads:[~2026-06-04  3:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04  3:38 Reinette Chatre [this message]
2026-06-04  3:38 ` [PATCH 1/2] MAINTAINERS: Add include/linux/cpuhplock.h to CPU HOTPLUG area Reinette Chatre
2026-06-04  3:38 ` [PATCH 2/2] cpu: Add lockdep_is_cpus_held()/lockdep_is_cpus_write_held() stubs for !CONFIG_HOTPLUG_CPU Reinette Chatre

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=cover.1780543665.git.reinette.chatre@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=bp@alien8.de \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    /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

Powered by JetHome