Eric Lee / smarc-fsl-linux-kernel

27 Jul, 2008

1 commit

  • 8d8bb39b9   dma-mapping: add the device argument to dma_mapping_error() ... Browse Code »

    Add per-device dma_mapping_ops support for CONFIG_X86_64 as POWER
    architecture does:

    This enables us to cleanly fix the Calgary IOMMU issue that some devices
    are not behind the IOMMU (http://lkml.org/lkml/2008/5/8/423).

    I think that per-device dma_mapping_ops support would be also helpful for
    KVM people to support PCI passthrough but Andi thinks that this makes it
    difficult to support the PCI passthrough (see the above thread). So I
    CC'ed this to KVM camp. Comments are appreciated.

    A pointer to dma_mapping_ops to struct dev_archdata is added. If the
    pointer is non NULL, DMA operations in asm/dma-mapping.h use it. If it's
    NULL, the system-wide dma_ops pointer is used as before.

    If it's useful for KVM people, I plan to implement a mechanism to register
    a hook called when a new pci (or dma capable) device is created (it works
    with hot plugging). It enables IOMMUs to set up an appropriate
    dma_mapping_ops per device.

    The major obstacle is that dma_mapping_error doesn't take a pointer to the
    device unlike other DMA operations. So x86 can't have dma_mapping_ops per
    device. Note all the POWER IOMMUs use the same dma_mapping_error function
    so this is not a problem for POWER but x86 IOMMUs use different
    dma_mapping_error functions.

    The first patch adds the device argument to dma_mapping_error. The patch
    is trivial but large since it touches lots of drivers and dma-mapping.h in
    all the architecture.

    This patch:

    dma_mapping_error() doesn't take a pointer to the device unlike other DMA
    operations. So we can't have dma_mapping_ops per device.

    Note that POWER already has dma_mapping_ops per device but all the POWER
    IOMMUs use the same dma_mapping_error function. x86 IOMMUs use device
    argument.

    [akpm@linux-foundation.org: fix sge]
    [akpm@linux-foundation.org: fix svc_rdma]
    [akpm@linux-foundation.org: build fix]
    [akpm@linux-foundation.org: fix bnx2x]
    [akpm@linux-foundation.org: fix s2io]
    [akpm@linux-foundation.org: fix pasemi_mac]
    [akpm@linux-foundation.org: fix sdhci]
    [akpm@linux-foundation.org: build fix]
    [akpm@linux-foundation.org: fix sparc]
    [akpm@linux-foundation.org: fix ibmvscsi]
    Signed-off-by: FUJITA Tomonori
    Cc: Muli Ben-Yehuda
    Cc: Andi Kleen
    Cc: Thomas Gleixner
    Cc: Ingo Molnar
    Cc: Avi Kivity
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    FUJITA Tomonori
     

13 Oct, 2007

1 commit

  • d3849d512   [SCSI] Fix ibmvscsi client for multiplatform iSeries+pSeries kernel ... Browse Code »

    If you build a multiplatform kernel for iSeries and pSeries, with
    ibmvscsic support, the resulting client doesn't work on iSeries.

    This fixes that, using the appropriate low-level operations
    for the machine detected at runtime.

    [jejb: fixed up rejections around the srp transport patch]

    Signed-off-by: David Woodhouse
    Acked by: Brian King
    Signed-off-by: Paul Mackerras
    Signed-off-by: James Bottomley

    David Woodhouse
     

18 Jun, 2007

1 commit

  • 6c0a60ec5   [SCSI] ibmvscsi: Enhanced error logging ... Browse Code »

    Converts ibmvscsi to use dev_printk and friends to simplify
    debugging. ibmvscsi adapter initialization now looks like this:

    ibmvscsi 30000005: SRP_VERSION: 16.a
    ibmvscsi 30000005: partner initialization complete
    ibmvscsi 30000005: sent SRP login
    ibmvscsi 30000005: SRP_LOGIN succeeded

    Additionally, this patch adds the logging of a couple return codes in
    a couple logs.

    Signed-off-by: Brian King
    Signed-off-by: James Bottomley

    Brian King
     

02 May, 2007

1 commit

26 Apr, 2007

1 commit

24 Apr, 2007

1 commit

13 Apr, 2007

1 commit

05 Oct, 2006

1 commit

  • 7d12e780e   IRQ: Maintain regs pointer globally rather than passing to IRQ handlers ... Browse Code »

    Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
    of passing regs around manually through all ~1800 interrupt handlers in the
    Linux kernel.

    The regs pointer is used in few places, but it potentially costs both stack
    space and code to pass it around. On the FRV arch, removing the regs parameter
    from all the genirq function results in a 20% speed up of the IRQ exit path
    (ie: from leaving timer_interrupt() to leaving do_IRQ()).

    Where appropriate, an arch may override the generic storage facility and do
    something different with the variable. On FRV, for instance, the address is
    maintained in GR28 at all times inside the kernel as part of general exception
    handling.

    Having looked over the code, it appears that the parameter may be handed down
    through up to twenty or so layers of functions. Consider a USB character
    device attached to a USB hub, attached to a USB controller that posts its
    interrupts through a cascaded auxiliary interrupt controller. A character
    device driver may want to pass regs to the sysrq handler through the input
    layer which adds another few layers of parameter passing.

    I've build this code with allyesconfig for x86_64 and i386. I've runtested the
    main part of the code on FRV and i386, though I can't test most of the drivers.
    I've also done partial conversion for powerpc and MIPS - these at least compile
    with minimal configurations.

    This will affect all archs. Mostly the changes should be relatively easy.
    Take do_IRQ(), store the regs pointer at the beginning, saving the old one:

    struct pt_regs *old_regs = set_irq_regs(regs);

    And put the old one back at the end:

    set_irq_regs(old_regs);

    Don't pass regs through to generic_handle_irq() or __do_IRQ().

    In timer_interrupt(), this sort of change will be necessary:

    - update_process_times(user_mode(regs));
    - profile_tick(CPU_PROFILING, regs);
    + update_process_times(user_mode(get_irq_regs()));
    + profile_tick(CPU_PROFILING);

    I'd like to move update_process_times()'s use of get_irq_regs() into itself,
    except that i386, alone of the archs, uses something other than user_mode().

    Some notes on the interrupt handling in the drivers:

    (*) input_dev() is now gone entirely. The regs pointer is no longer stored in
    the input_dev struct.

    (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
    something different depending on whether it's been supplied with a regs
    pointer or not.

    (*) Various IRQ handler function pointers have been moved to type
    irq_handler_t.

    Signed-Off-By: David Howells
    (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)

    David Howells
     

01 Aug, 2006

1 commit

31 Jul, 2006

1 commit

10 Jul, 2006

1 commit

26 Jun, 2006

1 commit

13 Apr, 2006

1 commit

01 Apr, 2006

1 commit

26 Jan, 2006

1 commit

07 Dec, 2005

1 commit

  • bb58596f6   [SCSI] ibmvscsi kexec fix ... Browse Code »

    This makes ibmvscsi work correctly with the recent set of kexec
    patches that went in. This is based on work by Michael Ellerman, who
    chased this initially. He validated that it works during kexec.

    Handle kexec correctly in ibmvscsi. During kexec the adapter
    will not get cleaned up correctly, so we may need to reset it
    to make it sane again.

    Signed-off-by: Dave Boutcher
    Signed-off-by: James Bottomley

    Dave C Boutcher
     

30 Aug, 2005

1 commit

  • 71d276d75   [PATCH] Create vio_bus_ops ... Browse Code »

    Create vio_bus_ops so that we just pass a structure to vio_bus_init
    instead of three separate function pointers.

    Rearrange vio.h to avoid forward references. vio.h only needs
    struct device_node from prom.h so remove the include and just
    declare it.

    Signed-off-by: Stephen Rothwell
    Signed-off-by: Paul Mackerras

    Stephen Rothwell
     

03 Jul, 2005

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds