From: Rob Landley <rob@landley.net>
To: Dennis Zhou <dennis@kernel.org>, Rich Felker <dalias@libc.org>
Cc: Linux-sh list <linux-sh@vger.kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] Fix the j-core SOC build.
Date: Wed, 10 Nov 2021 23:39:15 -0600 [thread overview]
Message-ID: <7d97a4d2-f7db-9d8d-21c2-ab80be03e364@landley.net> (raw)
In-Reply-To: <YYx5ZuWFSNOu/wah@fedora>
On 11/10/21 8:01 PM, Dennis Zhou wrote:
> I'm surprised I haven't heard any reports of this until now. Thanks for
> ccing me. Fwiw, it's generally good to cc the author / subsystem
> maintainer when there is an issue.
>
> I would need to think about it a little bit more, but I think
> percpu-km.c was written more in the mindset of !MMU == !SMP. It sounds
> like for superh that's not true.
>
> Given that, if sh has no MMU,
sh1 and sh2 are nommu. sh3 and sh4 have mmu. J2 is an SMP sh2 compatible (with
some backported sh3 instructions plus a cmpxchg variant to make the SMP work).
It is, as far as I know, the only nommu SMP in the tree, but it worked for us
until recently.
Rob
next prev parent reply other threads:[~2021-11-11 5:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 19:32 [PATCH] Fix the j-core SOC build Rob Landley
2021-10-02 21:39 ` John Paul Adrian Glaubitz
2021-10-03 2:18 ` Rich Felker
2021-11-10 21:33 ` Rich Felker
2021-11-11 0:53 ` Rich Felker
2021-11-11 2:01 ` Dennis Zhou
2021-11-11 5:39 ` Rob Landley [this message]
2021-11-11 14:16 ` Rich Felker
2021-11-12 18:34 ` Dennis Zhou
2021-11-12 18:57 ` Rich Felker
2021-11-12 22:41 ` Dennis Zhou
2021-10-03 9:10 ` Sergey Shtylyov
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=7d97a4d2-f7db-9d8d-21c2-ab80be03e364@landley.net \
--to=rob@landley.net \
--cc=dalias@libc.org \
--cc=dennis@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.org \
--cc=npiggin@gmail.com \
/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).