From: Patrick Doyle <wpdster@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: post@pfrst.de, linux-mips@vger.kernel.org
Subject: Re: Address space in MIPS Linux kernel
Date: Fri, 20 Mar 2020 15:08:36 -0400 [thread overview]
Message-ID: <CAF_dkJDBtT=G+i9hPM81ik1zK2aiRbo3T4wT27zbubrunW7+og@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2003201517230.2689954@eddie.linux-mips.org>
On Fri, Mar 20, 2020 at 11:39 AM Maciej W. Rozycki <macro@linux-mips.org> wrote:
> KSEG2 addresses are handed out with virtual allocations, typically
> `vmalloc' and friends (also used for mapping kernel modules), but also
> `ioremap' and friends if hardware constraints mandate it. KSEG0 addresses
> are handed out with regular allocations made with `kmalloc' and friends,
> and also `ioremap' and friends where feasible. Also addresses coming from
> the kernel executable and the stack will be in KSEG0.
>
> This is for 32-bit MIPS/Linux configurations; 64-bit ones have additional
> segments, which will be used accordingly.
>
> HTH,
>
> Maciej
Thanks. I tracked down the call to vmalloc. I'm still have no clue
why we are triggering a kernel panic when/where we do, but it clearly
does not have anything to do with calling memmove() from KSEG2 space
to KSEG0 space, and I am now looking elsewhere (like what resources
may get allocated/locked on the way to that call to memmove() that
don't get freed/unlocked on the way back up, or what resources were
not locked that should have been).
--wpd
prev parent reply other threads:[~2020-03-20 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 22:25 Address space in MIPS Linux kernel Patrick Doyle
[not found] ` <Pine.LNX.4.64.2003061230320.1467@Mobile0.Peter>
2020-03-06 14:51 ` Patrick Doyle
2020-03-20 15:39 ` Maciej W. Rozycki
2020-03-20 19:08 ` Patrick Doyle [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='CAF_dkJDBtT=G+i9hPM81ik1zK2aiRbo3T4wT27zbubrunW7+og@mail.gmail.com' \
--to=wpdster@gmail.com \
--cc=linux-mips@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=post@pfrst.de \
/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).