From: Conor Dooley <conor@kernel.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Vlastimil Babka <vbabka@suse.cz>,
Conor Dooley <Conor.Dooley@microchip.com>
Subject: Re: [PATCH] riscv: Update k210 defconfigs
Date: Mon, 14 Nov 2022 21:05:03 +0000 [thread overview]
Message-ID: <Y3Ktf8KXUnCl3Zbf@spud> (raw)
In-Reply-To: <ce2a2873-c031-228d-e21f-e9918660e4b3@opensource.wdc.com>
On Tue, Nov 15, 2022 at 05:58:11AM +0900, Damien Le Moal wrote:
> On 11/15/22 05:05, Conor Dooley wrote:
> > On Mon, Nov 14, 2022 at 10:31:51AM +0900, Damien Le Moal wrote:
> >> In preparation for SLOB deprecation, update the nommu_k210_* defconfigs
> >> to switch to using SLUB. To save memory, CONFIG_SLUB_CPU_PARTIAL is not
> >> selected.
> >>
> >> Suggested-by: Vlastimil Babka <vbabka@suse.cz>
> >> Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
> >
> > Hey,
> > Gave it a go w/ your v21 branch. To me, seems about as usable as it was
> > before...
>
> Please use upstream buildroot. Everything is in master for this board and
> that v21 branch is dead now.
Ah cool, willdo.
> > Tested-by: Conor Dooley <conor.dooley@microchip.com>
>
> I used buildroot defconfigs sipeed_maix_bit_defconfig and
> sipeed_maix_bit_sd_card_defconfig. Both had the same issue with SLUB: lots
> of errors with the shell, including failures for the init shell commands.
> And sometimes I end up with a prompt but no way to run any shell command
> at all. I guess that depends on fragmentation of the memory after boot
> completes.
Yeah, I guess I was just fortunate (or unfortunate?) and did not see any
- but I only ran the most trivial of commands after boot. I did give it
a couple of boots since I'd seen you mention problems but only 4/5
times.
>
> >
> > btw, what's the craic with that? Looks like you actually landed in
> > upstream buildroot fairly soon after you pointed me at your series.
> > Anything missing from buildroot, or did it all land?
>
> Everything landed, plus some (some build fixes).
>
> Palmer,
>
> Please hold on before applying this patch. Discussion still going on about
> SLUB.
I'm only keeping half an eye on that thread, lmk if you'd like me to
re-test this at some point.
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-11-14 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 1:31 [PATCH] riscv: Update k210 defconfigs Damien Le Moal
2022-11-14 20:05 ` Conor Dooley
2022-11-14 20:58 ` Damien Le Moal
2022-11-14 21:05 ` Conor Dooley [this message]
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=Y3Ktf8KXUnCl3Zbf@spud \
--to=conor@kernel.org \
--cc=Conor.Dooley@microchip.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=vbabka@suse.cz \
/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.