21 Sep, 2011

1 commit

  • Change the CONFIG_DMAR to CONFIG_INTEL_IOMMU to be consistent
    with the other IOMMU options.

    Rename the CONFIG_INTR_REMAP to CONFIG_IRQ_REMAP to match the
    irq subsystem name.

    And define the CONFIG_DMAR_TABLE for the common ACPI DMAR
    routines shared by both CONFIG_INTEL_IOMMU and CONFIG_IRQ_REMAP.

    Signed-off-by: Suresh Siddha
    Cc: yinghai@kernel.org
    Cc: youquan.song@intel.com
    Cc: joerg.roedel@amd.com
    Cc: tony.luck@intel.com
    Cc: dwmw2@infradead.org
    Link: http://lkml.kernel.org/r/20110824001456.558630224@sbsiddha-desk.sc.intel.com
    Signed-off-by: Ingo Molnar

    Suresh Siddha
     

27 May, 2011

1 commit

  • The ns_cgroup is an annoying cgroup at the namespace / cgroup frontier and
    leads to some problems:

    * cgroup creation is out-of-control
    * cgroup name can conflict when pids are looping
    * it is not possible to have a single process handling a lot of
    namespaces without falling in a exponential creation time
    * we may want to create a namespace without creating a cgroup

    The ns_cgroup was replaced by a compatibility flag 'clone_children',
    where a newly created cgroup will copy the parent cgroup values.
    The userspace has to manually create a cgroup and add a task to
    the 'tasks' file.

    This patch removes the ns_cgroup as suggested in the following thread:

    https://lists.linux-foundation.org/pipermail/containers/2009-June/018616.html

    The 'cgroup_clone' function is removed because it is no longer used.

    This is a userspace-visible change. Commit 45531757b45c ("cgroup: notify
    ns_cgroup deprecated") (merged into 2.6.27) caused the kernel to emit a
    printk warning users that the feature is planned for removal. Since that
    time we have heard from XXX users who were affected by this.

    Signed-off-by: Daniel Lezcano
    Signed-off-by: Serge E. Hallyn
    Cc: Eric W. Biederman
    Cc: Jamal Hadi Salim
    Reviewed-by: Li Zefan
    Acked-by: Paul Menage
    Acked-by: Matt Helsley
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Daniel Lezcano
     

15 Aug, 2010

1 commit


04 Aug, 2010

1 commit

  • This patch adds a hwmon driver for package level thermal control. The driver
    dumps package level thermal information through sysfs interface so that upper
    level application (e.g. lm_sensor) can retrive the information.

    Instead of having the package level hwmon code in coretemp, I write a seperate
    driver pkgtemp because:

    First, package level thermal sensors include not only sensors for each core,
    but also sensors for uncore, memory controller or other components in the
    package. Logically it will be clear to have a seperate hwmon driver for package
    level hwmon to monitor wider range of sensors in a package. Merging package
    thermal driver into core thermal driver doesn't make sense and may mislead.

    Secondly, merging the two drivers together may cause coding mess. It's easier
    to include various package level sensors info if more sensor information is
    implemented. Coretemp code needs to consider a lot of legacy machine cases.
    Pkgtemp code only considers platform starting from Sandy Bridge.

    On a 1Sx4Cx2T Sandy Bridge platform, lm-sensors dumps the pkgtemp and coretemp:

    pkgtemp-isa-0000
    Adapter: ISA adapter
    physical id 0: +33.0°C (high = +79.0°C, crit = +99.0°C)

    coretemp-isa-0000
    Adapter: ISA adapter
    Core 0: +32.0°C (high = +79.0°C, crit = +99.0°C)

    coretemp-isa-0001
    Adapter: ISA adapter
    Core 1: +32.0°C (high = +79.0°C, crit = +99.0°C)

    coretemp-isa-0002
    Adapter: ISA adapter
    Core 2: +32.0°C (high = +79.0°C, crit = +99.0°C)

    coretemp-isa-0003
    Adapter: ISA adapter
    Core 3: +32.0°C (high = +79.0°C, crit = +99.0°C)

    [ hpa: folded v3 patch removing improper global variable "SHOW" ]

    Signed-off-by: Fenghua Yu
    LKML-Reference:
    Reviewed-by: Len Brown
    Signed-off-by: H. Peter Anvin

    Fenghua Yu
     

26 Aug, 2009

1 commit

  • s/HAVE_FTRACE_SYSCALLS/HAVE_SYSCALL_TRACEPOINTS/g
    s/TIF_SYSCALL_FTRACE/TIF_SYSCALL_TRACEPOINT/g

    The syscall enter/exit tracing is no longer specific to just ftrace, so
    they now have names that reflect their tie to tracepoints instead.

    Signed-off-by: Josh Stone
    Cc: Jason Baron
    Cc: Frederic Weisbecker
    Cc: Ingo Molnar
    Cc: Li Zefan
    Cc: Steven Rostedt
    Cc: Peter Zijlstra
    Cc: Mathieu Desnoyers
    Cc: Jiaying Zhang
    Cc: Martin Bligh
    Cc: Lai Jiangshan
    Cc: Paul Mundt
    Cc: Martin Schwidefsky
    Cc: Heiko Carstens
    LKML-Reference:
    Signed-off-by: Frederic Weisbecker

    Josh Stone
     

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
     

12 May, 2009

2 commits


28 Apr, 2009

1 commit

  • The original feature of migrating irq_desc dynamic was too fragile
    and was causing problems: it caused crashes on systems with lots of
    cards with MSI-X when user-space irq-balancer was enabled.

    We now have new patches that create irq_desc according to device
    numa node. This patch removes the leftover bits of the dynamic balancer.

    [ Impact: remove dead code ]

    Signed-off-by: Yinghai Lu
    Cc: Andrew Morton
    Cc: Suresh Siddha
    Cc: "Eric W. Biederman"
    Cc: Rusty Russell
    LKML-Reference:
    Signed-off-by: Ingo Molnar

    Yinghai Lu
     

26 Feb, 2009

1 commit


25 Feb, 2009

2 commits


23 Feb, 2009

1 commit

  • Impact: remove unused/broken code

    The Voyager subarch last built successfully on the v2.6.26 kernel
    and has been stale since then and does not build on the v2.6.27,
    v2.6.28 and v2.6.29-rc5 kernels.

    No actual users beyond the maintainer reported this breakage.
    Patches were sent and most of the fixes were accepted but the
    discussion around how to do a few remaining issues cleanly
    fizzled out with no resolution and the code remained broken.

    In the v2.6.30 x86 tree development cycle 32-bit subarch support
    has been reworked and removed - and the Voyager code, beyond the
    build problems already known, needs serious and significant
    changes and probably a rewrite to support it.

    CONFIG_X86_VOYAGER has been marked BROKEN then. The maintainer has
    been notified but no patches have been sent so far to fix it.

    While all other subarchs have been converted to the new scheme,
    voyager is still broken. We'd prefer to receive patches which
    clean up the current situation in a constructive way, but even in
    case of removal there is no obstacle to add that support back
    after the issues have been sorted out in a mutually acceptable
    fashion.

    So remove this inactive code for now.

    Signed-off-by: Ingo Molnar

    Ingo Molnar
     

13 Feb, 2009

1 commit


12 Feb, 2009

4 commits

  • It was enabled by mistake - iscsi is not included in a typical
    default PC, and no other architecture has it built-in (=y) either.

    Turn it off.

    Signed-off-by: Ingo Molnar

    Ingo Molnar
     
  • deprecation warnings have become rather noisy lately:

    drivers/i2c/i2c-core.c: In function ‘i2c_new_device’:
    drivers/i2c/i2c-core.c:283: warning: ‘i2c_attach_client’ is deprecated (declared at include/linux/i2c.h:434)
    drivers/i2c/i2c-core.c: In function ‘i2c_del_adapter’:
    drivers/i2c/i2c-core.c:646: warning: ‘detach_client’ is deprecated (declared at include/linux/i2c.h:154)
    drivers/i2c/i2c-core.c: In function ‘i2c_register_driver’:
    drivers/i2c/i2c-core.c:713: warning: ‘detach_client’ is deprecated (declared at include/linux/i2c.h:154)
    drivers/i2c/i2c-core.c: In function ‘__detach_adapter’:
    drivers/i2c/i2c-core.c:780: warning: ‘detach_client’ is deprecated (declared at include/linux/i2c.h:154)
    drivers/i2c/i2c-core.c: At top level:
    drivers/i2c/i2c-core.c:876: warning: ‘i2c_attach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:827)
    drivers/i2c/i2c-core.c:876: warning: ‘i2c_attach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:827)
    drivers/i2c/i2c-core.c:904: warning: ‘i2c_detach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:879)
    drivers/i2c/i2c-core.c:904: warning: ‘i2c_detach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:879)

    So turn it off for now - these reminders can obscure critical warnings.

    Signed-off-by: Ingo Molnar

    Ingo Molnar
     
  • Signed-off-by: Ingo Molnar

    Ingo Molnar
     
  • Signed-off-by: Ingo Molnar

    Ingo Molnar
     

