Re: threads and fork on machine with VIPT-WB cache

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

 



On Mon, 10 May 2010, John David Anglin wrote:

> I'll do a little more testing tonight.  In testing, I have had a
> couple of boot failures on gsyprf11 starting iptables.  Haven't
> seen any hpmc's starting sshd.

It appears James' kmap change is needed on PA8800 (rp3440) for cache
coherency.  I see segmentation faults in sh with just the flush in
ptep_set_wrprotect.  I haven't had a chance to test whether the flush
in ptep_set_wrprotect is needed to fix minifail on this machine.
However, a GCC build completed successfully with the kmap change and
without the ptep_set_wrprotect flush.

On gsyprf11 (PA8700), James' kmap change doesn't fix minifail and we need
the cache flush in ptep_set_wrprotect to fix minifail.  The kmap change
causes general instability by itself.

Thus, it appears necessary to merge the two approaches and treat PA8700
and PA8800 differently.

I think we are really killing performance with the cache flushing...

Dave
-- 
J. David Anglin                                  dave.anglin@xxxxxxxxxxxxxx
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux SoC]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux