Linux-MIPS Archive on lore.kernel.org
 help / color / Atom feed
From: Huacai Chen <chenhc@lemote.com>
To: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <jhogan@kernel.org>,
	Paul Burton <paul.burton@mips.com>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>,
	"open list:MIPS" <linux-mips@vger.kernel.org>,
	Fuxin Zhang <zhangfx@lemote.com>,
	Zhangjin Wu <wuzhangjin@gmail.com>
Subject: Re: [PATCH V2] MIPS: Loongson: Add board_ebase_setup() support
Date: Fri, 15 Nov 2019 16:22:19 +0800
Message-ID: <CAAhV-H7drSBCsB-pMBDuQ0v-J9=vWPWaphGB2zM1Ucij6xf4TA@mail.gmail.com> (raw)
In-Reply-To: <CAAhV-H7v6xfBY8SpNKnhTh075=HQWggP72UN5=jQGyOH3BdFdg@mail.gmail.com>

Hi, Paul,

On Sat, Nov 9, 2019 at 7:02 PM Huacai Chen <chenhc@lemote.com> wrote:
>
> Hi, Paul
>
> On Sat, Nov 9, 2019 at 3:11 AM Paul Burton <paulburton@kernel.org> wrote:
> >
> > Hi Huacai,
> >
> > On Mon, Nov 04, 2019 at 02:09:41PM +0800, Huacai Chen wrote:
> > > Old processors before Loongson-3A2000 have a 32bit ebase register and
> > > have no WG bit, new processors since Loongson-3A2000 have a 64bit ebase
> > > register and do have the WG bit. Unfortunately, Loongson processors
> > > which have the WG bit are slightly different from MIPS R2. This makes
> > > the generic ebase setup not suitable for every scenarios.
> >
> > Can you describe how the Loongson WG bit differs from the WG bit as
> > architecturally defined? This patch may make things work for you but it
> > doesn't give us any record of what the hardware errata is or what we
> > actually need to do to work with the broken WG bit.
> >
> > For example - right now Loongson kernels don't use the WG bit at all, so
> > what's the problem? It doesn't matter if WG has different behavior if we
> > don't use it.
> >
> > So one option here might be to just continue to not indicate support for
> > the WG bit. It does look like the kernel ought to be ensuring the
> > exception vector it allocates is at a suitable address in this case, and
> > currently isn't. Something like the (untested) patch below ought to
> > address that. In practice though memblock is configured to allocate
> > bottom-up until after this point so it should be unlikely we'll get an
> > unsuitable address, and there's a WARN_ON() in trap_init() that would
> > already tell you if that happened.
> >
> > > To make Loongson's kernel be more robust, we add a board_ebase_setup()
> > > hook to ensure that CKSEG0 is always used for ebase. This is also useful
> > > on platforms where BIOS doesn't initialise an appropriate ebase.
> >
> > Can you also elaborate on that? I'm not sure why this would help on
> > systems that don't initialize EBase - the kernel unconditionally sets
> > EBase for >= MIPSr2 systems in configure_exception_vector() anyway, and
> > since v5.2 it doesn't even try to inherit whatever the bootloader used.
> >
> I'm sorry that I haven't seen the changes in 5.2. My original problem
> has been fixed with the below two commits.
> 172dcd935c34b022729f45a7bbaae5cc052 ("MIPS: Always allocate exception
> vector for MIPSr2+")
> de56d4c1da3e68f0ca468a55f6677bef3cee ("MIPS: Remove duplicate EBase
> configuration")
>
> My own patch is only needed in 4.9/4.14/4.19, and I can backport the
> above two commits while completely drop my own patch.
Maybe this patch is still neccesary. The above two commits surely make
it possible to boot with any firmware, but dynamically allocated ebase
cannot work perfectly with STR(suspend) and STD(hibernation).

STR is fixable, because we can save ebase at suspend and restore it at
resume. However, STD is very diffcult to fix, because we cannot assure
the ebase allocated by the new kernel is the same as the old kernel,
and I think change ebase during kernel switching is dangerous.

So could you please consider to accept this patch? Thanks.
>
> Thanks,
> Huacai
>
> > Thanks,
> >     Paul
> >
> > ---
> > diff --git a/arch/mips/kernel/traps.c b/arch/mips/kernel/traps.c
> > index 342e41de9d64..a25ee41eff48 100644
> > --- a/arch/mips/kernel/traps.c
> > +++ b/arch/mips/kernel/traps.c
> > @@ -2271,7 +2271,7 @@ void __init trap_init(void)
> >         extern char except_vec4;
> >         extern char except_vec3_r4000;
> >         unsigned long i, vec_size;
> > -       phys_addr_t ebase_pa;
> > +       phys_addr_t ebase_pa, ebase_limit;
> >
> >         check_wait();
> >
> > @@ -2287,7 +2287,21 @@ void __init trap_init(void)
> >                 else
> >                         vec_size = PAGE_SIZE;
> >
> > -               ebase_pa = memblock_phys_alloc(vec_size, 1 << fls(vec_size));
> > +               /*
> > +                * If we have support for the EBase.WG bit then allow the
> > +                * exception vector to be located anywhere. When EBase.WG is
> > +                * not supported EBase is limited to a (c)kseg[01] address, so
> > +                * we must ensure the allocated vector is in memory accessible
> > +                * via those unmapped regions.
> > +                */
> > +               if (cpu_has_ebase_wg)
> > +                       ebase_limit = MEMBLOCK_ALLOC_ACCESSIBLE;
> > +               else
> > +                       ebase_limit = CKSEG1 - CKSEG0;
> > +
> > +               ebase_pa = memblock_phys_alloc_range(vec_size,
> > +                                                    1 << fls(vec_size),
> > +                                                    0, ebase_limit);
> >                 if (!ebase_pa)
> >                         panic("%s: Failed to allocate %lu bytes align=0x%x\n",
> >                               __func__, vec_size, 1 << fls(vec_size));

      reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04  6:09 Huacai Chen
2019-11-07 11:47 ` Jiaxun Yang
2019-11-08  1:21   ` Huacai Chen
2019-11-08 19:11 ` Paul Burton
2019-11-09 11:02   ` Huacai Chen
2019-11-15  8:22     ` Huacai Chen [this message]

Reply instructions:

You may reply publically 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='CAAhV-H7drSBCsB-pMBDuQ0v-J9=vWPWaphGB2zM1Ucij6xf4TA@mail.gmail.com' \
    --to=chenhc@lemote.com \
    --cc=jhogan@kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul.burton@mips.com \
    --cc=paulburton@kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=wuzhangjin@gmail.com \
    --cc=zhangfx@lemote.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

Linux-MIPS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-mips/0 linux-mips/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-mips linux-mips/ https://lore.kernel.org/linux-mips \
		linux-mips@vger.kernel.org
	public-inbox-index linux-mips

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-mips


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git