The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Irix on MIPS -- was kernel mode paged
Date: Mon, 25 Nov 2019 11:12:42 -0800	[thread overview]
Message-ID: <CAP6exYJfJ77nDuAyiti6MHwh5qVrOWf7vbqS9APsSqycQAfdHQ@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfrdWv4JJcvpzsqAoX4+Vv6L4NQyG2xVBpoONBn7eJ6Ocw@mail.gmail.com>

Ah thinks Warner, that was exactly what I was trying to recall.

And I am reminded as well how overloaded the term 'paged' is ... but
yeah, in this case, I was looking for examples where the kernel ran
with essentially no mmu but user programs did.

Note that on Alpha there was an identity mapped space with no MMU as
well but that was only for PAL mode and firmware that used PAL mode
(like LinuxBIOS).

On modern systems we have RISC-V with the no MMU M mode, and I just
got to thinking that running a kernel in M mode would be "what's old
is new again" :-)

Thanks


On Thu, Nov 21, 2019 at 7:24 PM Warner Losh <imp@bsdimp.com> wrote:
>
>
>
> On Thu, Nov 21, 2019, 2:12 PM ron minnich <rminnich@gmail.com> wrote:
>>
>> I'm looking for a reference to any Unix ports where the kernel ran in
>> a non-paged address space and  user mode was paged. I could swear this
>> was done at some point, and memory says it was on a soft-TLB system
>> like the MIPS, to avoid TLB pollution and TLB fault overhead.
>>
>> But maybe I'm nuts. I am happy to hear either answer.
>
>
> Mips had KSEG0 which didn't go through TLB and was mapped to physical memory.  Some MIPS kernels ran in this space to avoid TLB issues...
>
> Warner

      reply	other threads:[~2019-11-25 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 21:11 ron minnich
2019-11-22  3:24 ` Warner Losh
2019-11-25 19:12   ` ron minnich [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=CAP6exYJfJ77nDuAyiti6MHwh5qVrOWf7vbqS9APsSqycQAfdHQ@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=imp@bsdimp.com \
    --cc=tuhs@minnie.tuhs.org \
    /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).