30 Jan, 2009

1 commit


27 Jan, 2009

1 commit

  • Now that all EEPROM drivers live in the same place, let's harmonize
    their symbol names.

    Also fix eeprom's dependencies, it definitely needs sysfs, and is no
    longer experimental after many years in the kernel tree.

    Signed-off-by: Jean Delvare
    Acked-by: Wolfram Sang
    Cc: David Brownell

    Jean Delvare
     

19 Dec, 2008

1 commit

  • This commit:

    commit 5cb04df8d3f03e37a19f2502591a84156be71772
    Author: Ingo Molnar
    Date: Sun May 4 19:49:04 2008 +0200

    x86: defconfig updates

    changed CONFIG_RELOCATABLE from n to y, which may lead to a mismatch
    between the vmlinux debug information and the runtime location of the
    kernel, even when the bootloader does not relocate the kernel.

    Revert the specific change. Works for me with GRUB and qemu.

    Reference: http://lkml.org/lkml/2008/11/25/243

    Signed-off-by: Vegard Nossum
    Signed-off-by: Ingo Molnar

    Vegard Nossum
     

24 Nov, 2008

1 commit


16 Oct, 2008

1 commit


13 Oct, 2008

1 commit


12 Oct, 2008

1 commit


04 Oct, 2008

1 commit


06 Sep, 2008

1 commit

  • Additional updates to the x86 defconfigs. The goals are, as before:

    - Make them usable to testers, more so than distributors or end users,
    both of which are likely to have their own config already.
    - Keep 32 and 64 bits as similar as is practical.

    Changes:

    - Use a more generic CPU type (ppro and generic, respectively).
    - Bump number of CPUs to 64 (few if any NR_CPUS arrays left).
    - Enable PAT.
    - Enable OPTIMIZE_INLINE.
    - Enable microcode update support.
    - Build SMT scheduler support (in addition to MC).

    Signed-off-by: H. Peter Anvin
    Signed-off-by: Ingo Molnar

    H. Peter Anvin
     

04 Sep, 2008

1 commit


27 Aug, 2008

1 commit

  • Enable some option commonly used by testers in defconfig, including
    some very common device drivers and network boot support. defconfig
    is still not meant to be a kitchen-sink configuration.

    Signed-off-by: H. Peter Anvin

    H. Peter Anvin
     

20 Jul, 2008

1 commit

  • From: Arjan van de Ven
    Date: Sat, 19 Jul 2008 15:47:17 -0700

    CONFIG_NONPROMISC_DEVMEM was a rather confusing name - but renaming it
    to CONFIG_PROMISC_DEVMEM causes problems on architectures that do not
    support this feature; this patch renames it to CONFIG_STRICT_DEVMEM,
    so that architectures can opt-in into it.

    ( the polarity of the option is still the same as it was originally; it
    needs to be for now to not break architectures that don't have the
    infastructure yet to support this feature)

    Signed-off-by: Arjan van de Ven
    Cc: "V.Radhakrishnan"
    Signed-off-by: Ingo Molnar
    ---

    Ingo Molnar
     

13 May, 2008

3 commits


26 Apr, 2008

