From: Dexuan Cui <decui@microsoft.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: static_branch_enable() does not work from a __init function?
Date: Wed, 16 Dec 2020 03:54:29 +0000 [thread overview]
Message-ID: <MW4PR21MB1857CC85A6844C89183C93E9BFC59@MW4PR21MB1857.namprd21.prod.outlook.com> (raw)
Hi,
The below init_module() prints "foo: false". This is strange since
static_branch_enable() is called before the static_branch_unlikely().
This strange behavior happens to v5.10 and an old v5.4 kernel.
If I remove the "__init" marker from the init_module() function, then
I get the expected output of "foo: true"! I guess here I'm missing
something with Static Keys?
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/jump_label.h>
static DEFINE_STATIC_KEY_FALSE(enable_foo);
int __init init_module(void)
{
static_branch_enable(&enable_foo);
if (static_branch_unlikely(&enable_foo))
printk("foo: true\n");
else
printk("foo: false\n");
return 0;
}
void cleanup_module(void)
{
static_branch_disable(&enable_foo);
}
MODULE_LICENSE("GPL");
PS, I originally found: in arch/x86/kvm/vmx/vmx.c: vmx_init(), it looks
like the line "static_branch_enable(&enable_evmcs);" does not take effect
in a v5.4-based kernel, but does take effect in the v5.10 kernel in the
same x86-64 virtual machine on Hyper-V, so I made the above test module
to test static_branch_enable(), and found that static_branch_enable() in
the test module does not work with both v5.10 and my v5.4 kernel, if the
__init marker is used.
Thanks,
-- Dexuan
next reply other threads:[~2020-12-16 3:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 3:54 Dexuan Cui [this message]
2020-12-16 9:26 ` static_branch_enable() does not work from a __init function? Peter Zijlstra
2020-12-16 10:59 ` Peter Zijlstra
2020-12-16 13:30 ` [RFC][PATCH] jump_label/static_call: Add MAINTAINERS Peter Zijlstra
2020-12-16 13:42 ` Peter Zijlstra
2020-12-16 14:23 ` Steven Rostedt
2020-12-16 16:19 ` Josh Poimboeuf
2020-12-16 16:19 ` Ard Biesheuvel
2020-12-16 21:16 ` Jason Baron
2020-12-16 13:54 ` [PATCH] jump_label: Fix usage in module __init Peter Zijlstra
2020-12-16 16:36 ` Josh Poimboeuf
2020-12-16 20:45 ` static_branch_enable() does not work from a __init function? Dexuan Cui
2020-12-16 11:55 ` Jessica Yu
2020-12-16 12:47 ` Peter Zijlstra
2020-12-16 13:10 ` Jessica Yu
2020-12-16 13:23 ` Peter Zijlstra
2020-12-16 13:27 ` Jessica Yu
2020-12-16 12:38 ` Jessica Yu
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=MW4PR21MB1857CC85A6844C89183C93E9BFC59@MW4PR21MB1857.namprd21.prod.outlook.com \
--to=decui@microsoft.com \
--cc=bristot@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).