18 Nov, 2011

1 commit

  • Generate system call tables and unistd_*.h automatically from the
    tables in arch/x86/syscalls. All other information, like NR_syscalls,
    is auto-generated, some of which is in asm-offsets_*.c.

    This allows us to keep all the system call information in one place,
    and allows for kernel space and user space to see different
    information; this is currently used for the ia32 system call numbers
    when building the 64-bit kernel, but will be used by the x32 ABI in
    the near future.

    This also removes some gratuitious differences between i386, x86-64
    and ia32; in particular, now all system call tables are generated with
    the same mechanism.

    Cc: H. J. Lu
    Cc: Sam Ravnborg
    Cc: Michal Marek
    Signed-off-by: H. Peter Anvin

    H. Peter Anvin
     

22 Oct, 2010

1 commit


14 Oct, 2010

1 commit


14 Sep, 2010

1 commit

  • The arch/x86/Makefile uses scripts/gcc-x86_$(BITS)-has-stack-protector.sh
    to check if cc1 supports -fstack-protector. When -fPIE is passed to cc1,
    these scripts fail causing stack protection to be disabled even when it
    is available.

    This fix is similar to commit c47efe5548abbf53c2f66e06dcb46183b11d6b22

    Reported-by: Kai Dietrich
    Signed-off-by: Magnus Granberg
    LKML-Reference:
    Signed-off-by: Anthony G. Basile
    Cc: Andrew Morton
    Signed-off-by: H. Peter Anvin

    basile@opensource.dyc.edu
     

14 May, 2010

1 commit

  • The newer assemblers support the .cfi_sections directive so we can put
    the CFI from .S files into the .debug_frame section that is preserved
    in unstripped vmlinux and in separate debuginfo, rather than the
    .eh_frame section that is now discarded by vmlinux.lds.S.

    Signed-off-by: Roland McGrath
    LKML-Reference:
    Signed-off-by: H. Peter Anvin

    Roland McGrath
     

17 Feb, 2010

1 commit

  • For some reason the 64-bit tree was doing this differently and
    I can't see why it would need to.

    This correct behaviour when you have two GPUs plugged in and
    32-bit put the console in one place and 64-bit in another.

    Signed-off-by: Dave Airlie
    LKML-Reference:
    Signed-off-by: H. Peter Anvin

    Dave Airlie
     

17 Nov, 2009

1 commit


23 Oct, 2009

1 commit

  • STACKPROTECTOR_ALL has a really high overhead (runtime and stack
    footprint) and is not really worth it protection wise (the
    normal STACKPROTECTOR is in effect for all functions with
    buffers already), so lets just remove the option entirely.

    Reported-by: Dave Jones
    Reported-by: Chuck Ebbert
    Signed-off-by: Arjan van de Ven
    Cc: Eric Sandeen
    LKML-Reference:
    Signed-off-by: Ingo Molnar

    Arjan van de Ven
     

17 Oct, 2009

1 commit


24 Sep, 2009

1 commit


20 Sep, 2009

1 commit

  • Replace the use of CROSS_COMPILE to select a customized
    installkernel script with the possibility to set INSTALLKERNEL
    to select a custom installkernel script when running make:

    make INSTALLKERNEL=arm-installkernel install

    With this patch we are now more consistent across
    different architectures - they did not all support use
    of CROSS_COMPILE.

    The use of CROSS_COMPILE was a hack as this really belongs
    to gcc/binutils and the installkernel script does not change
    just because we change toolchain.

    The use of CROSS_COMPILE caused troubles with an upcoming patch
    that saves CROSS_COMPILE when a kernel is built - it would no
    longer be installable.
    [Thanks to Peter Z. for this hint]

    This patch undos what Ian did in commit:

    0f8e2d62fa04441cd12c08ce521e84e5bd3f8a46
    ("use ${CROSS_COMPILE}installkernel in arch/*/boot/install.sh")

    The patch has been lightly tested on x86 only - but all changes
    looks obvious.

    Acked-by: Peter Zijlstra
    Acked-by: Mike Frysinger [blackfin]
    Acked-by: Russell King [arm]
    Acked-by: Paul Mundt [sh]
    Acked-by: "H. Peter Anvin" [x86]
    Cc: Ian Campbell
    Cc: Tony Luck [ia64]
    Cc: Fenghua Yu [ia64]
    Cc: Hirokazu Takata [m32r]
    Cc: Geert Uytterhoeven [m68k]
    Cc: Kyle McMartin [parisc]
    Cc: Benjamin Herrenschmidt [powerpc]
    Cc: Martin Schwidefsky [s390]
    Cc: Thomas Gleixner [x86]
    Cc: Ingo Molnar [x86]
    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

14 Sep, 2009

2 commits

  • …/git/tip/linux-2.6-tip

    * 'x86-kbuild-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
    x86: Simplify the Makefile in a minor way through use of cc-ifversion

    Linus Torvalds
     
  • * 'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip: (22 commits)
    x86: Fix code patching for paravirt-alternatives on 486
    x86, msr: change msr-reg.o to obj-y, and export its symbols
    x86: Use hard_smp_processor_id() to get apic id for AMD K8 cpus
    x86, sched: Workaround broken sched domain creation for AMD Magny-Cours
    x86, mcheck: Use correct cpumask for shared bank4
    x86, cacheinfo: Fixup L3 cache information for AMD multi-node processors
    x86: Fix CPU llc_shared_map information for AMD Magny-Cours
    x86, msr: Fix msr-reg.S compilation with gas 2.16.1, on 32-bit too
    x86: Move kernel_fpu_using to irq_fpu_usable in asm/i387.h
    x86, msr: fix msr-reg.S compilation with gas 2.16.1
    x86, msr: Export the register-setting MSR functions via /dev/*/msr
    x86, msr: Create _on_cpu helpers for {rw,wr}msr_safe_regs()
    x86, msr: Have the _safe MSR functions return -EIO, not -EFAULT
    x86, msr: CFI annotations, cleanups for msr-reg.S
    x86, asm: Make _ASM_EXTABLE() usable from assembly code
    x86, asm: Add 32-bit versions of the combined CFI macros
    x86, AMD: Disable wrongly set X86_FEATURE_LAHF_LM CPUID bit
    x86, msr: Rewrite AMD rd/wrmsr variants
    x86, msr: Add rd/wrmsr interfaces with preset registers
    x86: add specific support for Intel Atom architecture
    ...

    Linus Torvalds
     

31 Aug, 2009

1 commit

  • Stack protector support was not detected when building with
    ARCH=i386 on x86_64 systems:

    arch/x86/Makefile:80: stack protector enabled but no compiler support

    The "-m32" argument needs to be passed to the detection script.

    Signed-off-by: Michal Schmidt
    Cc: Tejun Heo
    Cc: Jeremy Fitzhardinge
    Cc: Arjan van de Ven
    LKML-Reference:
    Signed-off-by: Ingo Molnar
    --

    Michal Schmidt
     

27 Aug, 2009

1 commit

  • Add a user-space selftest of x86 instruction decoder at kernel build
    time.
    When CONFIG_X86_DECODER_SELFTEST=y, Kbuild builds a test harness of x86
    instruction decoder and performs it after building vmlinux.
    The test compares the results of objdump and x86 instruction decoder
    code and check there are no differences.

    Signed-off-by: Masami Hiramatsu
    Signed-off-by: Jim Keniston
    Cc: Ananth N Mavinakayanahalli
    Cc: Avi Kivity
    Cc: Andi Kleen
    Cc: Christoph Hellwig
    Cc: Frank Ch. Eigler
    Cc: H. Peter Anvin
    Cc: Ingo Molnar
    Cc: Jason Baron
    Cc: K.Prasad
    Cc: Lai Jiangshan
    Cc: Li Zefan
    Cc: Przemysław Pawełczyk
    Cc: Roland McGrath
    Cc: Sam Ravnborg
    Cc: Srikar Dronamraju
    Cc: Steven Rostedt
    Cc: Tom Zanussi
    Cc: Vegard Nossum
    LKML-Reference:
    Signed-off-by: Frederic Weisbecker

    Masami Hiramatsu
     

23 Aug, 2009

1 commit


04 Aug, 2009

1 commit


13 Jun, 2009

1 commit

  • General description: kmemcheck is a patch to the linux kernel that
    detects use of uninitialized memory. It does this by trapping every
    read and write to memory that was allocated dynamically (e.g. using
    kmalloc()). If a memory address is read that has not previously been
    written to, a message is printed to the kernel log.

    Thanks to Andi Kleen for the set_memory_4k() solution.

    Andrew Morton suggested documenting the shadow member of struct page.

    Signed-off-by: Vegard Nossum
    Signed-off-by: Pekka Enberg

    [export kmemcheck_mark_initialized]
    [build fix for setup_max_cpus]
    Signed-off-by: Ingo Molnar

    [rebased for mainline inclusion]
    Signed-off-by: Vegard Nossum

    Vegard Nossum
     

11 Jun, 2009

1 commit

  • …/git/tip/linux-2.6-tip

    * 'x86-kbuild-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip: (46 commits)
    x86, boot: add new generated files to the appropriate .gitignore files
    x86, boot: correct the calculation of ZO_INIT_SIZE
    x86-64: align __PHYSICAL_START, remove __KERNEL_ALIGN
    x86, boot: correct sanity checks in boot/compressed/misc.c
    x86: add extension fields for bootloader type and version
    x86, defconfig: update kernel position parameters
    x86, defconfig: update to current, no material changes
    x86: make CONFIG_RELOCATABLE the default
    x86: default CONFIG_PHYSICAL_START and CONFIG_PHYSICAL_ALIGN to 16 MB
    x86: document new bzImage fields
    x86, boot: make kernel_alignment adjustable; new bzImage fields
    x86, boot: remove dead code from boot/compressed/head_*.S
    x86, boot: use LOAD_PHYSICAL_ADDR on 64 bits
    x86, boot: make symbols from the main vmlinux available
    x86, boot: determine compressed code offset at compile time
    x86, boot: use appropriate rep string for move and clear
    x86, boot: zero EFLAGS on 32 bits
    x86, boot: set up the decompression stack as early as possible
    x86, boot: straighten out ranges to copy/zero in compressed/head*.S
    x86, boot: stylistic cleanups for boot/compressed/head_64.S
    ...

    Fixed trivial conflict in arch/x86/configs/x86_64_defconfig manually

    Linus Torvalds
     

18 Apr, 2009

1 commit

  • It is common to use "make install" in restricted environments which
    differ from the one which was actually used to build the kernel. In
    such environments it is highly undesirable to trigger a rebuild of any
    part of the system. Worse, the rebuild may be spurious, triggered by
    differences in the environment.

    Signed-off-by: H. Peter Anvin
    Cc: Sam Ravnborg
    LKML-Reference:

    H. Peter Anvin
     

17 Apr, 2009

1 commit


13 Mar, 2009

2 commits


13 Feb, 2009

1 commit


10 Feb, 2009

1 commit

  • Impact: no default -fno-stack-protector if stackp is enabled, cleanup

    Stackprotector make rules had the following problems.

    * cc support test and warning are scattered across makefile and
    kernel/panic.c.

    * -fno-stack-protector was always added regardless of configuration.

    Update such that cc support test and warning are contained in makefile
    and -fno-stack-protector is added iff stackp is turned off. While at
    it, prepare for 32bit support.

    Signed-off-by: Tejun Heo
    Signed-off-by: Ingo Molnar

    Tejun Heo
     

29 Jan, 2009

2 commits


31 Dec, 2008

1 commit


23 Oct, 2008

1 commit


15 Oct, 2008

1 commit


26 Jul, 2008

1 commit


11 Jul, 2008

2 commits


08 Jul, 2008

1 commit


10 Jun, 2008

1 commit

  • ... so it could fall back to normal numa and we'd reduce the impact of the
    NUMAQ subarch.

    NUMAQ depends on GENERICARCH
    also decouple genericarch numa from acpi.
    also make it fall back to bigsmp if apicid > 8.

    Signed-off-by: Yinghai Lu
    Signed-off-by: Ingo Molnar

    Yinghai Lu
     

05 Jun, 2008

1 commit


26 May, 2008

1 commit

  • If the user selects the stack-protector config option, but does not have
    a gcc that has the right bits enabled (for example because it isn't build
    with a glibc that supports TLS, as is common for cross-compilers, but also
    because it may be too old), then the runtime test fails right now.

    This patch adds a warning message for this scenario. This warning accomplishes
    two goals
    1) the user is informed that the security option he selective isn't available
    2) the user is suggested to turn of the CONFIG option that won't work for him,
    and would make the runtime test fail anyway.

    Signed-off-by: Arjan van de Ven
    Signed-off-by: Ingo Molnar
    Signed-off-by: Thomas Gleixner

    Arjan van de Ven
     

13 May, 2008

1 commit


17 Apr, 2008

2 commits