On Tue, Jan 08, 2008 at 01:54:15PM +0000, Catalin Marinas wrote: > On Tue, 2008-01-08 at 10:52 +0000, Russell King wrote: > > It's unclear at present what circumstances you'd use each of the two > > Xscale3 work-around bit combinations - or indeed whether there's a > > printing error in the documentation concerning TEXCB=00101. > > As I said, I don't know the details of this bug and can't comment. As I said I don't think there's anything further that can be usefully added to this discussion until we're further down the road with this. Even though you don't know the details of the bug report, I've mentioned as much as I know about it at present - and that includes with access to Marvells spec update document. When I'm further down the line with PXA3 work maybe I'll know more, but my priority at the moment on PXA3 is suspend/resume support. > I haven't run any benchmarks and I can't say how big the impact is but, > based on some past discussions, 3-4 more cycles in set_pte might go > unnoticed because of other, bigger overheads. Except when you're clearing out page tables - for instance when a thread exits. It's very noticable and shows up rather well in fork+exit tests - even shell scripts. This was certainly the case with 2.2 kernels. Whether 2.6 kernels are soo heavy weight that it's been swapped into non-existence I don't know. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
