All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: early ioremap not working with 2.4.19-pre1-aa1 ?
Date: Sat, 2 Mar 2002 03:44:48 +0100	[thread overview]
Message-ID: <20020302034448.M4431@inspiron.random> (raw)
In-Reply-To: <174730000.1015026374@flay>
In-Reply-To: <174730000.1015026374@flay>

On Fri, Mar 01, 2002 at 03:46:14PM -0800, Martin J. Bligh wrote:
> I have code for the NUMA-Q systems that does an ioremap
> as the first thing in smp_boot_cpus (ia32 tree). This seems to 
> work fine until I install the aa patches ... then it hangs in the 
> ioremap.

this sounds like the same problem of the MXT patch. In short pte_alloc
and in turn ioremap was usable only after the initcalls.

Does this incremental patch fix it?  (untested)

--- 2.4.19pre1aa1/include/linux/highmem.h.~1~	Fri Mar  1 20:19:05 2002
+++ 2.4.19pre1aa1/include/linux/highmem.h	Sat Mar  2 03:43:42 2002
@@ -12,6 +12,7 @@
 
 /* declarations for linux/mm/highmem.c */
 unsigned int nr_free_highpages(void);
+extern void init_kmap(void);
 
 extern struct buffer_head *create_bounce(int rw, struct buffer_head * bh_orig);
 
@@ -64,6 +65,7 @@
 #else /* CONFIG_HIGHMEM */
 
 static inline unsigned int nr_free_highpages(void) { return 0; }
+#define init_kmap() do { } while(0)
 
 static inline void *kmap(struct page *page) { return page_address(page); }
 
--- 2.4.19pre1aa1/init/main.c.~1~	Wed Feb 27 12:46:19 2002
+++ 2.4.19pre1aa1/init/main.c	Sat Mar  2 03:42:52 2002
@@ -599,6 +599,7 @@
 	mem_init();
 	kmem_cache_sizes_init();
 	pgtable_cache_init();
+	init_kmap();
 
 #ifdef CONFIG_PERFMON
 	perfmon_init();
--- 2.4.19pre1aa1/mm/highmem.c.~1~	Wed Feb 27 12:46:13 2002
+++ 2.4.19pre1aa1/mm/highmem.c	Sat Mar  2 03:43:50 2002
@@ -45,7 +45,7 @@
 
 static wait_queue_head_t pkmap_map_wait[KM_NR_SERIES];
 
-static __init int init_kmap(void)
+void __init init_kmap(void)
 {
 	int i;
 
@@ -56,7 +56,6 @@
 #endif
 	return 0;
 }
-__initcall(init_kmap);
 
 static void flush_all_zero_pkmaps(void)
 {
> 
> Has anyone got any idea why this might be? I'd really like to
> test out the -aa vm patches on this box ... I can debug it some
> more - just looking for an easy answer ;-)
> 
> Thanks,
> 
> Martin.


Andrea

  reply	other threads:[~2002-03-02  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 23:46 early ioremap not working with 2.4.19-pre1-aa1 ? Martin J. Bligh
2002-03-02  2:44 ` Andrea Arcangeli [this message]
2002-03-07  1:57   ` Martin J. Bligh
  -- strict thread matches above, loose matches on Subject: below --
2002-03-02 13:12 Mikael Pettersson

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=20020302034448.M4431@inspiron.random \
    --to=andrea@suse.de \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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.