On Mon, 2009-10-19 at 10:58 +1100, Michael Ellerman wrote:
> > if (bus->self) {
> > +#ifdef CONFIG_PPC_STD_MMU_64
> > struct resource *res = bus->resource[0];
> > +#endif
> >
> > pr_debug("IO unmapping for PCI-PCI bridge %s\n",
> > pci_name(bus->s
On Sat, 2009-10-17 at 21:34 +0200, Wolfgang Denk wrote:
> Dear Joakim Tjernlund,
> > OK, but then you don't mix some libs/apps with soft and other
> > apps/libs with hard FP?
>
> No, we never tried that. Sounds scary to me.
And dangerous. Hard-float and soft-float are ABI incompatible, so you
ca
Hi,
> > +#define PPC_WARN_ALIGNMENT(type, regs) \
> > + do {\
> > + perf_sw_event(PERF_COUNT_SW_ALIGNMENT_FAULTS, \
> > + 1, 0, regs, regs->dar);
On Fri, 2009-10-16 at 12:05 -0500, Kumar Gala wrote:
> Fix the following 3 issues:
>
> arch/powerpc/kernel/process.c: In function 'arch_randomize_brk':
> arch/powerpc/kernel/process.c:1183: error: 'mmu_highuser_ssize' undeclared
> (first use in this function)
> arch/powerpc/kernel/process.c:1183:
On Sun, 2009-10-18 at 22:13 +1100, Anton Blanchard wrote:
> Hook up the alignment-faults and emulation-faults events for powerpc.
>
> Signed-off-by: Anton Blanchard
> ---
>
> Index: linux.trees.git/arch/powerpc/include/asm/emulated_ops.h
>
Dear Joakim Tjernlund,
In message
you
wrote:
>
> > If the application is really using FP instructions a lot, then there
> > is a huge difference between using soft-float and MATH_EMU; I
> > remember test cases where soft-float was faster by factors of
> > 500...1000.
>
> Ouch, I had no idea th
Hi Anton,
On Sun, 18 Oct 2009 22:11:26 +1100 Anton Blanchard wrote:
>
> @@ -66,8 +66,12 @@ extern void ppc_warn_emulated_print(cons
>
> #else /* !CONFIG_PPC_EMULATED_STATS */
>
> -#define PPC_WARN_EMULATED(type) do { } while (0)
> +#define __PPC_WARN_EMULATED(type)do { } while (0)
>
Wolfgang Denk wrote on 17/10/2009 21:34:54:
>
> Dear Joakim Tjernlund,
>
> In message 00651...@transmode.se> you wrote:
> >
> > > Recompile and relink it with soft-fp as well. Or ask the provider to
> > > do that.
> >
> > That is what I am trying do/find out. The supplier claims that
> > it shoul
Add some dummy symbols for the branches at 0xf00, 0xf20 and 0xf40,
otherwise hits end up in trap_0e which is confusing to the user.
Signed-off-by: Anton Blanchard
---
Index: linux.trees.git/arch/powerpc/kernel/exceptions-64s.S
===
A lot of hits in "setup" doesn't make much sense, so hide this symbol and
allow all the hits to end up in copy_4k_page.
Signed-off-by: Anton Blanchard
---
Index: linux.trees.git/arch/powerpc/lib/copypage_64.S
===
--- linux.trees.gi
If CONFIG_PPC_ISERIES isn't defined we end up with iseries_check_pending_irqs
and do_work at the same address. perf ends up picking
iseries_check_pending_irqs which creates confusing backtraces. Hide it.
Signed-off-by: Anton Blanchard
--
Index: linux.trees.git/arch/powerpc/kernel/entry_64.S
===
Add two more sw events that are common to many cpus.
Alignment faults: When a load or store is not aligned properly.
Emulation faults: When an instruction is emulated in software.
Both cause a very significant slowdown (100x or worse), so identifying and
fixing them is very important.
Signed-o
perf_event wants a separate event for alignment and emulation faults,
so create another PPC_WARN_* define. This will make it easy to hook in
perf_event at one spot.
We pass in regs which will be required for these events.
Signed-off-by: Anton Blanchard
---
Index: linux.trees.git/arch/powerpc/i
Hook up the alignment-faults and emulation-faults events for powerpc.
Signed-off-by: Anton Blanchard
---
Index: linux.trees.git/arch/powerpc/include/asm/emulated_ops.h
===
--- linux.trees.git.orig/arch/powerpc/include/asm/emulated_
Hi Ben,
> Breaks 6xx_defconfig:
Yuck. Since the CREATE_TRACE_POINTS stuff appears to need a non trivial number
of includes it might be best just to fold it into one of the tracepoint call
sites like this.
--
This patch adds powerpc specific tracepoints for interrupt entry and exit.
While we a
Hi, Scott
Scott Wood wrote:
On Fri, Oct 16, 2009 at 07:01:43AM +0200, Felix Radensky wrote:
Thanks for confirmation. So the real problem is eLBC ?
What happens if I access other devices on eLBC (e.g. FPGA)
simultaneously with NAND or NOR ?
AFAICT, the problem is NAND being accessed simultaneo
16 matches
Mail list logo