Bug#561203: threads and fork on machine with VIPT-WB cache

2010-04-02 Thread NIIBE Yutaka
NIIBE Yutaka wrote: To have same semantics as other archs, I think that VIPT-WB cache machine should have cache flush at ptep_set_wrprotect, so that memory of the page has up-to-date data. Yes, it will be huge performance impact for fork. But I don't find any good solution other than this yet.

Bug#576030: gcc-4.3: wcstoll returns only the value for 32bit.

2010-04-02 Thread Aurelien Jarno
On Wed, Mar 31, 2010 at 11:32:50PM +0900, Hikaru MIYAGI wrote: Package: gcc-4.3 Version: 4.3.2-1.1 Severity: important wcstoll returns only the value for 32bit. For instance, wcstoll(L1, NULL, 16) returns 0 though it is sure to become 4294967296. This is not reproducible here.

Bug#561203: threads and fork on machine with VIPT-WB cache

2010-04-02 Thread James Bottomley
On Fri, 2010-04-02 at 12:48 +0900, NIIBE Yutaka wrote: Thanks for your quick reply. James Bottomley wrote: In COW breaking, the page table entry is copied, so A and B no longer have page table entries at the same physical location. If the COW is intact, A and B have the same physical

Bug#561203: threads and fork on machine with VIPT-WB cache

2010-04-02 Thread John David Anglin
On Fri, 02 Apr 2010, NIIBE Yutaka wrote: NIIBE Yutaka wrote: To have same semantics as other archs, I think that VIPT-WB cache machine should have cache flush at ptep_set_wrprotect, so that memory of the page has up-to-date data. Yes, it will be huge performance impact for fork. But I