From: Bibo Mao <maobibo@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Tianrui Zhao <zhaotianrui@loongson.cn>,
kernel@xen0n.name, kvm@vger.kernel.org,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH 3/3] LoongArch: KVM: Set vcpu_is_preempted() macro rather than function
Date: Wed, 11 Mar 2026 14:30:04 +0800 [thread overview]
Message-ID: <a72cefd7-8da3-043b-67d2-39ff43f1934b@loongson.cn> (raw)
In-Reply-To: <CAAhV-H499qApb0sW-HcyrHQS1Sn2gDp9jHVFahNz-u0GoLCLng@mail.gmail.com>
On 2026/3/11 下午12:38, Huacai Chen wrote:
> On Wed, Mar 11, 2026 at 11:51 AM Bibo Mao <maobibo@loongson.cn> wrote:
>>
>>
>>
>> On 2026/3/11 上午11:35, Huacai Chen wrote:
>>> Hi, Bibo,
>>>
>>> On Wed, Mar 11, 2026 at 11:21 AM Bibo Mao <maobibo@loongson.cn> wrote:
>>>>
>>>> vcpu_is_preempted() is performance sensitive called in function
>>>> osq_lock(), here set it as macro. So that parameter is not parsed
>>>> at most time, it can avoid cache line thrashing across numa node.
>>> I remember that I had suggested you define vcpu_is_preempted() in the
>>> header file but you refused.
>> yes, I refuse then, that is a tragedy, I am sorry for that:(
>>
>> By some benchmarks, vcpu_is_preempted() is called in busy-loop method,
>> more obvious with more CPUs, it may be a bottleneck.
> I also remember that you said the static key and percpu steal_time
> structure should be EXPORT_SYMBOL, but you haven't done this patch.
Currently API vcpu_is_preempted() and its caller owner_on_cpu() is only
used on files in kernel/locking/mutex.c, rwsem.c etc, it seems that it
is only used by kernel. And there is no obvious signals for module usage
with this API.
So I do not want to export the symbol this time, will export the symbol
if there is actually usage for modules.
Regards
Bibo Mao
>
> Huacai
>
>>
>> Regards
>> Bibo Mao
>>
>>>
>>> Huacai
>>>
>>>>
>>>> Here is part of unixbench result on 3C5000 DualWay machine with 32
>>>> Cores and 2 Numa node.
>>>> origin with patch CONFIG_PARAVIRT disabled
>>>> execl 6871.9 7134.2 7190.8
>>>> fstime 425.5 959.9 956.1
>>>>
>>>> From the test result, with macro method it is almost the same with
>>>> CONFIG_PARAVIRT disabled, and there is some improvment compared with
>>>> function method.
>>>>
>>>> Signed-off-by: Bibo Mao <maobibo@loongson.cn>
>>>> ---
>>>> arch/loongarch/include/asm/qspinlock.h | 27 +++++++++++++++++++++-----
>>>> arch/loongarch/kernel/paravirt.c | 15 ++------------
>>>> 2 files changed, 24 insertions(+), 18 deletions(-)
>>>>
>>>> diff --git a/arch/loongarch/include/asm/qspinlock.h b/arch/loongarch/include/asm/qspinlock.h
>>>> index 66244801db67..305afd37cdcb 100644
>>>> --- a/arch/loongarch/include/asm/qspinlock.h
>>>> +++ b/arch/loongarch/include/asm/qspinlock.h
>>>> @@ -5,8 +5,10 @@
>>>> #include <linux/jump_label.h>
>>>>
>>>> #ifdef CONFIG_PARAVIRT
>>>> -
>>>> +#include <asm/kvm_para.h>
>>>> DECLARE_STATIC_KEY_FALSE(virt_spin_lock_key);
>>>> +DECLARE_STATIC_KEY_FALSE(virt_preempt_key);
>>>> +DECLARE_PER_CPU(struct kvm_steal_time, steal_time);
>>>>
>>>> #define virt_spin_lock virt_spin_lock
>>>>
>>>> @@ -34,10 +36,25 @@ static inline bool virt_spin_lock(struct qspinlock *lock)
>>>> return true;
>>>> }
>>>>
>>>> -#define vcpu_is_preempted vcpu_is_preempted
>>>> -
>>>> -bool vcpu_is_preempted(int cpu);
>>>> -
>>>> +/*
>>>> + * Macro is better than inline function here
>>>> + * With inline function, parameter cpu is parsed even though it is not used.
>>>> + * This may cause cache line thrashing across NUMA node.
>>>> + * With macro method, parameter cpu is parsed only when it is used.
>>>> + */
>>>> +#define vcpu_is_preempted(cpu) \
>>>> +({ \
>>>> + bool __val; \
>>>> + \
>>>> + if (!static_branch_unlikely(&virt_preempt_key)) \
>>>> + __val = false; \
>>>> + else { \
>>>> + struct kvm_steal_time *src; \
>>>> + src = &per_cpu(steal_time, cpu); \
>>>> + __val = !!(src->preempted & KVM_VCPU_PREEMPTED); \
>>>> + } \
>>>> + __val; \
>>>> +})
>>>> #endif /* CONFIG_PARAVIRT */
>>>>
>>>> #include <asm-generic/qspinlock.h>
>>>> diff --git a/arch/loongarch/kernel/paravirt.c b/arch/loongarch/kernel/paravirt.c
>>>> index b74fe6db49ab..2d1206e486e2 100644
>>>> --- a/arch/loongarch/kernel/paravirt.c
>>>> +++ b/arch/loongarch/kernel/paravirt.c
>>>> @@ -10,8 +10,8 @@
>>>> #include <asm/paravirt.h>
>>>>
>>>> static int has_steal_clock;
>>>> -static DEFINE_PER_CPU(struct kvm_steal_time, steal_time) __aligned(64);
>>>> -static DEFINE_STATIC_KEY_FALSE(virt_preempt_key);
>>>> +DEFINE_PER_CPU(struct kvm_steal_time, steal_time) __aligned(64);
>>>> +DEFINE_STATIC_KEY_FALSE(virt_preempt_key);
>>>> DEFINE_STATIC_KEY_FALSE(virt_spin_lock_key);
>>>>
>>>> static bool steal_acc = true;
>>>> @@ -261,17 +261,6 @@ static int pv_time_cpu_down_prepare(unsigned int cpu)
>>>> return 0;
>>>> }
>>>>
>>>> -bool vcpu_is_preempted(int cpu)
>>>> -{
>>>> - struct kvm_steal_time *src;
>>>> -
>>>> - if (!static_branch_unlikely(&virt_preempt_key))
>>>> - return false;
>>>> -
>>>> - src = &per_cpu(steal_time, cpu);
>>>> - return !!(src->preempted & KVM_VCPU_PREEMPTED);
>>>> -}
>>>> -EXPORT_SYMBOL(vcpu_is_preempted);
>>>> #endif
>>>>
>>>> static void pv_cpu_reboot(void *unused)
>>>> --
>>>> 2.39.3
>>>>
>>>>
>>
>>
prev parent reply other threads:[~2026-03-11 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 3:18 [PATCH 0/3] LoongArch: KVM: Some small enhanments Bibo Mao
2026-03-11 3:18 ` [PATCH 1/3] LoongArch: KVM: Add kvm_request_pending checking in kvm_late_check_requests() Bibo Mao
2026-03-11 3:18 ` [PATCH 2/3] LoongArch: KVM: Move host CSR_EENTRY save in context switch Bibo Mao
2026-03-11 3:18 ` [PATCH 3/3] LoongArch: KVM: Set vcpu_is_preempted() macro rather than function Bibo Mao
2026-03-11 3:35 ` Huacai Chen
2026-03-11 3:47 ` Bibo Mao
2026-03-11 4:38 ` Huacai Chen
2026-03-11 6:30 ` Bibo Mao [this message]
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=a72cefd7-8da3-043b-67d2-39ff43f1934b@loongson.cn \
--to=maobibo@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=jgross@suse.com \
--cc=kernel@xen0n.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=zhaotianrui@loongson.cn \
/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
all inboxes | Powered by JetHome®