In article <001001c5226f$321c8010$0e00a8c0@paq6>
locore64@alkyltechnology.com wrote:

> PV list is used to share a single page between multiple VA
> pages, right?  If so, all VA must agree each other for their
> "VA index".  In the case when such the VA disagree touching
> "conflicting VA range" makes virtual alias.  The solution is the
> same.  Do every effort to choose matching VA all the time.

Hmm, then current implementation may cause the problem.

> > we should just
> > invalidate cache for such KSEG0 VA before freeing
> > them by uvm_pagefree(9)?
> 
> VIPT cache needs no invalidation for that case.

...Unless the free'ed physical page is reused later and mapped
to KSEG2 VA which has a different index from its KSEG0 one?
i.e. the cache flush is required on -current pmap implementation
in that case?
---
Izumi Tsutsui
tsutsui@ceres.dti.ne.jp