All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoann Allain <yallain@avilinks.com>
To: Fuxin Zhang <fxzhang@ict.ac.cn>
Cc: Srinivas Kommu <kommu@hotmail.com>,
	Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: Preempted interrupt handler
Date: Thu, 22 Dec 2005 09:35:07 +0100	[thread overview]
Message-ID: <43AA653B.6050207@avilinks.com> (raw)
In-Reply-To: <43A9F76A.4080305@ict.ac.cn>


Fuxin Zhang a écrit :

>>Is it normal for the modules to be loaded at 0xc0000000 (this is
>>highmem, isn't it)? I see the same on my bcm1250 box. I've been wondering
>>why they can't be loaded in kseg0. Or is it because of bad
>>modutils/compiler flags?
>>    
>>
>It is not necessary highmem. 0xc0000000 is a MAPPED(i.e. use TLB) kernel
>segment,
>used by vmalloc to allocate a large virtually continous memory area for
>modules. Use kseg0 you have to get a large physically continuous area,
>and that is difficult unless you reserve some memory.
>  
>
I've just found in LDD 2nd version book (page 218), that on MIPS, 
addresses returned by vmalloc belong to a completely different address 
range from kmalloc addresses, whereas on x86 platforms they belong to 
the same.

Concerning the clues given by Ralf, I've tried insmoding the module by a 
recent version of modutils instead of using the insmod brought with 
Busybox : the kernel behaved the same, it doesn't want to use the 
handler of my kernel.
I've also checked that I was compiling with the mlong-calls flag...

Therefore, I think I will compile my module into the kernel, until I 
found a solution to this problem...

Thanks everyone!

      reply	other threads:[~2005-12-22  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 17:43 Preempted interrupt handler Yoann Allain
2005-12-20 13:18 ` Ralf Baechle
2005-12-21 19:39   ` Srinivas Kommu
2005-12-21 20:15     ` Steven J. Hill
2005-12-22  0:46     ` Fuxin Zhang
2005-12-22  8:35       ` Yoann Allain [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=43AA653B.6050207@avilinks.com \
    --to=yallain@avilinks.com \
    --cc=fxzhang@ict.ac.cn \
    --cc=kommu@hotmail.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.