Hello. Sergei Shtylyov wrote:
Why is cycles_t 32-bits on some of the arches to begin with?
I guess this was done for speed reasons.
The whole 64-bit timebase can't be rad atomically on PPC32. ARM probably has stricter limitations...
Ingo
WBR, Sergei - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c (take 3)
- From: Sergei Shtylyov <[email protected]>
- Re: [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c (take 3)
- From: Sergei Shtylyov <[email protected]>
- Re: [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c (take 3)
- From: Ingo Molnar <[email protected]>
- Re: [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c (take 3)
- From: Sergei Shtylyov <[email protected]>
- [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c (take 3)
- Prev by Date: RE: la la la la ... swappiness
- Next by Date: [PATCH] Remove 'volatile' from spinlocks
- Previous by thread: Re: [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c (take 3)
- Next by thread: [PATCH] atkbd: disable spurious ACK/NAK warning on panic
- Index(es):
 |