From: Peter Zijlstra <peterz@infradead.org>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] x86/perf: Use static_call for x86_pmu.guest_get_msrs
Date: Mon, 18 Jan 2021 14:35:03 +0100 [thread overview]
Message-ID: <YAWOhxi6Vxiq8JLR@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <a82754e7-9a2d-7ab4-466d-fc0d51a3b7f2@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
On Mon, Jan 18, 2021 at 09:05:06PM +0800, Like Xu wrote:
> I guess this fix will silence the compiler error,
> and v2 will be sent after the local 0day test passes.
I think there's also a problem where you don't assign a function at all.
I think you want something like
if (!x86_pmu.guest_get_msr)
x86_pmu.guest_get_msr = guest_get_msr_nop;
right before x86_pmu_static_call_update();
And then have it be something like:
static void *guest_et_msr_nop(int *nr)
{
*nr = 0;
return NULL;
}
and then you can reduce the entire thing to:
struct perf_guest_switch_msr *perf_guest_get_msrs(int *nr)
{
return static_call(x86_pmu_guest_get_msrs)(nr);
}
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Like Xu <like.xu@linux.intel.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Jason Baron <jbaron@akamai.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] x86/perf: Use static_call for x86_pmu.guest_get_msrs
Date: Mon, 18 Jan 2021 14:35:03 +0100 [thread overview]
Message-ID: <YAWOhxi6Vxiq8JLR@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <a82754e7-9a2d-7ab4-466d-fc0d51a3b7f2@linux.intel.com>
On Mon, Jan 18, 2021 at 09:05:06PM +0800, Like Xu wrote:
> I guess this fix will silence the compiler error,
> and v2 will be sent after the local 0day test passes.
I think there's also a problem where you don't assign a function at all.
I think you want something like
if (!x86_pmu.guest_get_msr)
x86_pmu.guest_get_msr = guest_get_msr_nop;
right before x86_pmu_static_call_update();
And then have it be something like:
static void *guest_et_msr_nop(int *nr)
{
*nr = 0;
return NULL;
}
and then you can reduce the entire thing to:
struct perf_guest_switch_msr *perf_guest_get_msrs(int *nr)
{
return static_call(x86_pmu_guest_get_msrs)(nr);
}
next prev parent reply other threads:[~2021-01-18 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 7:21 [PATCH] x86/perf: Use static_call for x86_pmu.guest_get_msrs Like Xu
2021-01-18 10:10 ` Peter Zijlstra
2021-01-18 12:12 ` kernel test robot
2021-01-18 12:12 ` kernel test robot
2021-01-18 13:05 ` Like Xu
2021-01-18 13:05 ` Like Xu
2021-01-18 13:35 ` Peter Zijlstra [this message]
2021-01-18 13:35 ` Peter Zijlstra
2021-01-22 3:19 ` Like Xu
2021-01-22 3:19 ` Like Xu
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=YAWOhxi6Vxiq8JLR@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kbuild-all@lists.01.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.