RE: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
- From: "kus Kusche Klaus" <kus@xxxxxxxx>
- Date: Tue, 3 Jan 2006 16:40:28 +0100
> From: Daniel Walker
> Most likely . It's hard to create a global solution in the entry-*.S
> files cause the code in there is called so early.
One more problem:
There seem to be more irq enable/disable than in entry-header.S:
entry-armv.S contains an open-coded enable,
asm-arm/assembler.h defines irq save/restore macros, ...
And they all do not trace.
--
Klaus Kusche (Software Development - Control Systems)
KEBA AG Gewerbepark Urfahr, A-4041 Linz, Austria (Europe)
Tel: +43 / 732 / 7090-3120 Fax: +43 / 732 / 7090-6301
E-Mail: kus@xxxxxxxx WWW: www.keba.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Prev by Date: Re: [patch 08/19] mutex subsystem, core
- Next by Date: Re: [patch 08/19] mutex subsystem, core
- Previous by thread: RE: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
- Next by thread: RE: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
- Index(es):
Relevant Pages
|
