litmus-rt.git/drivers/base, branch wip-pm-ovd

PM: fix irq enable/disable in runtime PM code

2009-11-29T15:51:27+00:00

This patch (as1305) fixes a bug in the irq-enable settings and removes
some related overhead in the runtime PM code.

	In __pm_runtime_resume(), within the scope of the original
	spin_lock_irq(), we know that irqs are disabled.  There's no
	reason to go through a pair of enable/disable cycles when
	acquiring and releasing the parent's lock.

	In __pm_runtime_set_status(), irqs are already disabled when
	the parent's lock is acquired, and they must remain disabled
	when it is released.

Signed-off-by: Alan Stern 
Signed-off-by: Rafael J. Wysocki

PM: Remove some debug messages producing too much noise

2009-11-03T10:18:18+00:00

pm_runtime_idle() is somewhat noisy. Remove debug prints.

Signed-off-by: Pavel Machek 
Signed-off-by: Rafael J. Wysocki

PM: Fix warning on suspend errors

2009-11-03T10:03:33+00:00

Fixes the point where we need to complete the power transition when
device suspend fails, so that we don't print warnings about devices
added to the device hierarchy after a failing suspend.

[rjw: Modified changelog.]

Signed-off-by: Romit Dasgupta 
Signed-off-by: Rafael J. Wysocki

Driver core: allow certain drivers prohibit bind/unbind via sysfs

2009-10-30T21:59:51+00:00

Platform drivers registered via platform_driver_probe() can be bound
to devices only once, upon registration, because discard their probe()
routines to save memory. Unbinding the driver through sysfs 'unbind'
leaves the device stranded and confuses users so let's not create
bind and unbind attributes for such drivers.

Signed-off-by: Dmitry Torokhov 
Cc: Éric Piel 
Signed-off-by: Greg Kroah-Hartman

Driver core: fix driver_register() return value

2009-10-30T21:59:51+00:00

In this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=16dc42e018c2868211b4928f20a957c0c216126c
the check was added for another driver to already claim the same device
on the same bus. But the returned error code was wrong: to modprobe, the
-EEXIST means that _this_ driver is already installed. It therefore
doesn't produce the needed error message when _another_ driver is trying
to register for the same device.  Returning -EBUSY fixes the problem.

Signed-off-by: Stas Sergeev 
Cc: stable 
Signed-off-by: Greg Kroah-Hartman

mm: oom analysis: add shmem vmstat

2009-09-22T14:17:27+00:00

Recently we encountered OOM problems due to memory use of the GEM cache.
Generally a large amuont of Shmem/Tmpfs pages tend to create a memory
shortage problem.

We often use the following calculation to determine the amount of shmem
pages:

shmem = NR_ACTIVE_ANON + NR_INACTIVE_ANON - NR_ANON_PAGES

however the expression does not consider isolated and mlocked pages.

This patch adds explicit accounting for pages used by shmem and tmpfs.

Signed-off-by: KOSAKI Motohiro 
Acked-by: Rik van Riel 
Reviewed-by: Christoph Lameter 
Acked-by: Wu Fengguang 
Cc: David Rientjes 
Cc: Hugh Dickins 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mm: oom analysis: Show kernel stack usage in /proc/meminfo and OOM log output

2009-09-22T14:17:27+00:00

The amount of memory allocated to kernel stacks can become significant and
cause OOM conditions.  However, we do not display the amount of memory
consumed by stacks.

Add code to display the amount of memory used for stacks in /proc/meminfo.

Signed-off-by: KOSAKI Motohiro 
Reviewed-by: Christoph Lameter 
Reviewed-by: Minchan Kim 
Reviewed-by: Rik van Riel 
Cc: David Rientjes 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Driver-Core: extend devnode callbacks to provide permissions

2009-09-19T19:50:38+00:00

This allows subsytems to provide devtmpfs with non-default permissions
for the device node. Instead of the default mode of 0600, null, zero,
random, urandom, full, tty, ptmx now have a mode of 0666, which allows
non-privileged processes to access standard device nodes in case no
other userspace process applies the expected permissions.

This also fixes a wrong assignment in pktcdvd and a checkpatch.pl complain.

Signed-off-by: Kay Sievers 
Signed-off-by: Greg Kroah-Hartman

Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev

2009-09-15T16:50:49+00:00

Devtmpfs lets the kernel create a tmpfs instance called devtmpfs
very early at kernel initialization, before any driver-core device
is registered. Every device with a major/minor will provide a
device node in devtmpfs.

Devtmpfs can be changed and altered by userspace at any time,
and in any way needed - just like today's udev-mounted tmpfs.
Unmodified udev versions will run just fine on top of it, and will
recognize an already existing kernel-created device node and use it.
The default node permissions are root:root 0600. Proper permissions
and user/group ownership, meaningful symlinks, all other policy still
needs to be applied by userspace.

If a node is created by devtmps, devtmpfs will remove the device node
when the device goes away. If the device node was created by
userspace, or the devtmpfs created node was replaced by userspace, it
will no longer be removed by devtmpfs.

If it is requested to auto-mount it, it makes init=/bin/sh work
without any further userspace support. /dev will be fully populated
and dynamic, and always reflect the current device state of the kernel.
With the commonly used dynamic device numbers, it solves the problem
where static devices nodes may point to the wrong devices.

It is intended to make the initial bootup logic simpler and more robust,
by de-coupling the creation of the inital environment, to reliably run
userspace processes, from a complex userspace bootstrap logic to provide
a working /dev.

Signed-off-by: Kay Sievers 
Signed-off-by: Jan Blunck 
Tested-By: Harald Hoyer 
Tested-By: Scott James Remnant 
Signed-off-by: Greg Kroah-Hartman

driver core: platform_device_add_data(): use kmemdup()

2009-09-15T16:50:48+00:00

Instead of open-coding it.

Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman