Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Gill" <gill.robles@exterity.co.uk>, <linux-mips@linux-mips.org>
Subject: Re: Page fault question
Date: Wed, 24 Sep 2003 12:05:31 +0200	[thread overview]
Message-ID: <00d301c38283$67145be0$10eca8c0@grendel> (raw)
In-Reply-To: 000901c3826e$9703adc0$4300a8c2@gillpc

[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]

The EMMA2 (uPD61130) uses the NEC Vr4130 core, wheras the EMMA2L (uPD61120)
uses a MIPS 4Kc core.  The 4Kc is a MIPS32-compliant core, but the Vr41xx family
predates the MIPS32 spec for the MMU interface, and has some significant incompatibilities,
mostly due to the fact that the Vr4100's assume a 1K page granularity, versus 4K for the 4Kc
and almost all other MIPS processors.  You can't use the same MMU code for both chips.
One kernel needs to be configured for a "MIPS32" CPU, the other for "R41xx".
  ----- Original Message ----- 
  From: Gill 
  To: linux-mips@linux-mips.org 
  Sent: Wednesday, September 24, 2003 9:36 AM
  Subject: Page fault question


  Hello -



  I'm currently porting vmlinux from NEC's EMMA2L platform to EMMA2.  The problem I'm having is that linux hangs when it attempts to do its first page fault: the page fault handler is successfully called, the call to handle_mm_fault returns 2 (major fault).but then code execution appears to just stop.  Linux is not completely dead, however - it still responds to a timer interrupt.



  As the code for handling page faults is standard code, and TLB hardware should be the same on EMMA2 as on EMMA2L (where it works!), I don't understand what's gone wrong!  Does anyone have any ideas?



  Thanks for your help,





  Gill

[-- Attachment #2: Type: text/html, Size: 4467 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Gill <gill.robles@exterity.co.uk>, linux-mips@linux-mips.org
Subject: Re: Page fault question
Date: Wed, 24 Sep 2003 12:05:31 +0200	[thread overview]
Message-ID: <00d301c38283$67145be0$10eca8c0@grendel> (raw)
Message-ID: <20030924100531.ztARUVmn1_ffHDNsmE8gooMhxpXMKT6jWFUwZDxulXE@z> (raw)
In-Reply-To: 000901c3826e$9703adc0$4300a8c2@gillpc

[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]

The EMMA2 (uPD61130) uses the NEC Vr4130 core, wheras the EMMA2L (uPD61120)
uses a MIPS 4Kc core.  The 4Kc is a MIPS32-compliant core, but the Vr41xx family
predates the MIPS32 spec for the MMU interface, and has some significant incompatibilities,
mostly due to the fact that the Vr4100's assume a 1K page granularity, versus 4K for the 4Kc
and almost all other MIPS processors.  You can't use the same MMU code for both chips.
One kernel needs to be configured for a "MIPS32" CPU, the other for "R41xx".
  ----- Original Message ----- 
  From: Gill 
  To: linux-mips@linux-mips.org 
  Sent: Wednesday, September 24, 2003 9:36 AM
  Subject: Page fault question


  Hello -



  I'm currently porting vmlinux from NEC's EMMA2L platform to EMMA2.  The problem I'm having is that linux hangs when it attempts to do its first page fault: the page fault handler is successfully called, the call to handle_mm_fault returns 2 (major fault).but then code execution appears to just stop.  Linux is not completely dead, however - it still responds to a timer interrupt.



  As the code for handling page faults is standard code, and TLB hardware should be the same on EMMA2 as on EMMA2L (where it works!), I don't understand what's gone wrong!  Does anyone have any ideas?



  Thanks for your help,





  Gill

[-- Attachment #2: Type: text/html, Size: 4467 bytes --]

  parent reply	other threads:[~2003-09-24 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24  7:36 Page fault question Gill
2003-09-24  7:36 ` Gill
2003-09-24 10:05 ` Kevin D. Kissell [this message]
2003-09-24 10:05   ` Kevin D. Kissell

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='00d301c38283$67145be0$10eca8c0@grendel' \
    --to=kevink@mips.com \
    --cc=gill.robles@exterity.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox