2005-09-26 10:04:21 +04:00
|
|
|
#
|
|
|
|
# Makefile for the linux kernel.
|
|
|
|
#
|
|
|
|
|
2007-12-20 14:58:00 +03:00
|
|
|
CFLAGS_ptrace.o += -DUTS_MACHINE='"$(UTS_MACHINE)"'
|
|
|
|
|
2005-09-30 07:51:25 +04:00
|
|
|
ifeq ($(CONFIG_PPC64),y)
|
2007-11-07 08:13:29 +03:00
|
|
|
CFLAGS_prom_init.o += -mno-minimal-toc
|
2005-09-30 07:51:25 +04:00
|
|
|
endif
|
2005-09-30 10:16:52 +04:00
|
|
|
ifeq ($(CONFIG_PPC32),y)
|
2005-10-06 06:06:20 +04:00
|
|
|
CFLAGS_prom_init.o += -fPIC
|
2005-10-06 07:24:50 +04:00
|
|
|
CFLAGS_btext.o += -fPIC
|
2005-09-30 10:16:52 +04:00
|
|
|
endif
|
2005-10-06 06:06:20 +04:00
|
|
|
|
2008-10-07 03:06:12 +04:00
|
|
|
ifdef CONFIG_FUNCTION_TRACER
|
2008-05-15 07:49:44 +04:00
|
|
|
# Do not trace early boot code
|
2008-09-02 10:50:38 +04: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-26 23:54:46 +03:00
|
|
|
CFLAGS_REMOVE_prom.o = -pg -mno-sched-epilog
|
2009-02-10 08:10:27 +03:00
|
|
|
# do not trace tracer code
|
2008-09-02 10:50:38 +04:00
|
|
|
CFLAGS_REMOVE_ftrace.o = -pg -mno-sched-epilog
|
2009-02-10 08:10:27 +03:00
|
|
|
# timers used by tracing
|
|
|
|
CFLAGS_REMOVE_time.o = -pg -mno-sched-epilog
|
2008-05-15 07:49:44 +04:00
|
|
|
endif
|
|
|
|
|
2008-03-08 05:55:58 +03:00
|
|
|
obj-y := cputable.o ptrace.o syscalls.o \
|
2006-01-12 13:22:34 +03:00
|
|
|
irq.o align.o signal_32.o pmc.o vdso.o \
|
2007-06-04 09:15:49 +04:00
|
|
|
init_task.o process.o systbl.o idle.o \
|
2008-12-23 21:55:54 +03:00
|
|
|
signal.o sysfs.o cacheinfo.o
|
2005-11-11 13:15:21 +03:00
|
|
|
obj-y += vdso32/
|
2008-01-03 04:03:11 +03:00
|
|
|
obj-$(CONFIG_PPC64) += setup_64.o sys_ppc32.o \
|
2006-02-10 08:02:20 +03:00
|
|
|
signal_64.o ptrace32.o \
|
2006-08-11 09:03:01 +04:00
|
|
|
paca.o cpu_setup_ppc970.o \
|
2007-02-05 01:36:51 +03:00
|
|
|
cpu_setup_pa6t.o \
|
2008-08-18 08:23:51 +04:00
|
|
|
firmware.o nvram_64.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 05:43:47 +04:00
|
|
|
obj64-$(CONFIG_RELOCATABLE) += reloc_64.o
|
2005-11-11 13:15:21 +03:00
|
|
|
obj-$(CONFIG_PPC64) += vdso64/
|
2005-10-10 16:50:37 +04:00
|
|
|
obj-$(CONFIG_ALTIVEC) += vecemu.o vector.o
|
2006-04-18 15:49:11 +04:00
|
|
|
obj-$(CONFIG_PPC_970_NAP) += idle_power4.o
|
2006-11-11 09:24:59 +03:00
|
|
|
obj-$(CONFIG_PPC_OF) += of_device.o of_platform.o prom_parse.o
|
2007-09-20 18:00:11 +04:00
|
|
|
obj-$(CONFIG_PPC_CLOCK) += clock.o
|
2005-11-10 07:26:20 +03:00
|
|
|
procfs-$(CONFIG_PPC64) := proc_ppc64.o
|
|
|
|
obj-$(CONFIG_PROC_FS) += $(procfs-y)
|
2007-03-04 09:04:44 +03:00
|
|
|
rtaspci-$(CONFIG_PPC64)-$(CONFIG_PCI) := rtas_pci.o
|
|
|
|
obj-$(CONFIG_PPC_RTAS) += rtas.o rtas-rtc.o $(rtaspci-y-y)
|
2005-11-03 06:41:19 +03:00
|
|
|
obj-$(CONFIG_RTAS_FLASH) += rtas_flash.o
|
|
|
|
obj-$(CONFIG_RTAS_PROC) += rtas-proc.o
|
2005-11-10 07:26:20 +03:00
|
|
|
obj-$(CONFIG_LPARCFG) += lparcfg.o
|
2005-10-24 08:22:37 +04:00
|
|
|
obj-$(CONFIG_IBMVIO) += vio.o
|
2005-11-16 10:56:43 +03:00
|
|
|
obj-$(CONFIG_IBMEBUS) += ibmebus.o
|
2005-11-04 05:28:58 +03:00
|
|
|
obj-$(CONFIG_GENERIC_TBSYNC) += smp-tbsync.o
|
2005-12-04 10:39:37 +03:00
|
|
|
obj-$(CONFIG_CRASH_DUMP) += crash_dump.o
|
2008-06-19 01:26:52 +04:00
|
|
|
obj-$(CONFIG_E500) += idle_e500.o
|
2006-03-27 12:15:26 +04:00
|
|
|
obj-$(CONFIG_6xx) += idle_6xx.o l2cr_6xx.o cpu_setup_6xx.o
|
|
|
|
obj-$(CONFIG_TAU) += tau_6xx.o
|
2007-09-21 04:16:20 +04:00
|
|
|
obj-$(CONFIG_HIBERNATION) += swsusp.o suspend.o \
|
|
|
|
swsusp_$(CONFIG_WORD_SIZE).o
|
|
|
|
obj64-$(CONFIG_HIBERNATION) += swsusp_asm64.o
|
2008-06-20 20:31:01 +04:00
|
|
|
obj-$(CONFIG_MODULES) += module.o module_$(CONFIG_WORD_SIZE).o
|
2007-10-04 05:02:09 +04:00
|
|
|
obj-$(CONFIG_44x) += cpu_setup_44x.o
|
2009-02-12 16:54:53 +03:00
|
|
|
obj-$(CONFIG_FSL_BOOKE) += cpu_setup_fsl_booke.o dbell.o
|
2005-10-10 16:50:37 +04:00
|
|
|
|
2005-10-10 15:52:43 +04:00
|
|
|
extra-$(CONFIG_PPC_STD_MMU) := head_32.o
|
2005-09-30 10:16:52 +04:00
|
|
|
extra-$(CONFIG_PPC64) := head_64.o
|
2007-08-20 16:27:07 +04:00
|
|
|
extra-$(CONFIG_40x) := head_40x.o
|
2005-09-26 10:04:21 +04: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 05:55:49 +04: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 14:34:46 +04:00
|
|
|
udbg.o misc.o io.o dma.o \
|
2007-09-21 04:16:20 +04: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 14:34:46 +04:00
|
|
|
obj-$(CONFIG_PPC64) += dma-iommu.o iommu.o
|
2008-07-23 20:30:15 +04:00
|
|
|
obj-$(CONFIG_KGDB) += kgdb.o
|
2009-03-10 20:53:27 +03:00
|
|
|
obj-$(CONFIG_PPC_OF_BOOT_TRAMPOLINE) += prom_init.o
|
2005-09-28 14:28:14 +04:00
|
|
|
obj-$(CONFIG_MODULES) += ppc_ksyms.o
|
2005-10-06 06:06:20 +04:00
|
|
|
obj-$(CONFIG_BOOTX_TEXT) += btext.o
|
2005-11-05 02:33:55 +03:00
|
|
|
obj-$(CONFIG_SMP) += smp.o
|
2005-11-14 09:30:17 +03:00
|
|
|
obj-$(CONFIG_KPROBES) += kprobes.o
|
2006-01-10 08:19:05 +03:00
|
|
|
obj-$(CONFIG_PPC_UDBG_16550) += legacy_serial.o udbg_16550.o
|
2008-04-17 08:35:00 +04:00
|
|
|
obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
2006-11-11 09:24:53 +03:00
|
|
|
|
2007-09-21 04:16:20 +04:00
|
|
|
pci64-$(CONFIG_PPC64) += pci_dn.o isa-bridge.o
|
|
|
|
obj-$(CONFIG_PCI) += pci_$(CONFIG_WORD_SIZE).o $(pci64-y) \
|
|
|
|
pci-common.o
|
2007-05-08 06:58:34 +04:00
|
|
|
obj-$(CONFIG_PCI_MSI) += msi.o
|
2007-09-21 04:16:20 +04:00
|
|
|
obj-$(CONFIG_KEXEC) += machine_kexec.o crash.o \
|
|
|
|
machine_kexec_$(CONFIG_WORD_SIZE).o
|
2006-09-01 03:02:42 +04:00
|
|
|
obj-$(CONFIG_AUDIT) += audit.o
|
|
|
|
obj64-$(CONFIG_AUDIT) += compat_audit.o
|
2005-09-30 10:16:52 +04:00
|
|
|
|
2008-05-15 07:49:44 +04:00
|
|
|
obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
|
2009-02-10 08:10:27 +03:00
|
|
|
obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
|
2008-05-15 07:49:44 +04:00
|
|
|
|
2007-09-19 00:29:35 +04: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 09:25:10 +03:00
|
|
|
ifneq ($(CONFIG_PPC_INDIRECT_IO),y)
|
2006-11-13 01:27:39 +03: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 09:25:10 +03:00
|
|
|
endif
|
|
|
|
|
2005-11-18 07:43:34 +03:00
|
|
|
obj-$(CONFIG_PPC64) += $(obj64-y)
|
|
|
|
|
2008-12-17 13:09:01 +03:00
|
|
|
ifneq ($(CONFIG_XMON)$(CONFIG_KEXEC),)
|
2008-12-17 13:08:55 +03:00
|
|
|
obj-y += ppc_save_regs.o
|
|
|
|
endif
|
|
|
|
|
[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 10:27:25 +04:00
|
|
|
extra-$(CONFIG_PPC_FPU) += fpu.o
|
2005-10-28 06:51:45 +04:00
|
|
|
extra-$(CONFIG_PPC64) += entry_64.o
|
2008-01-07 08:12:44 +03: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 18:32:00 +03:00
|
|
|
|
2008-04-24 06:08:22 +04: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)
|
|
|
|
|
2008-02-11 18:32:00 +03:00
|
|
|
clean-files := vmlinux.lds
|