27 Apr, 2008

1 commit


05 Feb, 2008

1 commit

  • Eliminate all build warnings. OK, these build warnings are from
    a build on x86_64. When I build on ia64, I don't see warnings.

    Now builds cleanly on ia64 and x86_64.

    Documentation/ia64/aliasing-test.c: In function 'map_mem':
    Documentation/ia64/aliasing-test.c:39: warning: implicit declaration of function 'ioctl'
    Documentation/ia64/aliasing-test.c: In function 'scan_rom':
    Documentation/ia64/aliasing-test.c:183: warning: format '%ld' expects type 'long int', but argument 4 has type 'int'
    Documentation/ia64/aliasing-test.c: At top level:
    Documentation/ia64/aliasing-test.c:208: warning: function declaration isn't a prototype
    Documentation/ia64/aliasing-test.c: In function 'main':
    Documentation/ia64/aliasing-test.c:259: warning: control reaches end of non-void function
    Documentation/ia64/aliasing-test.c: In function 'scan_rom':
    Documentation/ia64/aliasing-test.c:152: warning: 'rc' may be used uninitialized in this function
    Documentation/ia64/aliasing-test.c: In function 'scan_tree':
    Documentation/ia64/aliasing-test.c:68: warning: 'rc' may be used uninitialized in this function

    Signed-off-by: Randy Dunlap
    Acked-by: Bjorn Helgaas
    Signed-off-by: Andrew Morton
    Signed-off-by: Tony Luck

    Randy Dunlap
     

20 Oct, 2007

1 commit

  • Most of these fixes were already submitted for old kernel versions, and were
    approved, but for some reason they never made it into the releases.

    Because this is a consolidation of a couple old missed patches, it touches both
    Kconfigs and documentation texts.

    Signed-off-by: Matt LaPlante
    Acked-by: Randy Dunlap
    Signed-off-by: Adrian Bunk

    Matt LaPlante
     

12 Jul, 2007

1 commit

  • Example memory map (HP rx7640 with 'default' acpiconfig setting, VGA disabled):
    0x00000000 - 0x3FFFBFFF supports only WB (cacheable) access

    If a user attempts to perform an MMIO mmap (using the PCIIOC_MMAP_IS_MEM ioctl)
    to PCI config space (like mmap'ing and accessing memory at 0xA0000),
    we will MCA because the kernel will attempt to use a mapping with the UC
    attribute.

    So check the memory attribute in kern_mmap and the EFI memmap. If WC is
    requested, and WC or UC access is supported for the region, allow it.
    Otherwise, use the same attribute the kernel uses.

    Updates documentation and test cases as well.

    Signed-off-by: Alex Chiang
    Signed-off-by: Bjorn Helgaas
    Signed-off-by: Tony Luck

    Alex Chiang
     

01 Jun, 2007

1 commit

  • Fix various bits of obviously-busted code which we're not happening to
    compile, due to ifdefs.

    Cc: "Luck, Tony"
    Cc: Ivan Kokshaysky
    Cc: Richard Henderson
    Cc: Russell King
    Cc: Ralf Baechle
    Cc: Jeff Garzik
    Cc: Jan Kara
    Cc: James Bottomley
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Yoann Padioleau
     

01 May, 2007

1 commit


31 Mar, 2007

1 commit


06 Feb, 2007

1 commit


30 Jan, 2007

1 commit

  • This patch contains a documention and sample application. Since the sample
    application has ~1000 lines of code, it might not be suitable in a kernel
    documention in kenrel tree. If you think this is not good place to hold
    the sample application, please let me know and I'm open to other choices
    e.g. sourceforge etc.

    Signed-off-by: Fenghua Yu
    Signed-off-by: Tony Luck

    Fenghua Yu
     

04 Oct, 2006

2 commits


03 Oct, 2006

1 commit


09 May, 2006

1 commit

  • This closes a couple holes in our attribute aliasing avoidance scheme:

    - The current kernel fails mmaps of some /dev/mem MMIO regions because
    they don't appear in the EFI memory map. This keeps X from working
    on the Intel Tiger box.

    - The current kernel allows UC mmap of the 0-1MB region of
    /sys/.../legacy_mem even when the chipset doesn't support UC
    access. This causes an MCA when starting X on HP rx7620 and rx8620
    boxes in the default configuration.

    There's more detail in the Documentation/ia64/aliasing.txt file this
    adds, but the general idea is that if a region might be covered by
    a granule-sized kernel identity mapping, any access via /dev/mem or
    mmap must use the same attribute as the identity mapping.

    Otherwise, we fall back to using an attribute that is supported
    according to the EFI memory map, or to using UC if the EFI memory
    map doesn't mention the region.

    Signed-off-by: Bjorn Helgaas
    Signed-off-by: Tony Luck

    Bjorn Helgaas
     

17 Sep, 2005

1 commit


17 Apr, 2005

1 commit

  • 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