NetBSD-Bugs archive

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

Re: port-i386/38289 (a possible problem in x86 pmap_update)

To: port-i386-maintainer%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,ad%NetBSD.org@localhost,yamt%mwd.biglobe.ne.jp@localhost
Subject: Re: port-i386/38289 (a possible problem in x86 pmap_update)
From: ad%NetBSD.org@localhost
Date: Sat, 29 Mar 2008 14:17:43 +0000 (UTC)

Synopsis: a possible problem in x86 pmap_update

State-Changed-From-To: open->feedback
State-Changed-By: ad%NetBSD.org@localhost
State-Changed-When: Sat, 29 Mar 2008 14:17:43 +0000
State-Changed-Why:
pmap_deactivate() does the equivalent of pmap_update(). It's kind of ugly,
but it's an existing 'hook' in from the context switch code. Do you see
another problem?

Follow-Ups:
- Re: port-i386/38289 (a possible problem in x86 pmap_update)
  - From: YAMAMOTO Takashi

Prev by Date: Re: kern/38324 (callout KASSERT firing)
Next by Date: Re: bin/38327: uu{en,de}code - any reason to use non-portable [sg]etprogname?
Previous by Thread: Re: kern/38324 (callout KASSERT firing)
Next by Thread: Re: port-i386/38289 (a possible problem in x86 pmap_update)
Indexes:

Home | Main Index | Thread Index | Old Index