25 Nov, 2013

5 commits

  • for tmp_part->header.name:
    it is "Terminating null required only for names < 12 chars".
    so need to limit the %.12s for it in printk

    additional info:

    %12s limit the width, not for the original string output length
    if name length is more than 12, it still can be fully displayed.
    if name length is less than 12, the ' ' will be filled before name.

    %.12s truly limit the original string output length (precision)

    Signed-off-by: Chen Gang
    Signed-off-by: Benjamin Herrenschmidt

    Chen Gang
     
  • In a recent patch:
    commit c13f20ac48328b05cd3b8c19e31ed6c132b44b42
    Author: Michael Neuling
    powerpc/signals: Mark VSX not saved with small contexts

    We fixed an issue but an improved solution was later discussed after the patch
    was merged.

    Firstly, this patch doesn't handle the 64bit signals case, which could also hit
    this issue (but has never been reported).

    Secondly, the original patch isn't clear what MSR VSX should be set to. The
    new approach below always clears the MSR VSX bit (to indicate no VSX is in the
    context) and sets it only in the specific case where VSX is available (ie. when
    VSX has been used and the signal context passed has space to provide the
    state).

    This reverts the original patch and replaces it with the improved solution. It
    also adds a 64 bit version.

    Signed-off-by: Michael Neuling
    Cc: stable@vger.kernel.org
    Signed-off-by: Benjamin Herrenschmidt

    Michael Neuling
     
  • When CONFIG_SPARSEMEM_VMEMMAP option is used in kernel, makedumpfile fails
    to filter vmcore dump as it fails to do vmemmap translations. So far
    dump filtering on ppc64 never had to deal with vmemmap addresses seperately
    as vmemmap regions where mapped in zone normal. But with the inclusion of
    CONFIG_SPARSEMEM_VMEMMAP config option in kernel, this vmemmap address
    translation support becomes necessary for dump filtering. For vmemmap adress
    translation, few kernel symbols are needed by dump filtering tool. This patch
    adds those symbols to vmcoreinfo, which a dump filtering tool can use for
    filtering the kernel dump. Tested this changes successfully with makedumpfile
    tool that supports vmemmap to physical address translation outside zone normal.

    [ Removed unneeded #ifdef as suggested by Michael Ellerman --BenH ]

    Signed-off-by: Hari Bathini
    Signed-off-by: Benjamin Herrenschmidt

    Hari Bathini
     
  • Stephen reported a failure in an allyesconfig build.
    CONFIG_CPU_LITTLE_ENDIAN=y gets set but his toolchain is not
    new enough to support little endian. We really want to
    default to a big endian build; Ben suggested using a choice
    which defaults to CPU_BIG_ENDIAN.

    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • Currently if I cross build TAGS or cscope from x86 I get this:
    % make ARCH=powerpc TAGS
    gcc-4.8.real: error: unrecognized command line option ‘-mbig-endian’
    GEN TAGS
    %

    I'm not setting CROSS_COMPILE= as logically I shouldn't need to and I
    haven't needed to in the past when building TAGS or cscope. Also, the
    above completess correct as the error is not fatal to the build.

    This was caused by:
    commit d72b08017161ab385d4ae080ea415c9eb7ceef83
    Author: Ian Munsie
    powerpc: Add ability to build little endian kernels

    The below fixes this by testing for the -mbig-endian option before
    adding it.

    I've not done the same thing in the little endian case as if
    -mlittle-endian doesn't exist, we probably want to fail quickly as you
    probably have an old big endian compiler.

    Signed-off-by: Michael Neuling
    Signed-off-by: Benjamin Herrenschmidt

    Michael Neuling
     

23 Nov, 2013

5 commits

  • And in flush_hugetlb_page(), don't check whether vma is NULL after
    we've already dereferenced it.

    This was found by Dan using static analysis as described here:
    https://lists.ozlabs.org/pipermail/linuxppc-dev/2013-November/113161.html

    We currently get away with this because the callers that currently pass
    NULL for vma seem to be 32-bit-only (e.g. highmem, and
    CONFIG_DEBUG_PGALLOC in pgtable_32.c) Hugetlb is currently 64-bit only,
    so we never saw a NULL vma here.

    Signed-off-by: Scott Wood
    Reported-by: Dan Carpenter

    Scott Wood
     
  • These lines were inoperative for four years, which puts some doubt into
    their importance, and it's possible the fixed version will regress, but
    at the very least they should be removed instead.

    Signed-off-by: Adam Borowski
    Signed-off-by: Scott Wood

    Adam Borowski
     
  • Commit beb2dc0a7a84be003ce54e98b95d65cc66e6e536 breaks the MPC8xx which
    seems to not support using mfspr SPRN_TBRx instead of mftb/mftbu
    despite what is written in the reference manual.

    This patch reverts to the use of mftb/mftbu when CONFIG_8xx is
    selected.

    Signed-off-by: Christophe Leroy
    Signed-off-by: Scott Wood

    LEROY Christophe
     
  • If CONFIG_ALTIVEC is enabled for CoreNet64, and if we also
    select CONFIG_E{5,6}500_CPU this may introduce -mcpu=e500mc64
    into $CFLAGS. But Altivec option not allowed with e500mc64,
    then some compiling errors occur like this:

    CC arch/powerpc/lib/xor_vmx.o
    arch/powerpc/lib/xor_vmx.c:1:0: error: AltiVec not supported in this target
    make[1]: *** [arch/powerpc/lib/xor_vmx.o] Error 1
    make: *** [arch/powerpc/lib] Error 2

    So we should restrict e500mc64 in altivec scenario.

    Signed-off-by: Tiejun Chen
    Signed-off-by: Scott Wood

    Tiejun Chen
     
  • Pull third set of powerpc updates from Benjamin Herrenschmidt:
    "This is a small collection of random bug fixes and a few improvements
    of Oops output which I deemed valuable enough to include as well.

    The fixes are essentially recent build breakage and regressions, and a
    couple of older bugs such as the DTL log duplication, the EEH issue
    with PCI_COMMAND_MASTER and the problem with small contexts passed to
    get/set_context with VSX enabled"

    * 'merge' of git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc:
    powerpc/signals: Mark VSX not saved with small contexts
    powerpc/pseries: Fix SMP=n build of rng.c
    powerpc: Make cpu_to_chip_id() available when SMP=n
    powerpc/vio: Fix a dma_mask issue of vio
    powerpc: booke: Fix build failures
    powerpc: ppc64 address space capped at 32TB, mmap randomisation disabled
    powerpc: Only print PACATMSCRATCH in oops when TM is active
    powerpc/pseries: Duplicate dtl entries sometimes sent to userspace
    powerpc: Remove a few lines of oops output
    powerpc: Print DAR and DSISR on machine check oopses
    powerpc: Fix __get_user_pages_fast() irq handling
    powerpc/eeh: More accurate log
    powerpc/eeh: Enable PCI_COMMAND_MASTER for PCI bridges

    Linus Torvalds
     

21 Nov, 2013

25 commits

  • The VSX MSR bit in the user context indicates if the context contains VSX
    state. Currently we set this when the process has touched VSX at any stage.

    Unfortunately, if the user has not provided enough space to save the VSX state,
    we can't save it but we currently still set the MSR VSX bit.

    This patch changes this to clear the MSR VSX bit when the user doesn't provide
    enough space. This indicates that there is no valid VSX state in the user
    context.

    This is needed to support get/set/make/swapcontext for applications that use
    VSX but only provide a small context. For example, getcontext in glibc
    provides a smaller context since the VSX registers don't need to be saved over
    the glibc function call. But since the program calling getcontext may have
    used VSX, the kernel currently says the VSX state is valid when it's not. If
    the returned context is then used in setcontext (ie. a small context without
    VSX but with MSR VSX set), the kernel will refuse the context. This situation
    has been reported by the glibc community.

    Based on patch from Carlos O'Donell.

    Tested-by: Haren Myneni
    Signed-off-by: Michael Neuling
    Cc: stable@vger.kernel.org
    Signed-off-by: Benjamin Herrenschmidt

    Michael Neuling
     
  • In commit a489043 "Implement arch_get_random_long() based on H_RANDOM" I
    broke the SMP=n build. We were getting plpar_wrappers.h via spinlock.h
    which breaks when SMP=n.

    Signed-off-by: Michael Ellerman
    Signed-off-by: Benjamin Herrenschmidt

    Michael Ellerman
     
  • Up until now we have only used cpu_to_chip_id() in the topology code,
    which is only used on SMP builds. However my recent commit a4da0d5
    "Implement arch_get_random_long/int() for powernv" added a usage when
    SMP=n, breaking the build.

    Move cpu_to_chip_id() into prom.c so it is available for SMP=n builds.

    We would move the extern to prom.h, but that breaks the include in
    topology.h. Instead we leave it in smp.h, but move it out of the
    CONFIG_SMP #ifdef. We also need to include asm/smp.h in rng.c, because
    the linux version skips asm/smp.h on UP. What a mess.

    Signed-off-by: Michael Ellerman
    Signed-off-by: Benjamin Herrenschmidt

    Michael Ellerman
     
  • I encountered following issue:
    [ 0.283035] ibmvscsi 30000015: couldn't initialize event pool
    [ 5.688822] ibmvscsi: probe of 30000015 failed with error -1

    which prevents the storage from being recognized, and the machine from
    booting.

    After some digging, it seems that it is caused by commit 4886c399da

    as dma_mask pointer in viodev->dev is not set, so in
    dma_set_mask_and_coherent(), dma_set_coherent_mask() is not called
    because dma_set_mask(), which is dma_set_mask_pSeriesLP() returned EIO.
    While before the commit, dma_set_coherent_mask() is always called.

    I tried to replace dma_set_mask_and_coherent() with
    dma_coerce_mask_and_coherent(), and the machine could boot again.

    Signed-off-by: Benjamin Herrenschmidt

    Li Zhong
     
  • arch/powerpc/platforms/wsp/wsp.c: In function ‘wsp_probe_devices’:
    arch/powerpc/platforms/wsp/wsp.c:76:3: error: implicit declaration of function ‘of_address_to_resource’ [-Werror=implicit-function-declaration]

    Signed-off-by: Aneesh Kumar K.V
    Signed-off-by: Benjamin Herrenschmidt

    Aneesh Kumar K.V
     
  • Commit fba2369e6ceb (mm: use vm_unmapped_area() on powerpc architecture)
    has a bug in slice_scan_available() where we compare an unsigned long
    (high_slices) against a shifted int. As a result, comparisons against
    the top 32 bits of high_slices (representing the top 32TB) always
    returns 0 and the top of our mmap region is clamped at 32TB

    This also breaks mmap randomisation since the randomised address is
    always up near the top of the address space and it gets clamped down
    to 32TB.

    Cc: stable@vger.kernel.org # v3.10+
    Signed-off-by: Anton Blanchard
    Acked-by: Michel Lespinasse
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • If TM is not active there is no need to print PACATMSCRATCH
    so we can save ourselves a line.

    Signed-off-by: Anton Blanchard
    Acked-by: Michael Neuling
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • When reading from the dispatch trace log (dtl) userspace interface, I
    sometimes see duplicate entries. One example:

    # hexdump -C dtl.out

    00000000 07 04 00 0c 00 00 48 44 00 00 00 00 00 00 00 00
    00000010 00 0c a0 b4 16 83 6d 68 00 00 00 00 00 00 00 00
    00000020 00 00 00 00 10 00 13 50 80 00 00 00 00 00 d0 32

    00000030 07 04 00 0c 00 00 48 44 00 00 00 00 00 00 00 00
    00000040 00 0c a0 b4 16 83 6d 68 00 00 00 00 00 00 00 00
    00000050 00 00 00 00 10 00 13 50 80 00 00 00 00 00 d0 32

    The problem is in scan_dispatch_log() where we call dtl_consumer()
    but bail out before incrementing the index.

    To fix this I moved dtl_consumer() after the timebase comparison.

    Signed-off-by: Anton Blanchard
    Cc: stable@vger.kernel.org
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • We waste quite a few lines in our oops output:

    ...
    MSR: 8000000000009032 CR: 28044024 XER: 00000000
    SOFTE: 0
    CFAR: 0000000000009088
    DAR: 000000000000001c, DSISR: 40000000

    GPR00: c0000000000c74f0 c00000037cc1b010 c000000000d2bb30 0000000000000000
    ...

    We can do a better job here and remove 3 lines:

    MSR: 8000000000009032 CR: 28044024 XER: 00000000
    CFAR: 0000000000009088 DAR: 0000000000000010, DSISR: 40000000 SOFTE: 1
    GPR00: c0000000000e3d10 c00000037cc2fda0 c000000000d2c3a8 0000000000000001

    Also move PACATMSCRATCH up, it doesn't really belong in the stack
    trace section.

    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • Machine check exceptions set DAR and DSISR, so print them in our
    oops output.

    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • __get_user_pages_fast() may be called with interrupts disabled (see e.g.
    get_futex_key() in kernel/futex.c) and therefore should use local_irq_save()
    and local_irq_restore() instead of local_irq_disable()/enable().

    Signed-off-by: Heiko Carstens
    CC: [v3.12]
    Signed-off-by: Benjamin Herrenschmidt

    Heiko Carstens
     
  • This clarifies in the log whether the error is a global PHB error
    or an individual PE being frozen.

    Signed-off-by: Gavin Shan
    Signed-off-by: Benjamin Herrenschmidt

    Gavin Shan
     
  • On PHB3, we will fail to fetch IODA tables without PCI_COMMAND_MASTER
    on PCI bridges. According to one experiment I had, the MSIx interrupts
    didn't raise from the adapter without the bit applied to all upstream
    PCI bridges including root port of the adapter. The patch forces to
    have that bit enabled accordingly.

    Signed-off-by: Gavin Shan
    CC:
    Signed-off-by: Benjamin Herrenschmidt

    Gavin Shan
     
  • Pull powerpc LE updates from Ben Herrenschmidt:
    "With my previous pull request I mentioned some remaining Little Endian
    patches, notably support for our new ABI, which I was sitting on
    making sure it was all finalized.

    The toolchain folks confirmed it now, the new ABI is stable and merged
    with gcc, so we are all good. Oh and we actually missed the actual
    Kconfig switch for LE so here it is, along with a couple more bug
    fixes.

    I have more fixes but not related to LE so I'll send them as a
    separate pull request tomorrow, let's get this one out of the way.

    Note that this supports running user space binaries using the new ABI,
    but the kernel itself still needs to be built with the old one. We'll
    bring fixes for that after -rc1.

    Here's Anton log that goes with this series:

    This patch series adds support for the new ABI, LPAR support for
    H_SET_MODE and finally adds a kconfig option and defconfig.

    ABIv2 support was recently committed to binutils and gcc, and should
    be merged into glibc soon. There are a number of very nice
    improvements including the removal of function descriptors. Rusty's
    kernel patches allow binaries of either ABI to work, easing the
    transition"

    * 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc:
    powerpc: Wrong DWARF CFI in the kernel vdso for little-endian / ELFv2
    powerpc: Add pseries_le_defconfig
    powerpc: Add CONFIG_CPU_LITTLE_ENDIAN kernel config option.
    powerpc: Don't use ELFv2 ABI to build the kernel
    powerpc: ELF2 binaries signal handling
    powerpc: ELF2 binaries launched directly.
    powerpc: Set eflags correctly for ELF ABIv2 core dumps.
    powerpc: Add TIF_ELF2ABI flag.
    pseries: Add H_SET_MODE to change exception endianness
    powerpc/pseries: Fix endian issues in pseries EEH code

    Linus Torvalds
     
  • I've finally tracked down why my CR signal-unwind test case still
    fails on little-endian. The problem turned to be that the kernel
    installs a signal trampoline in the vDSO, and provides a DWARF CFI
    record for that trampoline. This CFI describes the save location
    for CR:

    rsave (70, 38*RSIZE + (RSIZE - CRSIZE))

    which is correct for big-endian, but points to the wrong word on
    little-endian. This is wrong no matter which ABI.

    In addition, for the ELFv2 ABI, we should not only provide a CFI
    record for register 70 (cr2), but for all CR fields separately.
    Strictly speaking, I guess this would mean providing two separate
    vDSO images, one for ELFv1 processes and one for ELFv2 processes (or
    maybe playing some tricks with conditional DWARF expressions).
    However, having CFI records for the other CR fields in ELFv1 is not
    actually wrong, they just will be ignored. So it seems the simplest
    fix would be just to always provide CFI for all the fields.

    Signed-off-by: Ulrich Weigand
    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Ulrich Weigand
     
  • Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • With the little endian support merged, we can add the
    CONFIG_CPU_LITTLE_ENDIAN kernel config option.

    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • The kernel doesn't build correctly using the ELFv2 ABI. This patch
    ensures that the ELFv1 ABI is used when building a kernel with an
    ELFv2 enabled compiler.

    Signed-off-by: Alistair Popple
    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Alistair Popple
     
  • For the ELFv2 ABI, the hander is the entry point, not a function descriptor.
    We also need to set up r12, and fortunately the fast_exception_return
    exit path restores r12 for us so nothing else is required.

    Signed-off-by: Rusty Russell
    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Rusty Russell
     
  • No function descriptor, but we set r12 up and set TIF_RESTOREALL as it
    normally isn't restored on return from syscall.

    Signed-off-by: Rusty Russell
    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Rusty Russell
     
  • We leave it at zero (though it could be 1) for old tasks.

    Signed-off-by: Rusty Russell
    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Rusty Russell
     
  • Little endian ppc64 is getting an exciting new ABI. This is reflected
    by the bottom two bits of e_flags in the ELF header:

    0 == legacy binaries (v1 ABI)
    1 == binaries using the old ABI (compiled with a new toolchain)
    2 == binaries using the new ABI.

    We store this in a thread flag, because we need to set it in core
    dumps and for signal delivery. Our chief concern is that it doesn't
    use function descriptors.

    Signed-off-by: Rusty Russell
    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Rusty Russell
     
  • On little endian builds call H_SET_MODE so exceptions have the
    correct endianness. We need to reset the endian during kexec
    so do that in the MMU hashtable clear callback.

    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • Pull slave-dmaengine changes from Vinod Koul:
    "This brings for slave dmaengine:

    - Change dma notification flag to DMA_COMPLETE from DMA_SUCCESS as
    dmaengine can only transfer and not verify validaty of dma
    transfers

    - Bunch of fixes across drivers:

    - cppi41 driver fixes from Daniel

    - 8 channel freescale dma engine support and updated bindings from
    Hongbo

    - msx-dma fixes and cleanup by Markus

    - DMAengine updates from Dan:

    - Bartlomiej and Dan finalized a rework of the dma address unmap
    implementation.

    - In the course of testing 1/ a collection of enhancements to
    dmatest fell out. Notably basic performance statistics, and
    fixed / enhanced test control through new module parameters
    'run', 'wait', 'noverify', and 'verbose'. Thanks to Andriy and
    Linus [Walleij] for their review.

    - Testing the raid related corner cases of 1/ triggered bugs in
    the recently added 16-source operation support in the ioatdma
    driver.

    - Some minor fixes / cleanups to mv_xor and ioatdma"

    * 'next' of git://git.infradead.org/users/vkoul/slave-dma: (99 commits)
    dma: mv_xor: Fix mis-usage of mmio 'base' and 'high_base' registers
    dma: mv_xor: Remove unneeded NULL address check
    ioat: fix ioat3_irq_reinit
    ioat: kill msix_single_vector support
    raid6test: add new corner case for ioatdma driver
    ioatdma: clean up sed pool kmem_cache
    ioatdma: fix selection of 16 vs 8 source path
    ioatdma: fix sed pool selection
    ioatdma: Fix bug in selftest after removal of DMA_MEMSET.
    dmatest: verbose mode
    dmatest: convert to dmaengine_unmap_data
    dmatest: add a 'wait' parameter
    dmatest: add basic performance metrics
    dmatest: add support for skipping verification and random data setup
    dmatest: use pseudo random numbers
    dmatest: support xor-only, or pq-only channels in tests
    dmatest: restore ability to start test at module load and init
    dmatest: cleanup redundant "dmatest: " prefixes
    dmatest: replace stored results mechanism, with uniform messages
    Revert "dmatest: append verify result to results"
    ...

    Linus Torvalds
     

20 Nov, 2013

1 commit

  • Pull irq cleanups from Ingo Molnar:
    "This is a multi-arch cleanup series from Thomas Gleixner, which we
    kept to near the end of the merge window, to not interfere with
    architecture updates.

    This series (motivated by the -rt kernel) unifies more aspects of IRQ
    handling and generalizes PREEMPT_ACTIVE"

    * 'irq-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
    preempt: Make PREEMPT_ACTIVE generic
    sparc: Use preempt_schedule_irq
    ia64: Use preempt_schedule_irq
    m32r: Use preempt_schedule_irq
    hardirq: Make hardirq bits generic
    m68k: Simplify low level interrupt handling code
    genirq: Prevent spurious detection for unconditionally polled interrupts

    Linus Torvalds
     

16 Nov, 2013

2 commits

  • Pull trivial tree updates from Jiri Kosina:
    "Usual earth-shaking, news-breaking, rocket science pile from
    trivial.git"

    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial: (23 commits)
    doc: usb: Fix typo in Documentation/usb/gadget_configs.txt
    doc: add missing files to timers/00-INDEX
    timekeeping: Fix some trivial typos in comments
    mm: Fix some trivial typos in comments
    irq: Fix some trivial typos in comments
    NUMA: fix typos in Kconfig help text
    mm: update 00-INDEX
    doc: Documentation/DMA-attributes.txt fix typo
    DRM: comment: `halve' -> `half'
    Docs: Kconfig: `devlopers' -> `developers'
    doc: typo on word accounting in kprobes.c in mutliple architectures
    treewide: fix "usefull" typo
    treewide: fix "distingush" typo
    mm/Kconfig: Grammar s/an/a/
    kexec: Typo s/the/then/
    Documentation/kvm: Update cpuid documentation for steal time and pv eoi
    treewide: Fix common typo in "identify"
    __page_to_pfn: Fix typo in comment
    Correct some typos for word frequency
    clk: fixed-factor: Fix a trivial typo
    ...

    Linus Torvalds
     
  • Pull Kconfig cleanups from Mark Salter:
    "Remove some unused config options from C6X and clean up PC_PARPORT
    dependencies. The latter was discussed here:

    https://lkml.org/lkml/2013/10/8/12"

    * tag 'for-linus' of git://linux-c6x.org/git/projects/linux-c6x-upstreaming:
    c6x: remove unused COMMON_CLKDEV Kconfig parameter
    Kconfig cleanup (PARPORT_PC dependencies)
    x86: select ARCH_MIGHT_HAVE_PC_PARPORT
    unicore32: select ARCH_MIGHT_HAVE_PC_PARPORT
    sparc: select ARCH_MIGHT_HAVE_PC_PARPORT
    sh: select ARCH_MIGHT_HAVE_PC_PARPORT
    powerpc: select ARCH_MIGHT_HAVE_PC_PARPORT
    parisc: select ARCH_MIGHT_HAVE_PC_PARPORT
    mips: select ARCH_MIGHT_HAVE_PC_PARPORT
    microblaze: select ARCH_MIGHT_HAVE_PC_PARPORT
    m68k: select ARCH_MIGHT_HAVE_PC_PARPORT
    ia64: select ARCH_MIGHT_HAVE_PC_PARPORT
    arm: select ARCH_MIGHT_HAVE_PC_PARPORT
    alpha: select ARCH_MIGHT_HAVE_PC_PARPORT
    c6x: remove unused parameter in Kconfig

    Linus Torvalds
     

15 Nov, 2013

2 commits

  • Pull KVM changes from Paolo Bonzini:
    "Here are the 3.13 KVM changes. There was a lot of work on the PPC
    side: the HV and emulation flavors can now coexist in a single kernel
    is probably the most interesting change from a user point of view.

    On the x86 side there are nested virtualization improvements and a few
    bugfixes.

    ARM got transparent huge page support, improved overcommit, and
    support for big endian guests.

    Finally, there is a new interface to connect KVM with VFIO. This
    helps with devices that use NoSnoop PCI transactions, letting the
    driver in the guest execute WBINVD instructions. This includes some
    nVidia cards on Windows, that fail to start without these patches and
    the corresponding userspace changes"

    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm: (146 commits)
    kvm, vmx: Fix lazy FPU on nested guest
    arm/arm64: KVM: PSCI: propagate caller endianness to the incoming vcpu
    arm/arm64: KVM: MMIO support for BE guest
    kvm, cpuid: Fix sparse warning
    kvm: Delete prototype for non-existent function kvm_check_iopl
    kvm: Delete prototype for non-existent function complete_pio
    hung_task: add method to reset detector
    pvclock: detect watchdog reset at pvclock read
    kvm: optimize out smp_mb after srcu_read_unlock
    srcu: API for barrier after srcu read unlock
    KVM: remove vm mmap method
    KVM: IOMMU: hva align mapping page size
    KVM: x86: trace cpuid emulation when called from emulator
    KVM: emulator: cleanup decode_register_operand() a bit
    KVM: emulator: check rex prefix inside decode_register()
    KVM: x86: fix emulation of "movzbl %bpl, %eax"
    kvm_host: typo fix
    KVM: x86: emulate SAHF instruction
    MAINTAINERS: add tree for kvm.git
    Documentation/kvm: add a 00-INDEX file
    ...

    Linus Torvalds
     
  • We've switched over every architecture that supports SMP to it, so
    remove the new useless config variable.

    Signed-off-by: Christoph Hellwig
    Cc: Jan Kara
    Cc: Jens Axboe
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Christoph Hellwig