- 01 Mar, 2004 4 commits
-
-
David Mosberger authored
done by these routines is very special and needs to be done at exactly the right time. Removing it from the header-file reduces the risk of accidental misuse. Other arch maintainers agree that this is the Right Thing to do.
-
Matthew Wilcox authored
Support for extended config space on ia64. - Add the new parameter 'type' to ia64_sal_pci_config_{read,write} - Change callers to match. - Don't check `value' for NULL -- drivers/pci/access.c guarantees it isn't. - Make pci_sal_ops static. - Add pci_sal_ext_ops. - Introduce pci_set_sal_ops() as an arch_initcall to ensure the raw_pci_ops get set before we walk the ACPI namespace to discover PCI root bridges
-
Matthew Wilcox authored
This patch reorganises sal.c and adds a small amount of new functionality. - Introduce sal_revision to report what revision of the SAL spec is supported by the system. - Introduce sal_version to report what version of the vendor's SAL implementation is present. - Introduce SAL_VERSION_CODE to allow for easy comparisons. - Print the version at boot, and remove the 'oem=' and 'vendor=' strings. - Refactor ia64_sal_init() into several smaller functions. - Delete the dead variables 'max' and 'min'. - Stop printing the pal_proc and sal_proc entry addresses. - Print "None" if there are no SAL platform features.
-
Matthew Wilcox authored
Here's my attempt at a zx1_defconfig. I haven't checked it on many of the zx1 boxes (only zx2000 and rx2600) but I've set some options I know are needed on the other boxes.
-
- 28 Feb, 2004 1 commit
-
-
Alex Williamson authored
This is a minor update to sba_iommu initialization code. I moved the relaxed ordering to the zx1 specific init routine, those registers don't do anything on sx1000. The iommu page size setup is more generalized on ACPI ID, so the sx1000 specific init routine goes away. And the virtual dma_mask on zx1 was tweaked a little to better reflect the memory address space.
-
- 27 Feb, 2004 35 commits
-
-
David Mosberger authored
The pdflush kernel threads can lead to an unbounded chain of thread-creations which can overflow the kernel stacks because we didn't uses to reset the stack on kernel thread-creation. We do now. Reported by Andreas Schwab, tracked down with help from Keith Owens.
-
Peter Chubb authored
This patch changes the I/O SAPIC code to cache the low 32 bits of the mask word in kernel memory. This greatly speeds up mask_irq() and unmask_irq(). Normally, these operations are not on the speed-critical path of the kernel but with certain devices drivers (including users-level device- drivers) they can become performance-critical.
-
Stéphane Eranian authored
- fix bug in pfm_unload(), not allowed when not on correct CPU for system-wide - some perf/cleanup in overflow handler - fix reset_pmds to be on a per PMD basis on counter overflow rather than global - remove timing debug code on messages - no kernel info leak on PFM_END_MSG - remove double-store on reg_flags for pfm_write_pmcs, pfm_write_pmds - on restart reset_pmds is 0 by default - cleanup useless macros - cleanup some debug prints - added ability to remove debug code - streamlined sys_perfmonctl(), pfm_read_pmds(), pfm_write_*() - added current->tgid to default format sample header by using one reserved field
-
David Mosberger authored
The problem was that IDE-disks on machines with IDE harddisks, memory above 4GB and no hardware I/O TLB would go BUG_ON() in blk_queue_bounce_limit() because the IDE-controller could only address 4GB of memory and that was much less than BLK_BOUNCE_ISA (which is equal to ISA_DMA_THRESHOLD). Note that the problem does NOT trigger with CD-ROMs, which always uses the software I/O TLB (and hence bounce-buffers) on such machines. The best fix seems to be to simply lower ISA_DMA_THRESHOLD to 4GB-1 since that will ensure that the IDE block layer allocates memory with GFP_DMA, which will minimize bounce buffering.
-
David Mosberger authored
into tiger.hpl.hp.com:/data1/bk/lia64/to-linus-2.5
-
Kenneth W. Chen authored
This patch fixes a bug which could cause do_softirq() to be called at the wrong time (from do_IRQ()) or without pre-emption protection.
-
Linus Torvalds authored
-
David S. Miller authored
into kernel.bkbits.net:/home/davem/net-2.6
-
http://linux-lksctp.bkbits.net/lksctp-2.5.workDavid S. Miller authored
into nuts.davemloft.net:/disk1/BK/net-2.6
-
David S. Miller authored
-
bk://gkernel.bkbits.net/misc-2.5Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.5/linux
-
Jeff Garzik authored
of redundancy, and to help prevent future errors.
-
Hollis Blanchard authored
This makes GregKH happy by removing the device name from the device.bus_id field (and replacing it with a "name" sysfs attribute). It also renames the parent device from "vdevice" to "vio", making the /sys/bus and /sys/devices hierarchies consistent.
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.5/linux
-
Russell King authored
-
Russell King authored
Add documentation for the above two functions. Allow a NULL name to be passed to amba_request_regions. In this case, we use the driver's name associated with the device.
-
Russell King authored
-
Russell King authored
This allows the decompressor to automatically detect the geometry of the cache while booting to ensure correct behaviour over a wider number of ARM CPUs.
-
Russell King authored
This optimises the underlying string-long read function for little endian platforms.
-
Russell King authored
This gives greater information on the cause of the bad IRQ, allowing the cause to be more effectively traced.
-
Russell King authored
-
Russell King authored
The old sysctl PM interface has been replaced by the driver models interface. This has been gone for a while in the -rmk tree and no one complained, so there's no point keeping it around.
-
Russell King authored
-
Russell King authored
- use dev_dbg for device-centric debugging messages - use pr_debug for general debugging messages - use dmapools instead of pcipools - use NULL rather than 0 for NULL pointers - use enum dma_data_direction rather than int - use DMA_* direction definitions rather than PCI_DMA_* - only check for sane DMA direction on mapping functions, but check that DMA direction matches when unmapping/syncing.
-
Russell King authored
Thanks to Adrian Bunk. Remove kernel 2.0 #ifdef's from arm code, and move MODULE_* to the end of the file. Add an appropriate MODULE_LICENSE().
-
Kenneth W. Chen authored
This patch makes it possible to select the hugetlbfs page size at boot-time, rather than at compile-time. We believe we have resolved all the remaining issues. All critical speed path has been taken care of, i.e., vhpt handler and context switch. There should be no performance penalty with this dynamic hugetlb page size feature. We would like to thank Jack Steiner for his initiative on this feature and his initial cool working patch.
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Sridhar Samudrala authored
Currently, sinit_max_init_timeo is treated as the maximum timeout value for INIT retransmissions and the INIT process is aborted when the timeout reaches this value. But as per the SCTP sockets API draft, sinit_max_init_timeo only limits the timeout. The INIT process should be aborted only after MAX_INIT_RETRANSMITS.
-
Anton Blanchard authored
Add an iseries defconfig and update the pseries one.
-
Anton Blanchard authored
CONFIG_VETH isnt used anymore so we lets get rid of it.
-
Anton Blanchard authored
Fix a compile error in the ppc64 pci hotplug code.
-
Anton Blanchard authored
ppc64 tlb flush rework from Paul Mackerras Instead of doing a double pass of the pagetables, we batch things up in the pte flush routines and then shoot the batch down in flush_tlb_pending. Our page aging was broken, we never flushed entries out of the ppc64 hashtable. We now flush in ptep_test_and_clear_young. A number of other things were fixed up in the process: - change ppc64_tlb_batch to per cpu data - remove some LPAR debug code - be more careful with ioremap_mm inits - clean up arch/ppc64/mm/init.c, create tlb.c
-
Anton Blanchard authored
Set the ks bit on userspace segments otherwise the kernel can read/write into userspace mprotected pages.
-
Benjamin Herrenschmidt authored
This allows us to use more than 2Gb of RAM on a PowerMac G5. You can also boot with iommu=off to disable it, but then you get back the 2Gb RAM limitation.
-