linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: Rob Landley <rob@landley.net>
Cc: Linux-sh list <linux-sh@vger.kernel.org>,
	Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH] Fix the j-core SOC build.
Date: Wed, 10 Nov 2021 16:33:46 -0500	[thread overview]
Message-ID: <20211110213345.GK7074@brightrain.aerifal.cx> (raw)
In-Reply-To: <20211003021851.GA2559@brightrain.aerifal.cx>

On Sat, Oct 02, 2021 at 10:18:51PM -0400, Rich Felker wrote:
> On Sat, Oct 02, 2021 at 02:32:15PM -0500, Rob Landley wrote:
> > From: Rob Landley <rob@landley.net>
> > 
> > Commit b67177ecd956 broke the j-core SOC build with a link failure, because
> > mm/percpu.c function pcpu_post_unmap_tlb_flush() calls flush_tlb_kernel_range()
> > which is defined under #ifdef CONFIG_MMU.
> > 
> > Signed-off-by: Rob Landley <rob@landley.net>
> > ---
> > 
> >  arch/sh/kernel/smp.c |    5 +++++
> >  1 file changed, 5 insertions(+)
> > 
> > diff --git a/arch/sh/kernel/smp.c b/arch/sh/kernel/smp.c
> > index 65924d9ec245..3ec8f32aad85 100644
> > --- a/arch/sh/kernel/smp.c
> > +++ b/arch/sh/kernel/smp.c
> > @@ -468,4 +468,9 @@ void flush_tlb_one(unsigned long asid, unsigned long vaddr)
> >  	local_flush_tlb_one(asid, vaddr);
> >  }
> > 
> > +#else
> > +void flush_tlb_kernel_range(unsigned long start, unsigned long end)
> > +{
> > +	local_flush_tlb_all();
> > +}
> >  #endif
> 
> local_flush_tlb_all() is defined in arch/sh/mm/nommu.c as BUG(); so
> this is most likely wrong unless it just doesn't get called. I think
> there should probably be something at a very general level dummying
> out these functions/macros on nommu but I don't know where it should
> be.

I've looked into this some more, and while arch/arm does dummy its
equivalent functions out on nommu, arch/sh has always had them as
BUG(), and indeed it makes some sense to catch erroneous usage.
pcpu_post_unmap_tlb_flush should probably have the flush under #ifdef
CONFIG_MMU or something.

I've added the author of the commit that broke this to Cc in case he
has any thoughts.

Rich

  reply	other threads:[~2021-11-10 21:33 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 [this message]
2021-11-11  0:53     ` Rich Felker
2021-11-11  2:01       ` Dennis Zhou
2021-11-11  5:39         ` Rob Landley
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=20211110213345.GK7074@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=rob@landley.net \
    /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).