From: Waiman Long <longman@redhat.com>
To: maobibo <maobibo@loongson.cn>, Uros Bizjak <ubizjak@gmail.com>,
linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>
Subject: Re: [PATCH] locking/pvqspinlock: Correct the type of "old" variable in pv_kick_node()
Date: Mon, 22 Jul 2024 11:13:02 -0400 [thread overview]
Message-ID: <64b0aba3-6eab-4418-9019-a7e1123fba96@redhat.com> (raw)
In-Reply-To: <62c029b7-13dc-f4fc-d67a-7bd86f973e2f@loongson.cn>
On 7/22/24 02:54, maobibo wrote:
> Uros,
>
> Sorry for late reply because of weekend time. This modification works
> well for me.
>
> In later I want to define pv_node::state as int type on LoongArch
> because there is only int32/int64 cmpxchg is better supported on the
> system, however that is another issue.
I thought about changing pv_node::state to int, but that requires
changing the pv_wait() call to use int too. That doesn't work because
pv_wait() is also used to monitor the state of the lock byte of the
qspinlock. In essence, we can't use pvqspinlock if 8-bit cmpxchg isn't
supported.
Cheers,
Longman
>
> Tested-by:Bibo Mao <maobibo@loongson.cn>
>
> On 2024/7/22 上午12:45, Uros Bizjak wrote:
>> "enum vcpu_state" is not compatible with "u8" type for all targets,
>> resulting in:
>>
>> error: initialization of 'u8 *' {aka 'unsigned char *'} from
>> incompatible pointer type 'enum vcpu_state *'
>>
>> for LoongArch. Correct the type of "old" variable to "u8".
>>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> Cc: Ingo Molnar <mingo@kernel.org>
>> Cc: Will Deacon <will@kernel.org>
>> Cc: Waiman Long <longman@redhat.com>
>> Cc: Boqun Feng <boqun.feng@gmail.com>
>> Fixes: fea0e1820b51 ("locking/pvqspinlock: Use try_cmpxchg() in
>> qspinlock_paravirt.h")
>> Reported-by: Bibo Mao <maobibo@loongson.cn>
>> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
>> Closes:
>> https://lore.kernel.org/lkml/20240719024010.3296488-1-maobibo@loongson.cn/
>> ---
>> kernel/locking/qspinlock_paravirt.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/locking/qspinlock_paravirt.h
>> b/kernel/locking/qspinlock_paravirt.h
>> index f5a36e67b593..ac2e22502741 100644
>> --- a/kernel/locking/qspinlock_paravirt.h
>> +++ b/kernel/locking/qspinlock_paravirt.h
>> @@ -357,7 +357,7 @@ static void pv_wait_node(struct mcs_spinlock
>> *node, struct mcs_spinlock *prev)
>> static void pv_kick_node(struct qspinlock *lock, struct
>> mcs_spinlock *node)
>> {
>> struct pv_node *pn = (struct pv_node *)node;
>> - enum vcpu_state old = vcpu_halted;
>> + u8 old = vcpu_halted;
>> /*
>> * If the vCPU is indeed halted, advance its state to match
>> that of
>> * pv_wait_node(). If OTOH this fails, the vCPU was running and
>> will
>>
>
next prev parent reply other threads:[~2024-07-22 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 16:45 Uros Bizjak
2024-07-21 20:45 ` Waiman Long
2024-07-22 6:54 ` maobibo
2024-07-22 15:13 ` Waiman Long [this message]
2024-07-23 1:13 ` maobibo
2024-07-29 10:24 ` [tip: locking/urgent] " tip-bot2 for Uros Bizjak
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=64b0aba3-6eab-4418-9019-a7e1123fba96@redhat.com \
--to=longman@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maobibo@loongson.cn \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=ubizjak@gmail.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®