2005-09-26 14:04:21 +08:00
|
|
|
#
|
|
|
|
# Makefile for the linux kernel.
|
|
|
|
#
|
|
|
|
|
2007-12-20 19:58:00 +08:00
|
|
|
CFLAGS_ptrace.o += -DUTS_MACHINE='"$(UTS_MACHINE)"'
|
|
|
|
|
2009-06-10 04:48:51 +08:00
|
|
|
subdir-ccflags-$(CONFIG_PPC_WERROR) := -Werror
|
|
|
|
|
2005-09-30 11:51:25 +08:00
|
|
|
ifeq ($(CONFIG_PPC64),y)
|
2007-11-07 13:13:29 +08:00
|
|
|
CFLAGS_prom_init.o += -mno-minimal-toc
|
2005-09-30 11:51:25 +08:00
|
|
|
endif
|
2005-09-30 14:16:52 +08:00
|
|
|
ifeq ($(CONFIG_PPC32),y)
|
2005-10-06 10:06:20 +08:00
|
|
|
CFLAGS_prom_init.o += -fPIC
|
2005-10-06 11:24:50 +08:00
|
|
|
CFLAGS_btext.o += -fPIC
|
2005-09-30 14:16:52 +08:00
|
|
|
endif
|
2005-10-06 10:06:20 +08:00
|
|
|
|
2008-10-07 07:06:12 +08:00
|
|
|
ifdef CONFIG_FUNCTION_TRACER
|
2008-05-15 11:49:44 +08:00
|
|
|
# Do not trace early boot code
|
2008-09-02 14:50:38 +08:00
|
|
|
CFLAGS_REMOVE_cputable.o = -pg -mno-sched-epilog
|
|
|
|
CFLAGS_REMOVE_prom_init.o = -pg -mno-sched-epilog
|
|
|
|
CFLAGS_REMOVE_btext.o = -pg -mno-sched-epilog
|
2008-11-27 04:54:46 +08:00
|
|
|
CFLAGS_REMOVE_prom.o = -pg -mno-sched-epilog
|
2009-02-10 13:10:27 +08:00
|
|
|
# do not trace tracer code
|
2008-09-02 14:50:38 +08:00
|
|
|
CFLAGS_REMOVE_ftrace.o = -pg -mno-sched-epilog
|
2009-02-10 13:10:27 +08:00
|
|
|
# timers used by tracing
|
|
|
|
CFLAGS_REMOVE_time.o = -pg -mno-sched-epilog
|
2008-05-15 11:49:44 +08:00
|
|
|
endif
|
|
|
|
|
2008-03-08 10:55:58 +08:00
|
|
|
obj-y := cputable.o ptrace.o syscalls.o \
|
2006-01-12 18:22:34 +08:00
|
|
|
irq.o align.o signal_32.o pmc.o vdso.o \
|
2007-06-04 13:15:49 +08:00
|
|
|
init_task.o process.o systbl.o idle.o \
|
2008-12-24 02:55:54 +08:00
|
|
|
signal.o sysfs.o cacheinfo.o
|
2005-11-11 18:15:21 +08:00
|
|
|
obj-y += vdso32/
|
2008-01-03 09:03:11 +08:00
|
|
|
obj-$(CONFIG_PPC64) += setup_64.o sys_ppc32.o \
|
2006-02-10 13:02:20 +08:00
|
|
|
signal_64.o ptrace32.o \
|
2009-07-24 07:15:59 +08:00
|
|
|
paca.o nvram_64.o firmware.o
|
|
|
|
obj-$(CONFIG_PPC_BOOK3S_64) += cpu_setup_ppc970.o cpu_setup_pa6t.o
|
powerpc: Make the 64-bit kernel as a position-independent executable
This implements CONFIG_RELOCATABLE for 64-bit by making the kernel as
a position-independent executable (PIE) when it is set. This involves
processing the dynamic relocations in the image in the early stages of
booting, even if the kernel is being run at the address it is linked at,
since the linker does not necessarily fill in words in the image for
which there are dynamic relocations. (In fact the linker does fill in
such words for 64-bit executables, though not for 32-bit executables,
so in principle we could avoid calling relocate() entirely when we're
running a 64-bit kernel at the linked address.)
The dynamic relocations are processed by a new function relocate(addr),
where the addr parameter is the virtual address where the image will be
run. In fact we call it twice; once before calling prom_init, and again
when starting the main kernel. This means that reloc_offset() returns
0 in prom_init (since it has been relocated to the address it is running
at), which necessitated a few adjustments.
This also changes __va and __pa to use an equivalent definition that is
simpler. With the relocatable kernel, PAGE_OFFSET and MEMORY_START are
constants (for 64-bit) whereas PHYSICAL_START is a variable (and
KERNELBASE ideally should be too, but isn't yet).
With this, relocatable kernels still copy themselves down to physical
address 0 and run there.
Signed-off-by: Paul Mackerras <paulus@samba.org>
2008-08-30 09:43:47 +08:00
|
|
|
obj64-$(CONFIG_RELOCATABLE) += reloc_64.o
|
2009-07-24 07:15:59 +08:00
|
|
|
obj-$(CONFIG_PPC_BOOK3E_64) += exceptions-64e.o
|
2005-11-11 18:15:21 +08:00
|
|
|
obj-$(CONFIG_PPC64) += vdso64/
|
2009-06-03 05:17:37 +08:00
|
|
|
obj-$(CONFIG_ALTIVEC) += vecemu.o
|
2006-04-18 19:49:11 +08:00
|
|
|
obj-$(CONFIG_PPC_970_NAP) += idle_power4.o
|
2006-11-11 14:24:59 +08:00
|
|
|
obj-$(CONFIG_PPC_OF) += of_device.o of_platform.o prom_parse.o
|
2007-09-20 22:00:11 +08:00
|
|
|
obj-$(CONFIG_PPC_CLOCK) += clock.o
|
2009-09-25 03:29:13 +08:00
|
|
|
procfs-y := proc_powerpc.o
|
2005-11-10 12:26:20 +08:00
|
|
|
obj-$(CONFIG_PROC_FS) += $(procfs-y)
|
2007-03-04 14:04:44 +08:00
|
|
|
rtaspci-$(CONFIG_PPC64)-$(CONFIG_PCI) := rtas_pci.o
|
|
|
|
obj-$(CONFIG_PPC_RTAS) += rtas.o rtas-rtc.o $(rtaspci-y-y)
|
2009-09-25 03:30:05 +08:00
|
|
|
obj-$(CONFIG_PPC_RTAS_DAEMON) += rtasd.o
|
2005-11-03 11:41:19 +08:00
|
|
|
obj-$(CONFIG_RTAS_FLASH) += rtas_flash.o
|
|
|
|
obj-$(CONFIG_RTAS_PROC) += rtas-proc.o
|
2005-11-10 12:26:20 +08:00
|
|
|
obj-$(CONFIG_LPARCFG) += lparcfg.o
|
2005-10-24 12:22:37 +08:00
|
|
|
obj-$(CONFIG_IBMVIO) += vio.o
|
2005-11-16 15:56:43 +08:00
|
|
|
obj-$(CONFIG_IBMEBUS) += ibmebus.o
|
2005-11-04 10:28:58 +08:00
|
|
|
obj-$(CONFIG_GENERIC_TBSYNC) += smp-tbsync.o
|
2005-12-04 15:39:37 +08:00
|
|
|
obj-$(CONFIG_CRASH_DUMP) += crash_dump.o
|
2008-06-19 05:26:52 +08:00
|
|
|
obj-$(CONFIG_E500) += idle_e500.o
|
2006-03-27 16:15:26 +08:00
|
|
|
obj-$(CONFIG_6xx) += idle_6xx.o l2cr_6xx.o cpu_setup_6xx.o
|
|
|
|
obj-$(CONFIG_TAU) += tau_6xx.o
|
2007-09-21 08:16:20 +08:00
|
|
|
obj-$(CONFIG_HIBERNATION) += swsusp.o suspend.o \
|
|
|
|
swsusp_$(CONFIG_WORD_SIZE).o
|
|
|
|
obj64-$(CONFIG_HIBERNATION) += swsusp_asm64.o
|
2008-06-21 00:31:01 +08:00
|
|
|
obj-$(CONFIG_MODULES) += module.o module_$(CONFIG_WORD_SIZE).o
|
2007-10-04 09:02:09 +08:00
|
|
|
obj-$(CONFIG_44x) += cpu_setup_44x.o
|
2009-02-12 21:54:53 +08:00
|
|
|
obj-$(CONFIG_FSL_BOOKE) += cpu_setup_fsl_booke.o dbell.o
|
2005-10-10 20:50:37 +08:00
|
|
|
|
2009-07-24 07:15:59 +08:00
|
|
|
extra-y := head_$(CONFIG_WORD_SIZE).o
|
|
|
|
extra-$(CONFIG_PPC_BOOK3E_32) := head_new_booke.o
|
2007-08-20 20:27:07 +08:00
|
|
|
extra-$(CONFIG_40x) := head_40x.o
|
2005-09-26 14:04:21 +08:00
|
|
|
extra-$(CONFIG_44x) := head_44x.o
|
|
|
|
extra-$(CONFIG_FSL_BOOKE) := head_fsl_booke.o
|
|
|
|
extra-$(CONFIG_8xx) := head_8xx.o
|
|
|
|
extra-y += vmlinux.lds
|
|
|
|
|
2006-06-28 09:55:49 +08:00
|
|
|
obj-y += time.o prom.o traps.o setup-common.o \
|
powerpc: Merge 32 and 64-bit dma code
We essentially adopt the 64-bit dma code, with some changes to support
32-bit systems, including HIGHMEM. dma functions on 32-bit are now
invoked via accessor functions which call the correct op for a device based
on archdata dma_ops. If there is no archdata dma_ops, this defaults
to dma_direct_ops.
In addition, the dma_map/unmap_page functions are added to dma_ops
because we can't just fall back on map/unmap_single when HIGHMEM is
enabled. In the case of dma_direct_*, we stop using map/unmap_single
and just use the page version - this saves a lot of ugly
ifdeffing. We leave map/unmap_single in the dma_ops definition,
though, because they are needed by the iommu code, which does not
implement map/unmap_page. Ideally, going forward, we will completely
eliminate map/unmap_single and just have map/unmap_page, if it's
workable for 64-bit.
Signed-off-by: Becky Bruce <becky.bruce@freescale.com>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
2008-09-12 18:34:46 +08:00
|
|
|
udbg.o misc.o io.o dma.o \
|
2007-09-21 08:16:20 +08:00
|
|
|
misc_$(CONFIG_WORD_SIZE).o
|
|
|
|
obj-$(CONFIG_PPC32) += entry_32.o setup_32.o
|
powerpc: Merge 32 and 64-bit dma code
We essentially adopt the 64-bit dma code, with some changes to support
32-bit systems, including HIGHMEM. dma functions on 32-bit are now
invoked via accessor functions which call the correct op for a device based
on archdata dma_ops. If there is no archdata dma_ops, this defaults
to dma_direct_ops.
In addition, the dma_map/unmap_page functions are added to dma_ops
because we can't just fall back on map/unmap_single when HIGHMEM is
enabled. In the case of dma_direct_*, we stop using map/unmap_single
and just use the page version - this saves a lot of ugly
ifdeffing. We leave map/unmap_single in the dma_ops definition,
though, because they are needed by the iommu code, which does not
implement map/unmap_page. Ideally, going forward, we will completely
eliminate map/unmap_single and just have map/unmap_page, if it's
workable for 64-bit.
Signed-off-by: Becky Bruce <becky.bruce@freescale.com>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
2008-09-12 18:34:46 +08:00
|
|
|
obj-$(CONFIG_PPC64) += dma-iommu.o iommu.o
|
2008-07-24 00:30:15 +08:00
|
|
|
obj-$(CONFIG_KGDB) += kgdb.o
|
2009-03-11 01:53:27 +08:00
|
|
|
obj-$(CONFIG_PPC_OF_BOOT_TRAMPOLINE) += prom_init.o
|
2005-09-28 18:28:14 +08:00
|
|
|
obj-$(CONFIG_MODULES) += ppc_ksyms.o
|
2005-10-06 10:06:20 +08:00
|
|
|
obj-$(CONFIG_BOOTX_TEXT) += btext.o
|
2005-11-05 07:33:55 +08:00
|
|
|
obj-$(CONFIG_SMP) += smp.o
|
2005-11-14 14:30:17 +08:00
|
|
|
obj-$(CONFIG_KPROBES) += kprobes.o
|
2006-01-10 13:19:05 +08:00
|
|
|
obj-$(CONFIG_PPC_UDBG_16550) += legacy_serial.o udbg_16550.o
|
2008-04-17 12:35:00 +08:00
|
|
|
obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
2009-05-14 20:42:28 +08:00
|
|
|
obj-$(CONFIG_SWIOTLB) += dma-swiotlb.o
|
2006-11-11 14:24:53 +08:00
|
|
|
|
2007-09-21 08:16:20 +08:00
|
|
|
pci64-$(CONFIG_PPC64) += pci_dn.o isa-bridge.o
|
|
|
|
obj-$(CONFIG_PCI) += pci_$(CONFIG_WORD_SIZE).o $(pci64-y) \
|
2009-08-26 04:07:11 +08:00
|
|
|
pci-common.o pci_of_scan.o
|
2007-05-08 10:58:34 +08:00
|
|
|
obj-$(CONFIG_PCI_MSI) += msi.o
|
2007-09-21 08:16:20 +08:00
|
|
|
obj-$(CONFIG_KEXEC) += machine_kexec.o crash.o \
|
|
|
|
machine_kexec_$(CONFIG_WORD_SIZE).o
|
2006-09-01 07:02:42 +08:00
|
|
|
obj-$(CONFIG_AUDIT) += audit.o
|
|
|
|
obj64-$(CONFIG_AUDIT) += compat_audit.o
|
2005-09-30 14:16:52 +08:00
|
|
|
|
2008-05-15 11:49:44 +08:00
|
|
|
obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
|
2009-02-10 13:10:27 +08:00
|
|
|
obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
|
perf: Do the big rename: Performance Counters -> Performance Events
Bye-bye Performance Counters, welcome Performance Events!
In the past few months the perfcounters subsystem has grown out its
initial role of counting hardware events, and has become (and is
becoming) a much broader generic event enumeration, reporting, logging,
monitoring, analysis facility.
Naming its core object 'perf_counter' and naming the subsystem
'perfcounters' has become more and more of a misnomer. With pending
code like hw-breakpoints support the 'counter' name is less and
less appropriate.
All in one, we've decided to rename the subsystem to 'performance
events' and to propagate this rename through all fields, variables
and API names. (in an ABI compatible fashion)
The word 'event' is also a bit shorter than 'counter' - which makes
it slightly more convenient to write/handle as well.
Thanks goes to Stephane Eranian who first observed this misnomer and
suggested a rename.
User-space tooling and ABI compatibility is not affected - this patch
should be function-invariant. (Also, defconfigs were not touched to
keep the size down.)
This patch has been generated via the following script:
FILES=$(find * -type f | grep -vE 'oprofile|[^K]config')
sed -i \
-e 's/PERF_EVENT_/PERF_RECORD_/g' \
-e 's/PERF_COUNTER/PERF_EVENT/g' \
-e 's/perf_counter/perf_event/g' \
-e 's/nb_counters/nb_events/g' \
-e 's/swcounter/swevent/g' \
-e 's/tpcounter_event/tp_event/g' \
$FILES
for N in $(find . -name perf_counter.[ch]); do
M=$(echo $N | sed 's/perf_counter/perf_event/g')
mv $N $M
done
FILES=$(find . -name perf_event.*)
sed -i \
-e 's/COUNTER_MASK/REG_MASK/g' \
-e 's/COUNTER/EVENT/g' \
-e 's/\<event\>/event_id/g' \
-e 's/counter/event/g' \
-e 's/Counter/Event/g' \
$FILES
... to keep it as correct as possible. This script can also be
used by anyone who has pending perfcounters patches - it converts
a Linux kernel tree over to the new naming. We tried to time this
change to the point in time where the amount of pending patches
is the smallest: the end of the merge window.
Namespace clashes were fixed up in a preparatory patch - and some
stylistic fallout will be fixed up in a subsequent patch.
( NOTE: 'counters' are still the proper terminology when we deal
with hardware registers - and these sed scripts are a bit
over-eager in renaming them. I've undone some of that, but
in case there's something left where 'counter' would be
better than 'event' we can undo that on an individual basis
instead of touching an otherwise nicely automated patch. )
Suggested-by: Stephane Eranian <eranian@google.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Paul Mackerras <paulus@samba.org>
Reviewed-by: Arjan van de Ven <arjan@linux.intel.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Howells <dhowells@redhat.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-arch@vger.kernel.org>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-09-21 18:02:48 +08:00
|
|
|
obj-$(CONFIG_PPC_PERF_CTRS) += perf_event.o perf_callchain.o
|
2009-06-17 19:50:04 +08:00
|
|
|
obj64-$(CONFIG_PPC_PERF_CTRS) += power4-pmu.o ppc970-pmu.o power5-pmu.o \
|
|
|
|
power5+-pmu.o power6-pmu.o power7-pmu.o
|
perf_counter: powerpc: Add processor back-end for MPC7450 family
This adds support for the performance monitor hardware on the
MPC7450 family of processors (7450, 7451, 7455, 7447/7457, 7447A,
7448), used in the later Apple G4 powermacs/powerbooks and other
machines. These machines have 6 hardware counters with a unique
set of events which can be counted on each counter, with some
events being available on multiple counters.
Raw event codes for these processors are (PMC << 8) + PMCSEL.
If PMC is non-zero then the event is that selected by the given
PMCSEL value for that PMC (hardware counter). If PMC is zero
then the event selected is one of the low-numbered ones that are
common to several PMCs. In this case PMCSEL must be <= 22 and
the event is what that PMCSEL value would select on PMC1 (but
it may be placed any other PMC that has the same event for that
PMCSEL value).
For events that count cycles or occurrences that exceed a threshold,
the threshold requested can be specified in the 0x3f000 bits of the
raw event codes. If the event uses the threshold multiplier bit
and that bit should be set, that is indicated with the 0x40000 bit
of the raw event code.
This fills in some of the generic cache events. Unfortunately there
are quite a few blank spaces in the table, partly because these
processors tend to count cache hits rather than cache accesses.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linuxppc-dev@ozlabs.org
Cc: benh@kernel.crashing.org
LKML-Reference: <19000.55631.802122.696927@cargo.ozlabs.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-06-17 19:53:51 +08:00
|
|
|
obj32-$(CONFIG_PPC_PERF_CTRS) += mpc7450-pmu.o
|
2008-05-15 11:49:44 +08:00
|
|
|
|
2007-09-19 04:29:35 +08:00
|
|
|
obj-$(CONFIG_8XX_MINIMAL_FPEMU) += softemu8xx.o
|
|
|
|
|
[POWERPC] Allow hooking of PCI MMIO & PIO accessors on 64 bits
This patch reworks the way iSeries hooks on PCI IO operations (both MMIO
and PIO) and provides a generic way for other platforms to do so (we
have need to do that for various other platforms).
While reworking the IO ops, I ended up doing some spring cleaning in
io.h and eeh.h which I might want to split into 2 or 3 patches (among
others, eeh.h had a lot of useless stuff in it).
A side effect is that EEH for PIO should work now (it used to pass IO
ports down to the eeh address check functions which is bogus).
Also, new are MMIO "repeat" ops, which other archs like ARM already had,
and that we have too now: readsb, readsw, readsl, writesb, writesw,
writesl.
In the long run, I might also make EEH use the hooks instead
of wrapping at the toplevel, which would make things even cleaner and
relegate EEH completely in platforms/iseries, but we have to measure the
performance impact there (though it's really only on MMIO reads)
Since I also need to hook on ioremap, I shuffled the functions a bit
there. I introduced ioremap_flags() to use by drivers who want to pass
explicit flags to ioremap (and it can be hooked). The old __ioremap() is
still there as a low level and cannot be hooked, thus drivers who use it
should migrate unless they know they want the low level version.
The patch "arch provides generic iomap missing accessors" (should be
number 4 in this series) is a pre-requisite to provide full iomap
API support with this patch.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-11 14:25:10 +08:00
|
|
|
ifneq ($(CONFIG_PPC_INDIRECT_IO),y)
|
2006-11-13 06:27:39 +08:00
|
|
|
obj-y += iomap.o
|
[POWERPC] Allow hooking of PCI MMIO & PIO accessors on 64 bits
This patch reworks the way iSeries hooks on PCI IO operations (both MMIO
and PIO) and provides a generic way for other platforms to do so (we
have need to do that for various other platforms).
While reworking the IO ops, I ended up doing some spring cleaning in
io.h and eeh.h which I might want to split into 2 or 3 patches (among
others, eeh.h had a lot of useless stuff in it).
A side effect is that EEH for PIO should work now (it used to pass IO
ports down to the eeh address check functions which is bogus).
Also, new are MMIO "repeat" ops, which other archs like ARM already had,
and that we have too now: readsb, readsw, readsl, writesb, writesw,
writesl.
In the long run, I might also make EEH use the hooks instead
of wrapping at the toplevel, which would make things even cleaner and
relegate EEH completely in platforms/iseries, but we have to measure the
performance impact there (though it's really only on MMIO reads)
Since I also need to hook on ioremap, I shuffled the functions a bit
there. I introduced ioremap_flags() to use by drivers who want to pass
explicit flags to ioremap (and it can be hooked). The old __ioremap() is
still there as a low level and cannot be hooked, thus drivers who use it
should migrate unless they know they want the low level version.
The patch "arch provides generic iomap missing accessors" (should be
number 4 in this series) is a pre-requisite to provide full iomap
API support with this patch.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-11-11 14:25:10 +08:00
|
|
|
endif
|
|
|
|
|
2005-11-18 12:43:34 +08:00
|
|
|
obj-$(CONFIG_PPC64) += $(obj64-y)
|
perf_counter: powerpc: Add processor back-end for MPC7450 family
This adds support for the performance monitor hardware on the
MPC7450 family of processors (7450, 7451, 7455, 7447/7457, 7447A,
7448), used in the later Apple G4 powermacs/powerbooks and other
machines. These machines have 6 hardware counters with a unique
set of events which can be counted on each counter, with some
events being available on multiple counters.
Raw event codes for these processors are (PMC << 8) + PMCSEL.
If PMC is non-zero then the event is that selected by the given
PMCSEL value for that PMC (hardware counter). If PMC is zero
then the event selected is one of the low-numbered ones that are
common to several PMCs. In this case PMCSEL must be <= 22 and
the event is what that PMCSEL value would select on PMC1 (but
it may be placed any other PMC that has the same event for that
PMCSEL value).
For events that count cycles or occurrences that exceed a threshold,
the threshold requested can be specified in the 0x3f000 bits of the
raw event codes. If the event uses the threshold multiplier bit
and that bit should be set, that is indicated with the 0x40000 bit
of the raw event code.
This fills in some of the generic cache events. Unfortunately there
are quite a few blank spaces in the table, partly because these
processors tend to count cache hits rather than cache accesses.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linuxppc-dev@ozlabs.org
Cc: benh@kernel.crashing.org
LKML-Reference: <19000.55631.802122.696927@cargo.ozlabs.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-06-17 19:53:51 +08:00
|
|
|
obj-$(CONFIG_PPC32) += $(obj32-y)
|
2005-11-18 12:43:34 +08:00
|
|
|
|
2008-12-17 18:09:01 +08:00
|
|
|
ifneq ($(CONFIG_XMON)$(CONFIG_KEXEC),)
|
2008-12-17 18:08:55 +08:00
|
|
|
obj-y += ppc_save_regs.o
|
|
|
|
endif
|
|
|
|
|
2009-08-10 03:02:51 +08:00
|
|
|
# Disable GCOV in odd or sensitive code
|
|
|
|
GCOV_PROFILE_prom_init.o := n
|
|
|
|
GCOV_PROFILE_ftrace.o := n
|
|
|
|
GCOV_PROFILE_machine_kexec_64.o := n
|
|
|
|
GCOV_PROFILE_machine_kexec_32.o := n
|
|
|
|
GCOV_PROFILE_kprobes.o := n
|
|
|
|
|
[PATCH] powerpc: Fix handling of fpscr on 64-bit
The recent merge of fpu.S broken the handling of fpscr for
ARCH=powerpc and CONFIG_PPC64=y. FP registers could be corrupted,
leading to strange random application crashes.
The confusion arises, because the thread_struct has (and requires) a
64-bit area to save the fpscr, because we use load/store double
instructions to get it in to/out of the FPU. However, only the low
32-bits are actually used, so we want to treat it as a 32-bit quantity
when manipulating its bits to avoid extra load/stores on 32-bit. This
patch replaces the current definition with a structure of two 32-bit
quantities (pad and val), to clarify things as much as is possible.
The 'val' field is used when manipulating bits, the structure itself
is used when obtaining the address for loading/unloading the value
from the FPU.
While we're at it, consolidate the 4 (!) almost identical versions of
cvt_fd() and cvt_df() (arch/ppc/kernel/misc.S,
arch/ppc64/kernel/misc.S, arch/powerpc/kernel/misc_32.S,
arch/powerpc/kernel/misc_64.S) into a single version in fpu.S. The
new version takes a pointer to thread_struct and applies the correct
offset itself, rather than a pointer to the fpscr field itself, again
to avoid confusion as to which is the correct field to use.
Finally, this patch makes ARCH=ppc64 also use the consolidated fpu.S
code, which it previously did not.
Built for G5 (ARCH=ppc64 and ARCH=powerpc), 32-bit powermac (ARCH=ppc
and ARCH=powerpc) and Walnut (ARCH=ppc, CONFIG_MATH_EMULATION=y).
Booted on G5 (ARCH=powerpc) and things which previously fell over no
longer do.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2005-10-27 14:27:25 +08:00
|
|
|
extra-$(CONFIG_PPC_FPU) += fpu.o
|
2009-06-03 05:17:37 +08:00
|
|
|
extra-$(CONFIG_ALTIVEC) += vector.o
|
2005-10-28 10:51:45 +08:00
|
|
|
extra-$(CONFIG_PPC64) += entry_64.o
|
2008-01-07 13:12:44 +08:00
|
|
|
|
|
|
|
extra-y += systbl_chk.i
|
|
|
|
$(obj)/systbl.o: systbl_chk
|
|
|
|
|
|
|
|
quiet_cmd_systbl_chk = CALL $<
|
|
|
|
cmd_systbl_chk = $(CONFIG_SHELL) $< $(obj)/systbl_chk.i
|
|
|
|
|
|
|
|
PHONY += systbl_chk
|
|
|
|
systbl_chk: $(src)/systbl_chk.sh $(obj)/systbl_chk.i
|
|
|
|
$(call cmd,systbl_chk)
|
2008-02-11 23:32:00 +08:00
|
|
|
|
2009-06-11 10:12:28 +08:00
|
|
|
ifeq ($(CONFIG_PPC_OF_BOOT_TRAMPOLINE),y)
|
2008-04-24 10:08:22 +08:00
|
|
|
$(obj)/built-in.o: prom_init_check
|
|
|
|
|
|
|
|
quiet_cmd_prom_init_check = CALL $<
|
|
|
|
cmd_prom_init_check = $(CONFIG_SHELL) $< "$(NM)" "$(obj)/prom_init.o"
|
|
|
|
|
|
|
|
PHONY += prom_init_check
|
|
|
|
prom_init_check: $(src)/prom_init_check.sh $(obj)/prom_init.o
|
|
|
|
$(call cmd,prom_init_check)
|
2009-06-11 10:12:28 +08:00
|
|
|
endif
|
2008-04-24 10:08:22 +08:00
|
|
|
|
2008-02-11 23:32:00 +08:00
|
|
|
clean-files := vmlinux.lds
|