From: Dan Malek <dan@embeddededge•com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades•com>
Cc: linux-ppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: Re: map_page() and pinned TLB entries
Date: Thu, 16 Jun 2005 17:13:19 -0400 [thread overview]
Message-ID: <8efaee2824f500e906c2c05526ea3214@embeddededge.com> (raw)
In-Reply-To: <20050616144739.GA1559@logos.cnet>
On Jun 16, 2005, at 10:47 AM, Marcelo Tosatti wrote:
> What would be an elegant way of dealing with this? We can insert
> a conditional there such that only addresses not covered
> by other mappings (in this case the 8Mbyte entry) get flushed.
I'd like to make _tlbie() a macro on 8xx that simply tests the VA
and doesn't invalidate anything in the pinned space. Of course,
the code shouldn't be doing this anyway, and I think this
should be treated as a bug if it happens. If the Linux VM
thinks it needs to be doing this, pinned space isn't going to work.
The _tlbie() is an exported symbol, I suspect for MOL, so
we have to accommodate that.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-06-16 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 14:47 map_page() and pinned TLB entries Marcelo Tosatti
2005-06-16 21:13 ` Dan Malek [this message]
2005-06-16 16:47 ` Marcelo Tosatti
2005-06-16 22:17 ` 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=8efaee2824f500e906c2c05526ea3214@embeddededge.com \
--to=dan@embeddededge$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=marcelo.tosatti@cyclades$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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