| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
We need to continue with next microblaze PVR version that's why
I have to remove that ancient version. These version strings not match
any versions. From Microblaze v5.00.a is possible to use this style.
I believe that none use ancients versions. If yes they will be just
labeled as unknown version.
Signed-off-by: Michal Simek <[email protected]>
|
|
WB cache has special flag in PVR. There is added checking mechanism
for PVR and DTS.
Signed-off-by: Michal Simek <[email protected]>
|
|
There is missing checking agains PVR but this is not important
for now. There are some missing checking too.
Signed-off-by: Michal Simek <[email protected]>
|
|
We used cache_line as cache_line_lenght. For this reason
we did cache flushing 4 times longer than was necessary.
Signed-off-by: Michal Simek <[email protected]>
|
|
Signed-off-by: Michal Simek <[email protected]>
|
|
If -pg of gcc is enabled with CONFIG_FUNCTION_TRACER=y. a calling to
_mcount will be inserted into each kernel function. so, there is a
possibility to trace the kernel functions in _mcount.
This patch add the specific _mcount support for static function
tracing. by default, ftrace_trace_function is initialized as
ftrace_stub(an empty function), so, the default _mcount will introduce
very little overhead. after enabling ftrace in user-space, it will jump
to a real tracing function and do static function tracing for us.
Commit message from Wu Zhangjin <[email protected]>
Signed-off-by: Michal Simek <[email protected]>
|
|
There are just two major changes
Renamed local_irq functions to raw_local_irq in irq.c.
Added TRACE_IRQFLAGS_SUPPORT to Kconfig.debug.
Look at Documentation/irqflags-tracing.txt
Signed-off-by: Michal Simek <[email protected]>
|
|
Signed-off-by: John Williams <[email protected]>
Signed-off-by: Michal Simek <[email protected]>
|
|
Signed-off-by: Michal Simek <[email protected]>
|
|
Signed-off-by: Michal Simek <[email protected]>
|
|
The C99 specification states in section 6.11.5:
The placement of a storage-class specifier other than at the
beginning of the declaration specifiers in a declaration is an
obsolescent feature.
Signed-off-by: Tobias Klauser <[email protected]>
Signed-off-by: Michal Simek <[email protected]>
|
|
It is not necessary to check cpuinfo.use_dcache because
this checking is done in function which call that functions
Signed-off-by: Michal Simek <[email protected]>
|
|
Signed-off-by: Michal Simek <[email protected]>
|
|
Signed-off-by: Michal Simek <[email protected]>
|
|
Reviewed-by: Ingo Molnar <[email protected]>
Acked-by: Randy Dunlap <[email protected]>
Acked-by: John Linn <[email protected]>
Acked-by: Stephen Neuendorffer <[email protected]>
Acked-by: John Williams <[email protected]>
Signed-off-by: Michal Simek <[email protected]>
|
|
Reviewed-by: Ingo Molnar <[email protected]>
Acked-by: Stephen Neuendorffer <[email protected]>
Acked-by: John Linn <[email protected]>
Acked-by: John Williams <[email protected]>
Signed-off-by: Michal Simek <[email protected]>
|
|
Reviewed-by: Ingo Molnar <[email protected]>
Acked-by: Stephen Neuendorffer <[email protected]>
Acked-by: John Linn <[email protected]>
Acked-by: John Williams <[email protected]>
Signed-off-by: Michal Simek <[email protected]>
|
|
Reviewed-by: Ingo Molnar <[email protected]>
Acked-by: Stephen Neuendorffer <[email protected]>
Acked-by: John Linn <[email protected]>
Acked-by: John Williams <[email protected]>
Signed-off-by: Michal Simek <[email protected]>
|