All of lore.kernel.org
 help / color / mirror / Atom feed
From: David VomLehn <dvomlehn@cisco.com>
To: linux-mips@linux-mips.org
Subject: Re: Does HIGHMEM work on 32-bit MIPS ports?
Date: Tue, 26 Feb 2008 13:06:53 -0800	[thread overview]
Message-ID: <47C47F6D.7070305@cisco.com> (raw)

> On Wed, 20 Feb 2008, David VomLehn wrote:
>
> > Hmm, this is not good. I've got a MIPS 24Kc processor with a very
> > awkward memory layout. Any hints?
>
>  What does it mean "very awkward"?  What sort of problems do you have 
> that you are trying to solve?
>
>   Maciej
Specifically, we have two banks of memory. The first starts at 
0x10000000, which is no big deal (other than wasting the page map 
entries for the first chunk of memory). The second starts at 0x60000000, so:

   1. We have to access it with high memory, and
   2. There is a huge section of unused page map entries.

As it turns out, it is starting to look like we're making progress with 
the problem with high memory: In __flush_dcache_page, nothing is done if 
PageHighMem() returns true. Not surprisingly, this leads to Bad 
Things(tm). What we are working through now is making sure that we 
understand exactly what *should* be happening.

-- 
David VomLehn, dvomlehn@cisco.com
The opinions expressed herein are likely mine, but might not be my employer's...

             reply	other threads:[~2008-02-26 21:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 21:06 David VomLehn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-07  5:02 Does HIGHMEM work on 32-bit MIPS ports? David VomLehn
2008-03-05 22:55 David VomLehn
2008-03-06 15:44 ` Ralf Baechle
2008-02-20 19:20 David VomLehn
2008-02-21 10:55 ` Maciej W. Rozycki
2008-02-20  4:09 David VomLehn
2008-02-20 16:18 ` Ralf Baechle

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=47C47F6D.7070305@cisco.com \
    --to=dvomlehn@cisco.com \
    --cc=linux-mips@linux-mips.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 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.