1 commit

  • add CONFIG_OPTIMIZE_INLINING=y.

    allow gcc to optimize the kernel image's size by uninlining
    functions that have been marked 'inline'. Previously gcc was
    forced by Linux to always-inline these functions via a gcc
    attribute:

    #define inline inline __attribute__((always_inline))

    Especially when the user has already selected
    CONFIG_OPTIMIZE_FOR_SIZE=y this can make a huge difference in
    kernel image size (using a standard Fedora .config):

    text data bss dec hex filename
    5613924 562708 3854336 10030968 990f78 vmlinux.before
    5486689 562708 3854336 9903733 971e75 vmlinux.after

    that's a 2.3% text size reduction (!).

    Signed-off-by: Ingo Molnar

    Ingo Molnar
     

10 Feb, 2008

1 commit


30 Jan, 2008

2 commits

  • Someone complained that the 32-bit defconfig contains AS as default IO
    scheduler. Change that to CFQ.

    Signed-off-by: Andi Kleen
    Signed-off-by: Ingo Molnar
    Signed-off-by: Thomas Gleixner

    Andi Kleen
     
  • Use sparsemem as the only memory model for UP, SMP and NUMA. Measurements
    indicate that DISCONTIGMEM has a higher overhead than sparsemem. And
    FLATMEMs benefits are minimal. So I think its best to simply standardize
    on sparsemem.

    Results of page allocator tests (test can be had via git from slab git
    tree branch tests)

    Measurements in cycle counts. 1000 allocations were performed and then the
    average cycle count was calculated.

    Order FlatMem Discontig SparseMem
    0 639 665 641
    1 567 647 593
    2 679 774 692
    3 763 967 781
    4 961 1501 962
    5 1356 2344 1392
    6 2224 3982 2336
    7 4869 7225 5074
    8 12500 14048 12732
    9 27926 28223 28165
    10 58578 58714 58682

    (Note that FlatMem is an SMP config and the rest NUMA configurations)

    Memory use:

    SMP Sparsemem
    -------------

    Kernel size:

    text data bss dec hex filename
    3849268 397739 1264856 5511863 541ab7 vmlinux

    total used free shared buffers cached
    Mem: 8242252 41164 8201088 0 352 11512
    -/+ buffers/cache: 29300 8212952
    Swap: 9775512 0 9775512

    SMP Flatmem
    -----------

    Kernel size:

    text data bss dec hex filename
    3844612 397739 1264536 5506887 540747 vmlinux

    So 4.5k growth in text size vs. FLATMEM.

    total used free shared buffers cached
    Mem: 8244052 40544 8203508 0 352 11484
    -/+ buffers/cache: 28708 8215344

    2k growth in overall memory use after boot.

    NUMA discontig:

    text data bss dec hex filename
    3888124 470659 1276504 5635287 55fcd7 vmlinux

    total used free shared buffers cached
    Mem: 8256256 56908 8199348 0 352 11496
    -/+ buffers/cache: 45060 8211196
    Swap: 9775512 0 9775512

    NUMA sparse:

    text data bss dec hex filename
    3896428 470659 1276824 5643911 561e87 vmlinux

    8k text growth. Given that we fully inline virt_to_page and friends now
    that is rather good.

    total used free shared buffers cached
    Mem: 8264720 57240 8207480 0 352 11516
    -/+ buffers/cache: 45372 8219348
    Swap: 9775512 0 9775512

    The total available memory is increased by 8k.

    This patch makes sparsemem the default and removes discontig and
    flatmem support from x86.

    [ akpm@linux-foundation.org: allnoconfig build fix ]

    Acked-by: Andi Kleen
    Signed-off-by: Christoph Lameter
    Signed-off-by: Andrew Morton
    Signed-off-by: Ingo Molnar
    Signed-off-by: Thomas Gleixner

    Christoph Lameter
     

30 Oct, 2007

1 commit


26 Oct, 2007

1 commit

  • With some small changes to kconfig makefile we can now
    locate the defconfig files for i386 and x86_64 in
    the configs/ subdirectory under x86.
    make ARCH=i386 defconfig and make defconfig
    works as expected also after this change.
    But arch maintainers shall now update a defconfig file in
    the configs/ directory.

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg