All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: akpm@osdl.org, apw@shadowen.org, geert@linux-m68k.org, torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: is_highmem() and WANT_PAGE_VIRTUAL (was: Re: Linux 2.6.8-rc1)
Date: Mon, 12 Jul 2004 14:51:47 +0100	[thread overview]
Message-ID: <200407121351.i6CDplLM031827@voidhawk.shadowen.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0407121326410.17199@waterleaf.sonytel.be>

--- Geert wrote:
> | --- reference/mm/page_alloc.c	2004-07-07 18:08:56.000000000 +0100
> | +++ current/mm/page_alloc.c	2004-07-07 18:10:15.000000000 +0100
> | @@ -1421,7 +1421,7 @@ void __init memmap_init_zone(struct page
> |  		INIT_LIST_HEAD(&page->lru);
> |  #ifdef WANT_PAGE_VIRTUAL
> |  		/* The shift won't overflow because ZONE_NORMAL is below 4G. */
> | -		if (zone != ZONE_HIGHMEM)
> | +		if (!is_highmem(zone))
> |  			set_page_address(page, __va(start_pfn << PAGE_SHIFT));
> |  #endif
> |  		start_pfn++;
> 
> The above change is incorrect, since zone is an unsigned long, while
> is_highmem() takes a struct zone *.

My bad.  I was stupidly assuming that this was used then ZONE_HIGHMEM was
not enabled.  This should apply on top of 2.6.8-rc1 and repair the damage.

-apw

=== 8< ===
Should be applying is_highmem() to a zone.

Revision: $Rev: 386 $

Signed-off-by: Andy Whitcroft <apw@shadowen.org>

---

diff -X /home/apw/brief/lib/vdiff.excl -rupN reference/mm/page_alloc.c current/mm/page_alloc.c
--- reference/mm/page_alloc.c	2004-07-12 13:15:57.000000000 +0100
+++ current/mm/page_alloc.c	2004-07-12 14:37:19.000000000 +0100
@@ -1402,7 +1402,7 @@ void __init memmap_init_zone(struct page
 		INIT_LIST_HEAD(&page->lru);
 #ifdef WANT_PAGE_VIRTUAL
 		/* The shift won't overflow because ZONE_NORMAL is below 4G. */
-		if (!is_highmem(zone))
+		if (!is_highmem(page_zone(page)))
 			set_page_address(page, __va(start_pfn << PAGE_SHIFT));
 #endif
 		start_pfn++;

  reply	other threads:[~2004-07-12 13:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-11 18:29 Linux 2.6.8-rc1 Linus Torvalds
2004-07-11 23:00 ` [PATCH] edd (Re: Linux 2.6.8-rc1) Randy.Dunlap
2004-07-12  3:02   ` Adrian Bunk
2004-07-12  4:49   ` Matt Domsch
2004-07-12  5:21     ` Randy.Dunlap
2004-07-12  9:26 ` Linux 2.6.8-rc1 Matthias Andree
2004-07-12 18:54   ` Martin Schlemmer
2004-07-12  9:34 ` Paolo Ciarrocchi
2004-07-12 15:42   ` Adrian Bunk
2004-07-12 15:56     ` Paolo Ciarrocchi
2004-07-12 16:34       ` Adrian Bunk
2004-07-12 16:43         ` Linus Torvalds
2004-07-12 20:28           ` Paolo Ciarrocchi
2004-07-12 20:22         ` Paolo Ciarrocchi
2004-07-13 20:54       ` cliff white
2004-07-12 21:08     ` Horst von Brand
2004-07-12 11:30 ` is_highmem() and WANT_PAGE_VIRTUAL (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 13:51   ` Andy Whitcroft [this message]
2004-07-12 14:23     ` Geert Uytterhoeven
2004-07-12 12:01 ` Linux 2.6.8-rc1 Geert Uytterhoeven
2004-07-12 13:18   ` OGAWA Hirofumi
2004-07-12 13:25     ` Geert Uytterhoeven
2004-07-12 14:02       ` OGAWA Hirofumi
2004-07-12 13:23 ` struct_cpy() and kAFS (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 18:11   ` Andrew Morton
2004-07-12 18:23     ` Christoph Hellwig
2004-07-12 18:40       ` Andrew Morton
2004-07-13 10:14     ` David Howells
2004-07-12 23:49 ` Linux 2.6.8-rc1 (compile stats) John Cherry

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=200407121351.i6CDplLM031827@voidhawk.shadowen.org \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.