From: Stafford Horne <shorne@gmail.com>
To: Guo Ren <guoren@kernel.org>
Cc: Palmer Dabbelt <palmer@rivosinc.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
Peter Zijlstra <peterz@infradead.org>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
jszhang@kernel.org, Kefeng Wang <wangkefeng.wang@huawei.com>,
Openrisc <openrisc@lists.librecores.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 3/5] openrisc: Move to ticket-spinlock
Date: Tue, 22 Mar 2022 13:10:08 +0900 [thread overview]
Message-ID: <YjlMIGKgYaLLpp5T@antec> (raw)
In-Reply-To: <CAJF2gTSFh0NKLys7kr=UdQWHDyYgg3XmgTJtVaL37Re7QdZ8uw@mail.gmail.com>
On Tue, Mar 22, 2022 at 11:29:13AM +0800, Guo Ren wrote:
> On Tue, Mar 22, 2022 at 7:23 AM Stafford Horne <shorne@gmail.com> wrote:
> >
> > On Wed, Mar 16, 2022 at 04:25:58PM -0700, Palmer Dabbelt wrote:
> > > From: Peter Zijlstra <peterz@infradead.org>
> > >
> > > We have no indications that openrisc meets the qspinlock requirements,
> > > so move to ticket-spinlock as that is more likey to be correct.
> > >
> > > Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> > >
> > > ---
> > >
> > > I have specifically not included Peter's SOB on this, as he sent his
> > > original patch
> > > <https://lore.kernel.org/lkml/YHbBBuVFNnI4kjj3@hirez.programming.kicks-ass.net/>
> > > without one.
> > > ---
> > > arch/openrisc/Kconfig | 1 -
> > > arch/openrisc/include/asm/Kbuild | 5 ++---
> > > arch/openrisc/include/asm/spinlock.h | 3 +--
> > > arch/openrisc/include/asm/spinlock_types.h | 2 +-
> > > 4 files changed, 4 insertions(+), 7 deletions(-)
> >
> > Hello,
> >
> > This series breaks SMP support on OpenRISC. I haven't traced it down yet, it
> > seems trivial but I have a few places to check.
> >
> > I replied to this on a kbuild warning thread, but also going to reply here with
> > more information.
> >
> > https://lore.kernel.org/lkml/YjeY7CfaFKjr8IUc@antec/#R
> >
> > So far this is what I see:
> >
> > * ticket_lock is stuck trying to lock console_sem
> > * it is stuck on atomic_cond_read_acquire
> > reading lock value: returns 0 (*lock is 0x10000)
> > ticket value: is 1
> > * possible issues:
> > - OpenRISC is big endian, that seems to impact ticket_unlock, it looks
> All csky & riscv are little-endian, it seems the series has a bug with
> big-endian. Is that all right for qemu? (If qemu was all right, but
> real hardware failed.)
Hi Guo Ren,
OpenRISC real hardware and QEMU are both big-endian. It fails on both.
I replied on patch 1/5 with a suggested patch which fixes the issue for me.
Please have a look.
BTW. now I can look into the sparse warnings.
-Stafford
WARNING: multiple messages have this Message-ID (diff)
From: Stafford Horne <shorne@gmail.com>
To: Guo Ren <guoren@kernel.org>
Cc: Palmer Dabbelt <palmer@rivosinc.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
Peter Zijlstra <peterz@infradead.org>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
jszhang@kernel.org, Kefeng Wang <wangkefeng.wang@huawei.com>,
Openrisc <openrisc@lists.librecores.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 3/5] openrisc: Move to ticket-spinlock
Date: Tue, 22 Mar 2022 13:10:08 +0900 [thread overview]
Message-ID: <YjlMIGKgYaLLpp5T@antec> (raw)
In-Reply-To: <CAJF2gTSFh0NKLys7kr=UdQWHDyYgg3XmgTJtVaL37Re7QdZ8uw@mail.gmail.com>
On Tue, Mar 22, 2022 at 11:29:13AM +0800, Guo Ren wrote:
> On Tue, Mar 22, 2022 at 7:23 AM Stafford Horne <shorne@gmail.com> wrote:
> >
> > On Wed, Mar 16, 2022 at 04:25:58PM -0700, Palmer Dabbelt wrote:
> > > From: Peter Zijlstra <peterz@infradead.org>
> > >
> > > We have no indications that openrisc meets the qspinlock requirements,
> > > so move to ticket-spinlock as that is more likey to be correct.
> > >
> > > Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> > >
> > > ---
> > >
> > > I have specifically not included Peter's SOB on this, as he sent his
> > > original patch
> > > <https://lore.kernel.org/lkml/YHbBBuVFNnI4kjj3@hirez.programming.kicks-ass.net/>
> > > without one.
> > > ---
> > > arch/openrisc/Kconfig | 1 -
> > > arch/openrisc/include/asm/Kbuild | 5 ++---
> > > arch/openrisc/include/asm/spinlock.h | 3 +--
> > > arch/openrisc/include/asm/spinlock_types.h | 2 +-
> > > 4 files changed, 4 insertions(+), 7 deletions(-)
> >
> > Hello,
> >
> > This series breaks SMP support on OpenRISC. I haven't traced it down yet, it
> > seems trivial but I have a few places to check.
> >
> > I replied to this on a kbuild warning thread, but also going to reply here with
> > more information.
> >
> > https://lore.kernel.org/lkml/YjeY7CfaFKjr8IUc@antec/#R
> >
> > So far this is what I see:
> >
> > * ticket_lock is stuck trying to lock console_sem
> > * it is stuck on atomic_cond_read_acquire
> > reading lock value: returns 0 (*lock is 0x10000)
> > ticket value: is 1
> > * possible issues:
> > - OpenRISC is big endian, that seems to impact ticket_unlock, it looks
> All csky & riscv are little-endian, it seems the series has a bug with
> big-endian. Is that all right for qemu? (If qemu was all right, but
> real hardware failed.)
Hi Guo Ren,
OpenRISC real hardware and QEMU are both big-endian. It fails on both.
I replied on patch 1/5 with a suggested patch which fixes the issue for me.
Please have a look.
BTW. now I can look into the sparse warnings.
-Stafford
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 3/5] openrisc: Move to ticket-spinlock
Date: Tue, 22 Mar 2022 13:10:08 +0900 [thread overview]
Message-ID: <YjlMIGKgYaLLpp5T@antec> (raw)
In-Reply-To: <CAJF2gTSFh0NKLys7kr=UdQWHDyYgg3XmgTJtVaL37Re7QdZ8uw@mail.gmail.com>
On Tue, Mar 22, 2022 at 11:29:13AM +0800, Guo Ren wrote:
> On Tue, Mar 22, 2022 at 7:23 AM Stafford Horne <shorne@gmail.com> wrote:
> >
> > On Wed, Mar 16, 2022 at 04:25:58PM -0700, Palmer Dabbelt wrote:
> > > From: Peter Zijlstra <peterz@infradead.org>
> > >
> > > We have no indications that openrisc meets the qspinlock requirements,
> > > so move to ticket-spinlock as that is more likey to be correct.
> > >
> > > Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> > >
> > > ---
> > >
> > > I have specifically not included Peter's SOB on this, as he sent his
> > > original patch
> > > <https://lore.kernel.org/lkml/YHbBBuVFNnI4kjj3@hirez.programming.kicks-ass.net/>
> > > without one.
> > > ---
> > > arch/openrisc/Kconfig | 1 -
> > > arch/openrisc/include/asm/Kbuild | 5 ++---
> > > arch/openrisc/include/asm/spinlock.h | 3 +--
> > > arch/openrisc/include/asm/spinlock_types.h | 2 +-
> > > 4 files changed, 4 insertions(+), 7 deletions(-)
> >
> > Hello,
> >
> > This series breaks SMP support on OpenRISC. I haven't traced it down yet, it
> > seems trivial but I have a few places to check.
> >
> > I replied to this on a kbuild warning thread, but also going to reply here with
> > more information.
> >
> > https://lore.kernel.org/lkml/YjeY7CfaFKjr8IUc at antec/#R
> >
> > So far this is what I see:
> >
> > * ticket_lock is stuck trying to lock console_sem
> > * it is stuck on atomic_cond_read_acquire
> > reading lock value: returns 0 (*lock is 0x10000)
> > ticket value: is 1
> > * possible issues:
> > - OpenRISC is big endian, that seems to impact ticket_unlock, it looks
> All csky & riscv are little-endian, it seems the series has a bug with
> big-endian. Is that all right for qemu? (If qemu was all right, but
> real hardware failed.)
Hi Guo Ren,
OpenRISC real hardware and QEMU are both big-endian. It fails on both.
I replied on patch 1/5 with a suggested patch which fixes the issue for me.
Please have a look.
BTW. now I can look into the sparse warnings.
-Stafford
next prev parent reply other threads:[~2022-03-22 4:10 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 23:25 [PATCH 0/5] Generic Ticket Spinlocks Palmer Dabbelt
2022-03-16 23:25 ` [OpenRISC] " Palmer Dabbelt
2022-03-16 23:25 ` Palmer Dabbelt
2022-03-16 23:25 ` [PATCH 1/5] asm-generic: qspinlock: Indicate the use of mixed-size atomics Palmer Dabbelt
2022-03-16 23:25 ` [OpenRISC] " Palmer Dabbelt
2022-03-16 23:25 ` Palmer Dabbelt
2022-03-17 17:46 ` Waiman Long
2022-03-17 17:46 ` [OpenRISC] " Waiman Long
2022-03-17 17:46 ` Waiman Long
2022-03-16 23:25 ` [PATCH 2/5] asm-generic: ticket-lock: New generic ticket-based spinlock Palmer Dabbelt
2022-03-16 23:25 ` [OpenRISC] " Palmer Dabbelt
2022-03-16 23:25 ` Palmer Dabbelt
2022-03-17 9:46 ` Peter Zijlstra
2022-03-17 9:46 ` [OpenRISC] " Peter Zijlstra
2022-03-17 9:46 ` Peter Zijlstra
2022-03-17 13:57 ` Boqun Feng
2022-03-17 13:57 ` [OpenRISC] " Boqun Feng
2022-03-17 13:57 ` Boqun Feng
2022-03-17 15:03 ` Waiman Long
2022-03-17 15:03 ` [OpenRISC] " Waiman Long
2022-03-17 15:03 ` Waiman Long
2022-03-17 15:34 ` Boqun Feng
2022-03-17 15:34 ` [OpenRISC] " Boqun Feng
2022-03-17 15:34 ` Boqun Feng
2022-03-17 18:04 ` Waiman Long
2022-03-17 18:04 ` [OpenRISC] " Waiman Long
2022-03-17 18:04 ` Waiman Long
2022-03-16 23:25 ` [PATCH 3/5] openrisc: Move to ticket-spinlock Palmer Dabbelt
2022-03-16 23:25 ` [OpenRISC] " Palmer Dabbelt
2022-03-16 23:25 ` Palmer Dabbelt
2022-03-17 9:46 ` Peter Zijlstra
2022-03-17 9:46 ` [OpenRISC] " Peter Zijlstra
2022-03-17 9:46 ` Peter Zijlstra
2022-03-21 21:29 ` Stafford Horne
2022-03-21 21:29 ` [OpenRISC] " Stafford Horne
2022-03-21 21:29 ` Stafford Horne
2022-03-22 3:29 ` Guo Ren
2022-03-22 3:29 ` [OpenRISC] " Guo Ren
2022-03-22 3:29 ` Guo Ren
2022-03-22 4:10 ` Stafford Horne [this message]
2022-03-22 4:10 ` [OpenRISC] " Stafford Horne
2022-03-22 4:10 ` Stafford Horne
2022-03-22 6:45 ` Guo Ren
2022-03-22 6:45 ` [OpenRISC] " Guo Ren
2022-03-22 6:45 ` Guo Ren
2022-03-16 23:25 ` [PATCH 4/5] RISC-V: Move to ticket-spinlocks Palmer Dabbelt
2022-03-16 23:25 ` [OpenRISC] " Palmer Dabbelt
2022-03-16 23:25 ` Palmer Dabbelt
2022-03-16 23:26 ` [PATCH 5/5] RISC-V: Move to queued RW locks Palmer Dabbelt
2022-03-16 23:26 ` [OpenRISC] " Palmer Dabbelt
2022-03-16 23:26 ` Palmer Dabbelt
2022-03-17 9:47 ` Peter Zijlstra
2022-03-17 9:47 ` [OpenRISC] " Peter Zijlstra
2022-03-17 9:47 ` Peter Zijlstra
2022-03-17 9:16 ` [PATCH 0/5] Generic Ticket Spinlocks Arnd Bergmann
2022-03-17 9:16 ` [OpenRISC] " Arnd Bergmann
2022-03-17 9:16 ` Arnd Bergmann
2022-03-17 11:09 ` Heiko Stübner
2022-03-17 11:09 ` [OpenRISC] " Heiko =?unknown-8bit?q?St=C3=BCbner?=
2022-03-17 11:09 ` Heiko Stübner
2022-03-18 7:24 ` Guo Ren
2022-03-18 7:24 ` [OpenRISC] " Guo Ren
2022-03-18 7:24 ` Guo Ren
2022-03-18 8:40 ` Guo Ren
2022-03-18 8:40 ` [OpenRISC] " Guo Ren
2022-03-18 8:40 ` Guo Ren
2022-03-22 18:18 ` Conor Dooley
2022-03-22 18:18 ` [OpenRISC] " Conor Dooley
2022-03-22 18:18 ` Conor Dooley
2022-03-22 20:02 ` Palmer Dabbelt
2022-03-22 20:02 ` [OpenRISC] " Palmer Dabbelt
2022-03-22 20:02 ` Palmer Dabbelt
2022-03-22 20:19 ` Conor Dooley
2022-03-22 20:19 ` [OpenRISC] " Conor Dooley
2022-03-22 20:19 ` Conor Dooley
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=YjlMIGKgYaLLpp5T@antec \
--to=shorne@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=guoren@kernel.org \
--cc=jonas@southpole.se \
--cc=jszhang@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=openrisc@lists.librecores.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=wangkefeng.wang@huawei.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 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.