linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: peterz@infradead.org
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, jolsa@redhat.com,
	alexey.budankov@linux.intel.com, songliubraving@fb.com,
	acme@redhat.com, allison@lohutok.net, sashal@kernel.org
Subject: [PATCH v3 03/14] tools/kernel.h: extend with dummy RCU functions
Date: Mon, 22 Jun 2020 18:42:47 -0400	[thread overview]
Message-ID: <20200622224258.1208588-4-sashal@kernel.org> (raw)
In-Reply-To: <20200622224258.1208588-1-sashal@kernel.org>

These calls were added by 108c14858b9e ("locking/lockdep: Add support
for dynamic keys") and require no special handling in userspace, so just
add empty function definitions.

Signed-off-by: Sasha Levin <sashal@kernel.org>
---
 tools/include/linux/kernel.h | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/tools/include/linux/kernel.h b/tools/include/linux/kernel.h
index a7e54a08fb54c..902d3b9ab4c17 100644
--- a/tools/include/linux/kernel.h
+++ b/tools/include/linux/kernel.h
@@ -117,4 +117,11 @@ int scnprintf_pad(char * buf, size_t size, const char * fmt, ...);
 #define current_gfp_context(k) 0
 #define synchronize_rcu()
 
+static __maybe_unused int system_state;
+#define SYSTEM_SCHEDULING 0
+
+#define might_sleep()
+#define rcu_read_lock()
+#define rcu_read_unlock()
+
 #endif
-- 
2.25.1


  parent reply	other threads:[~2020-06-22 22:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 22:42 [PATCH v3 00/14] Fix up liblockdep for 5.8-rc Sasha Levin
2020-06-22 22:42 ` [PATCH v3 01/14] tools headers: Add kprobes.h header Sasha Levin
2020-06-22 22:42 ` [PATCH v3 02/14] tools headers: Add rcupdate.h header Sasha Levin
2020-06-22 22:42 ` Sasha Levin [this message]
2020-06-22 22:42 ` [PATCH v3 04/14] tools bitmap: add bitmap_andnot definition Sasha Levin
2020-06-22 22:42 ` [PATCH v3 05/14] tools/lib/lockdep: add definition required for IRQ flag tracing Sasha Levin
2020-06-22 22:42 ` [PATCH v3 06/14] tools bitmap: add bitmap_clear definition Sasha Levin
2020-06-22 22:42 ` [PATCH v3 07/14] tools/lib/lockdep: Hook up vsprintf, find_bit, hweight libraries Sasha Levin
2020-06-22 22:42 ` [PATCH v3 08/14] tools/lib/lockdep: Enable building with CONFIG_TRACE_IRQFLAGS Sasha Levin
2020-06-22 22:42 ` [PATCH v3 09/14] tools/lib/lockdep: New stacktrace API Sasha Levin
2020-06-22 22:42 ` [PATCH v3 10/14] tools/lib/lockdep: call lockdep_init_task on init Sasha Levin
2020-06-22 22:42 ` [PATCH v3 11/14] tools/lib/lockdep: switch to using lockdep_init_map_waits Sasha Levin
2020-06-22 22:42 ` [PATCH v3 12/14] tools/kernel.h: hide noinstr Sasha Levin
2020-06-23  3:12   ` kernel test robot
2020-06-22 22:42 ` [PATCH v3 13/14] tools/lib/lockdep: explicitly declare lockdep_init_task() Sasha Levin
2020-06-22 22:42 ` [PATCH v3 14/14] tools/kernel.h: hide task_struct.hardirq_chain_key Sasha Levin

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=20200622224258.1208588-4-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=acme@redhat.com \
    --cc=alexey.budankov@linux.intel.com \
    --cc=allison@lohutok.net \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=songliubraving@fb.com \
    --cc=tglx@linutronix.de \
    /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).