All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Mike Beede <mbeede@cisco.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Possible VM fix(s) for 2.4 PPC port
Date: Mon, 08 Jan 2001 12:35:18 -0500	[thread overview]
Message-ID: <3A59FA56.688369B4@mvista.com> (raw)
In-Reply-To: 3A59F666.E5376DE6@cisco.com


Mike Beede wrote:

> .....  If this isn't the place to
> send these, can someone let me know?

This will work.

> The second problem is that if you vmalloc memory requiring a new entry
> in the
> kernel pgd,

Crap, not again.....This was broken/fixed/broken/fixed during 2.3
and I thought it was finally correct.  It's really obvious on the
MPC8xx processors and I haven't seen it for a while.  I'll look
into it, as it used to be hidden away in macros or other generic
functions.  I thought the 6xx/7xx should have worked (unless we
have made some BAT mapping change recently.....)


Thanks.


	-- Dan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-01-08 17:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 17:18 Possible VM fix(s) for 2.4 PPC port Mike Beede
2001-01-08 17:35 ` Dan Malek [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=3A59FA56.688369B4@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mbeede@cisco.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 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.