hm. There should be no linkage between memory hotpluggability and So that's slub. Does slab already have this functionality or are you not bothering to maintain slab in this area? -

Add description about event notification callback routine to the document. Signed-off-by: Yasunori Goto <y-goto@jp.fujitsu.com> --- Documentation/memory-hotplug.txt | 58 ++++++++++++++++++++++++++++++++++++--- 1 file changed, 55 insertions(+), 3 deletions(-) Index: current/Documentation/memory-hotplug.txt =================================================================== --- current.orig/Documentation/memory-hotplug.txt 2007-10-17 15:57:50.000000000 +0900 +++ current/Documentation...

perhaps that open-coded writeback_set_ratelimit() should become a notifier callback. -

This patch simplifies /proc/cgroups by removing pointers and some debugging information, and simply presenting a list of subsystems, which hierarchy they are part of (if any) and the number of cgroups created for that subsystem. Hierarchy id is determined by the bitmask of subsystem ids attached to that hierarchy. Signed-off-by: Paul Menage <menage@google.com> --- Several people have commented that /proc/cgroups is too confusing or contains strange information. Here's an attempt to simpl...

Fix PCIe Hotplug so that it works with ExpressCard slots on Dell notebooks (and others?) in conjunction with the modparam of pciehp_force=1. The PCIe Hotplug driver has two issues when used on Dell notebooks which lack ACPI BIOS support for PCIe hotplug: 1. The driver does not recognise cards that were inserted prior to the driver being modprobe'd. 2. The driver stops functioning after a suspend/resume (RAM) cycle, and needs to be rmmod'd and modprobe'd to get it working again. This p...

(repost to conform with akpm's subject line conventions) One of three patches to fix PCIe Hotplug so that it works with ExpressCard slots on Dell notebooks (and others?) in conjunction with modparam of pciehp_force=1 Split out the hotplug hardware initialization code from pcie_init() into pcie_init_enable_events(), without changing any functionality. Signed-off-by: Mark Lord <mlord@pobox.com> --- --- a/drivers/pci/hotplug/pciehp_hpc.c 2007-10-17 19:06:38.000000000 -0400 +++ b/drivers/pci...

To make things simpler for distro people, I'm contemplating another patch in this series, to allow something like: pciehp_force=2 This would then *try* the ACPI BIOS calls, and only fall back to pcie_force=1 if the BIOS support fails. This would be an ideal default for most desktop/notebook distros to consider using. Without this, they don't have any good choice: use the defaults, and things fail on the most popular brand of machines in the marketplace. Use pciehp_force=1, and they may br...

02_pciehp_split_pcie_init.patch: Split out the hotplug hardware initialization code from pcie_init() into pcie_init_enable_events(), without changing any functionality. Signed-off-by: Mark Lord <mlord@pobox.com> --- --- git12/drivers/pci/hotplug/pciehp_hpc.c 2007-10-17 19:06:38.000000000 -0400 +++ linux/drivers/pci/hotplug/pciehp_hpc.c 2007-10-17 19:29:42.000000000 -0400 @@ -1067,99 +1067,22 @@ } #endif -int pcie_init(struct controller * ctrl, struct pcie_device *dev) +int pcie_ini...

03_pciehp_resume_reinit_hardware.patch: Make use of the previously split out pcie_init_enable_events() function to reinitialize the hotplug hardware on resume from suspend, but only when pciehp_force==1. Otherwise behaviour is unmodified. Signed-off-by: Mark Lord <mlord@pobox.com> --- --- git12/drivers/pci/hotplug/pciehp_ctrl.c 2007-10-17 19:28:23.000000000 -0400 +++ linux/drivers/pci/hotplug/pciehp_ctrl.c 2007-10-17 19:31:22.000000000 -0400 @@ -37,7 +37,6 @@ #include "pciehp.h" st...

01_pciehp_handle_preinserted_card.patch: Fix pciehp_probe() to deal with ExpressCard cards that were inserted prior to the driver being loaded. Signed-off-by: Mark Lord <mlord@pobox.com> --- --- git12/drivers/pci/hotplug/pciehp_ctrl.c 2007-10-17 22:30:19.000000000 -0400 +++ linux/drivers/pci/hotplug/pciehp_ctrl.c 2007-10-17 22:29:59.000000000 -0400 @@ -37,7 +37,6 @@ #include "pciehp.h" static void interrupt_event_handler(struct work_struct *work); -static int pciehp_enable_slot(stru...

Like many of us who earn a good living with Linux (for over a decade now) and follow the kernel developer discussions with waxing and waning interest depending on topic, I noticed James Morris' proposal to eliminate the LSM in favor of ordaining SELinux as THE security framework forever and amen, followed by the definitive decision by Linus that LSM would remain. Well, good, I thought. Linux should continue to represent freedom for anyone to use basic technology in any way he sees fit. I turned my atte...

