[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210611110019.GA579376@roeck-us.net>
Date: Fri, 11 Jun 2021 04:00:19 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Andreas Schwab <schwab@...ux-m68k.org>
Cc: Alex Ghiti <alex@...ti.fr>, Palmer Dabbelt <palmer@...belt.com>,
corbet@....net, Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, Arnd Bergmann <arnd@...db.de>,
aryabinin@...tuozzo.com, glider@...gle.com, dvyukov@...gle.com,
linux-doc@...r.kernel.org, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org, kasan-dev@...glegroups.com,
linux-arch@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v5 1/3] riscv: Move kernel mapping outside of linear
mapping
On Thu, Jun 10, 2021 at 07:29:15PM +0200, Andreas Schwab wrote:
> On Jun 10 2021, Guenter Roeck wrote:
>
> > On Thu, Jun 10, 2021 at 07:11:38PM +0200, Andreas Schwab wrote:
> >> On Jun 10 2021, Guenter Roeck wrote:
> >>
> >> > On Thu, Jun 10, 2021 at 06:39:39PM +0200, Andreas Schwab wrote:
> >> >> On Apr 18 2021, Alex Ghiti wrote:
> >> >>
> >> >> > To sum up, there are 3 patches that fix this series:
> >> >> >
> >> >> > https://patchwork.kernel.org/project/linux-riscv/patch/20210415110426.2238-1-alex@ghiti.fr/
> >> >> >
> >> >> > https://patchwork.kernel.org/project/linux-riscv/patch/20210417172159.32085-1-alex@ghiti.fr/
> >> >> >
> >> >> > https://patchwork.kernel.org/project/linux-riscv/patch/20210418112856.15078-1-alex@ghiti.fr/
> >> >>
> >> >> Has this been fixed yet? Booting is still broken here.
> >> >>
> >> >
> >> > In -next ?
> >>
> >> No, -rc5.
> >>
> > Booting v5.13-rc5 in qemu works for me for riscv32 and riscv64,
> > but of course that doesn't mean much. Just wondering, not knowing
> > the context - did you provide details ?
>
> Does that work for you:
>
> https://github.com/openSUSE/kernel-source/blob/master/config/riscv64/default
>
That isn't an upstream kernel configuration; it looks like includes suse
patches. But, yes, it does crash almost immediately if I build an upstream
kernel based on it and try to run that kernel in qemu. I did not try to
track it down further; after all, it might just be that the configuration
is inappropriate for use with qemu. But the configuration isn't really
what I had asked.
Guenter
Powered by blists - more mailing lists