From: Dan Malek <dan@embeddededge.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: CONFIG_PIN_TLB experiments
Date: Thu, 5 May 2005 12:10:23 -0400 [thread overview]
Message-ID: <22f91260e4268ca4830615ec10d0683e@embeddededge.com> (raw)
In-Reply-To: <20050504192238.GA3461@logos.cnet>
On May 4, 2005, at 3:22 PM, Marcelo Tosatti wrote:
> I'm trying to boot a kernel which does not create kernel pte's
> from 0xc000000 till 0xc080000.
The kernel will always (and must) create PTEs for all VM
spaces, It's our choice to not use them. In the case of Pinned
entries, what is supposed to happen is we load an entry that
covers a large space. Since we never get a miss fault, we
never look at the PTE tables to load something different.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-05-05 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 20:42 CONFIG_PIN_TLB experiments Marcelo Tosatti
2005-05-03 18:14 ` Conn Clark
2005-05-04 19:22 ` Marcelo Tosatti
2005-05-05 16:10 ` Dan Malek [this message]
2005-05-05 17:06 ` Conn Clark
2005-05-05 14:11 ` Marcelo Tosatti
2005-05-03 18:47 ` Dan Malek
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=22f91260e4268ca4830615ec10d0683e@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=marcelo.tosatti@cyclades.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
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).