First  |  Prev |  Next  |  Last
Pages: 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390
[PATCH] checkpatch: Add warnings for use of mdelay()
mdelay is a busy-wait loop which is wasteful. If at all possible, callers should use msleep instead of mdelay. The only time mdelay is really appropriate is in atomic context, however, delays of 1ms+ in atomic context are rather expensive, so a warning for this case is probably appropriate as well to encourage p... 27 Jul 2010 13:57
PCI / PCIe: Ask BIOS for control of all native services simultaneously
On Tue, Jul 27, 2010 at 09:43:41AM +0900, Kenji Kaneshige wrote: I think this will break PCIe services currently working. For example, firmware doesn't grant PCIe AER control on my hardware. On the other hand, firmware grants PCIe native hot-plug control on the same machine. So I think PCIe hot-plug will ... 28 Jul 2010 08:32
bdi: Use parent filesystem BDI for inodes not capable of writeback
> +static struct backing_dev_info *inode_to_bdi(struct inode *inode) +{ + struct backing_dev_info *bdi = inode->i_mapping->backing_dev_info; + + /* + * This is a hack but it solves a problem with device inode + * for e.g. /dev/zero getting dirty (via touch or so) and confusing + * writeback code... 29 Jul 2010 08:35
ipmi: Run a dummy command before submitting a new command
I don't think this is the right way to handle the problem. Though it's not going to break anything, this change is just a hack. We need to figure out why these machine exhibit this behavior. If it's a bug in the driver, then we need to fix the driver. If it's a bug in the HP firmware, then we need to docume... 27 Jul 2010 13:57
bdi: Initialize noop_backing_dev_info properly
On Tue, Jul 27, 2010 at 07:05:01PM +0200, Jan Kara wrote: Properly initialize this backing dev info so that writeback code does not barf when getting to it e.g. via sb->s_bdi. When do we actually get it in s_bdi? That should never happen. -- To unsubscribe from this list: send the line "unsubscribe linux-... 27 Jul 2010 13:57
[PATCH 0/3] Fix warnings in __mark_inode_dirty
Hi, patches below fix (some of) warnings in __mark_inode_dirty complaining about unregistered BDI ( The issue is that device inodes describing non-writeable BDI can still get dirty but they would be filed to writeback lists of these non-writeable BDI's. N... 27 Jul 2010 13:57
[PATCH 1/3] bdi: Use parent filesystem BDI for inodes not capable of writeback
If inode->i_mapping->backing_dev_info is not capable of writeback but the inode gets dirty (because inode itself has changed), use inode lists of a bdi of a filesystem holding the device inode. Forking the flusher thread just to do the writeout of a single inode would be silly and generally bdi needn't be prepared ... 27 Jul 2010 13:57
[PATCH 2/3] char: Mark /dev/zero and /dev/kmem as not capable of writeback
These devices don't do any writeback but their device inodes still can get dirty so mark bdi appropriately so that bdi code does the right thing and files inodes to lists of bdi carrying the device inodes. Signed-off-by: Jan Kara <jack(a)> --- drivers/char/mem.c | 3 ++- fs/char_dev.c | 4 +++- ... 27 Jul 2010 13:57
[RESEND PATCH] x86: fix keeping track of AMD C1E
Accomodate the original C1E-aware idle routine to the different times during boot when the BIOS enables C1E. While at it, remove the synthetic CPUID flag in favor of a single global setting which denotes C1E status on the system. Signed-off-by: Michal Schmidt <mschmidt(a)> Signed-off-by: Borislav Petkov ... 27 Jul 2010 13:57
[PATCH 3/3] x86/amd-iommu: Export cache-coherency capability
This patch exports the capability of the AMD IOMMU to force cache coherency of DMA transactions through the IOMMU-API. This is required to disable some nasty hacks in KVM when this capability is not available. Signed-off-by: Joerg Roedel <joerg.roedel(a)> --- arch/x86/kernel/amd_iommu.c | 5 +++++ 1 f... 27 Jul 2010 12:50
First  |  Prev |  Next  |  Last
Pages: 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390