I make no claims to worthyness, strongly deny being serious, Nope. I remain carefully neutral regarding the static/dynamic LSM issue. I was involved with the LSM when SELinux was still known as the Flask port and my development group proposed the first implementation, featuring authoritative hooks. Believe me, this The thing that killed authoritative hooks and that could kill LSM is the notion (which I refuse to take a side on) that out of tree I think the primary parties have gotten to the...

(cc-ing linux-ide) This doesn't seem a very reliable way to identify an IDE device, as all that 0 means is that the device does not claim conformance to any standard. I would think it would be legitimate for an IDE device to put a value like 5 in there as well, if it complies with SPC-4.. In the case of libata though, that appears to be due to this code in drivers/ata/libata-scsi.c: /* ATAPI devices typically report zero for their SCSI version, * and sometimes deviate from the spec WRT re...

synchronize_irq needs at the very least a compiler barrier and a read barrier on SMP, but there are enough cases around where a write barrier is also needed and it's not a hot path so I prefer using a full smp_mb() here. It will degrade to a compiler barrier on !SMP. Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> --- Index: linux-work/kernel/irq/manage.c =================================================================== --- linux-work.orig/kernel/irq/manage.c 2007-10-...

One could argue that it's the caller that should do the mb() but that would really be asking for trouble. Since most usage scenario require it, and it's not a hot path, I prefer having it here. Note that some kind of read barrier or compiler barrier should be needed regardless, or we are just not sync'ing with anything at all (we may have loaded the value ages ago and thus operate on a totally stale value). I prefer a full barrier to also ensure all previous stores are That isn't always t...

On Thu, 18 Oct 2007 11:25:42 +1000 Anyone reading this code is going to ask "wtf is that for". It needs a comment telling them. mb() is the new lock_kernel(). Sigh. -

Well, the new driver is not a fix. Anyway -- still plugging away at debugging libata. It seems some outside changes are causing a bunch of my test boxes to crap themselves. These need to go up in the meantime, however. Maybe its the sg-chaining stuff, we'll see. I'm watching that thread closely (after recovering from an email outage). Please pull from 'upstream-linus' branch of master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git upstream-linus to receive the following ...

The async_tx interface includes a completion callback. This adds support for using that callback, including using interrupts on completion. This second try does better at defining the callback prototype. Cc: David Miller <davem@davemloft.net> Signed-off-by: Shannon Nelson <shannon.nelson@intel.com> --- drivers/dma/ioat_dma.c | 25 +++++++++++++++++++++++++ 1 files changed, 25 insertions(+), 0 deletions(-) diff --git a/drivers/dma/ioat_dma.c b/drivers/dma/ioat_dma.c index 1...

At least 2 drivers (siimage and cs5535) have a bug where they use the construct: ide_drive_t *pair = &hwif->drives[drive->dn ^ 1]; To access the other drive in a master/slave pair. This is bogus because drive->dn is not the unit number, but the global drive number, thus can be 2 & 3 for ide1, 4 & 5 for ide2 etc... This causes the driver to access beyond the drive array into lalaland for any other interface than ide0 and in some case, actually crash :-) These 3 patches f...

The siimage use an incorrect construct to access the other drive of a pair, causing it to access beyond an array boundary on non-0 interfaces. This fixes it by using the new ide_get_paired_drive() hepler instead. Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> --- drivers/ide/pci/siimage.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: linux-work/drivers/ide/pci/siimage.c =================================================================== --- linux-wo...

2.6.23-git12 panics. Here's the short bit EIP:[<c01f5783>] blk_rq_map_sg+073/0x160 SS:ESP 0068:c2dc3df8 Kernel panic - not syncing: Fatal exception in interrupt -- Pete Clements -

Binaries get loaded into memory on demand, so it's quite possible that that part of the executable hasn't been loaded until something calls a function within it. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from hancockr@nospamshaw.ca Home Page: http://www.roberthancock.com/ -

Reorder the pci release actions Letting go of the resources in the right order helps get rid of occasional kernel complaints. Fix the pci_driver object name [Randy Dunlap] Rename the struct pci_driver data so that false section mismatch warnings won't be produced. Cc: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Shannon Nelson <shannon.nelson@intel.com> --- drivers/dma/ioat.c | 23 ++++++----------------- drivers/dma/ioat_dma.c | 5 ++++- 2 fil...

On Wed, 17 Oct 2007 17:14:39 -0700 Generates a warning on 32-bit: drivers/dma/ioat_dma.c: In function 'ioat_dma_test_callback': drivers/dma/ioat_dma.c:660: warning: cast from pointer to integer of different size and we can never ever print u64's anwyay: we dont' know what type the arch uses to implement them. The usual fix is to cast to unsigned long long, and when I remove this cast I get drivers/dma/ioat_dma.c: In function 'ioat_dma_self_test': drivers/dma/ioat_dma.c:718: warning: assig...

Yep - thanks. That's my misuse of Dan's dma_async_tx_callback typedef. sln -