From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: William Lee Irwin III <wli@holomorphy.com>,
linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Cc: jmerkey@timpanogas.org
Subject: Re: Question about Zone Allocation 2.4.X
Date: Thu, 2 Jan 2003 18:32:18 -0700 [thread overview]
Message-ID: <20030102183218.A21808@vger.timpanogas.org> (raw)
In-Reply-To: <20030103001127.GV9704@holomorphy.com>; from wli@holomorphy.com on Thu, Jan 02, 2003 at 04:11:27PM -0800
On Thu, Jan 02, 2003 at 04:11:27PM -0800, William Lee Irwin III wrote:
>
> Adding new zone types is easy. Just add them to mmzone.h, avoid setting
> ->virtual (which does not universally exist) in free_area_init_core()
> if it's not perma-mapped, stuff them in the fallback sequence in
> build_zonelists(), and detect them in arch/*/mm/init.c
>
Bill,
I also just reviewed the changes to the mmu code mode by Ingo -- very ugly
stuff. Looks like both changes are required to get this working properly
since without the PDE being setup properly, we'll get page faults since the
AS above 1GB is not mapped by the mmu.
Jeff
>
> Bill
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-01-03 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 0:55 Questton about Zone Allocation 2.4.X Jeff V. Merkey
2003-01-02 23:51 ` William Lee Irwin III
2003-01-02 23:54 ` William Lee Irwin III
2003-01-03 1:08 ` Jeff V. Merkey
2003-01-03 0:00 ` William Lee Irwin III
2003-01-03 1:15 ` Question " Jeff V. Merkey
2003-01-03 0:11 ` William Lee Irwin III
2003-01-03 1:32 ` Jeff V. Merkey [this message]
2003-01-03 0:30 ` William Lee Irwin III
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=20030102183218.A21808@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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