Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: [ARM32] Possible PMAP_KMPAGE = 0 produces lock collision

To: Andy Shevchenko <andy.shevchenko%gmail.com@localhost>
Subject: Re: [ARM32] Possible PMAP_KMPAGE = 0 produces lock collision
From: Matt Thomas <matt%3am-software.com@localhost>
Date: Mon, 21 Jul 2008 00:34:20 -0700


On Jul 21, 2008, at 12:11 AM, Andy Shevchenko wrote:

On Fri, Jul 18, 2008 at 7:51 PM, Matt Thomas <matt@3am-software.com> wrote:
you have the updated arm/include/arm32/pmap.h which definesPMAP_KMPAGE?
If it's not defined, the kernel will definitely panic.
I have unmodified pmap.h from NetBSD current. That file not includes
this constant at all.
Therefore it's obvious bug in the pmap.h.


Opps.  forgot to commit that file.  Sorry.  it's now fixed.

Follow-Ups:
- Re: [ARM32] Possible PMAP_KMPAGE = 0 produces lock collision
  - From: Andy Shevchenko

References:
- [ARM32] Possible PMAP_KMPAGE = 0 produces lock collision
  - From: Andy Shevchenko
- Re: [ARM32] Possible PMAP_KMPAGE = 0 produces lock collision
  - From: Matt Thomas
- Re: [ARM32] Possible PMAP_KMPAGE = 0 produces lock collision
  - From: Andy Shevchenko

Prev by Date: Re: [ARM32] Possible PMAP_KMPAGE = 0 produces lock collision
Next by Date: Re: rfc: OMAP2: micro benchmarks
Previous by Thread: Re: [ARM32] Possible PMAP_KMPAGE = 0 produces lock collision
Next by Thread: Re: [ARM32] Possible PMAP_KMPAGE = 0 produces lock collision
Indexes:

Home | Main Index | Thread Index | Old Index