On Thursday 2012-08-30 18:57, Andy Lutomirski wrote:
On Thu, Aug 30, 2012 at 9:14 AM, Jan Engelhardt jeng...@inai.de wrote:
On Thursday 2012-08-30 06:38, Andy Lutomirski wrote:
One of my disks went out to lunch for a while. Logs below.
[784786.047673] ata4.00: exception Emask 0x10 SAct 0x7800
From: Joe Perches j...@perches.com
Date: Sun, 26 Aug 2012 04:25:25 -0700
The recent commit to fix dynamic_debug was a bit unclean.
Neaten the style for dynamic_debug.
Reduce the stack use of message logging that uses netdev_printk
Add utility functions dev_printk_emit and dev_vprintk_emit for
On Wed, Aug 29, 2012 at 02:49:34PM -0700, Stephen Warren wrote:
On 08/28/12 13:35, Mark Brown wrote:
@@ -674,6 +676,7 @@ config ARCH_TEGRA
select GENERIC_CLOCKEVENTS
select GENERIC_GPIO
select HAVE_CLK
+select HAVE_CUSTOM_CLK
For 3.7, Tegra will switch to the common
Irina Tirdea irina.tir...@gmail.com writes:
Hi,
This is a set of patches to port perf to Android.
My approach is to include missing functions in Android (like getline,
getsid, etc). I am currently working on upstreaming these to Google.
With the missing functionality added to bionic, this
On 08/30/2012 02:30 AM, Jeremy Kerr wrote:
From: Matthew Garrett m...@redhat.com
The existing EFI variables code only supports variables of up to 1024
bytes. This limitation existed in version 0.99 of the EFI specification,
but was removed before any full releases. Since variables can now be
alloc_uprobe() might return a NULL pointer, put_uprobe() can't deal with
this.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
kernel/events/uprobes.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
On Sun, Aug 26, 2012 at 5:25 AM, Joe Perches j...@perches.com wrote:
The recent commit to fix dynamic_debug was a bit unclean.
Neaten the style for dynamic_debug.
Reduce the stack use of message logging that uses netdev_printk
Add utility functions dev_printk_emit and dev_vprintk_emit for
On Thu, Aug 30, 2012 at 09:38:41AM -0500, Kent Yoder wrote:
acpi_os_map_memory expects its return value to be in the __iomem address
space. Cast it back later when used in a memcpy to avoid the same sparse
warning there.
Signed-off-by: Kent Yoder k...@linux.vnet.ibm.com
I can't download
On Wed, Aug 29, 2012 at 03:50:00PM +0100, Krystian Garbaciak wrote:
Because, for some regulators, this is required: val += fvol-offset,
I was only able to reduce it to the following form.
What on earth makes you say this? The above is obviously linear.
Besides, you're missing several points
As a result of the election at Bali Hai, The five new members of the TAB
elected to two year terms are:
Chris Mason chris.ma...@fusionio.com
James Bottomley james.bottom...@hansenpartnership.com
John W. Linville linvi...@tuxdriver.com
Ric Wheeler ricwhee...@gmail.com
Jesse Barnes
Hi Hans and Prabhakar,
Hans Verkuil wrote:
Hi Prabhakar!
I've got some documentation review comments below...
On Thu August 30 2012 00:58:16 Prabhakar Lad wrote:
From: Lad, Prabhakar prabhakar@ti.com
add V4L2_CID_DPCM_PREDICTOR control of type menu, which
determines the dpcm predictor.
On Wed, Aug 29, 2012 at 04:58:45PM -0500, Seth Jennings wrote:
This patch fixes a race condition that results in memory
corruption when using cleancache.
The race exists between the zcache shrinker handler,
shrink_zcache_memory() and cleancache_get_page().
In most cases, the shrinker will
On Thu, Aug 30, 2012 at 6:12 AM, Eric Dumazet eric.duma...@gmail.com wrote:
On Wed, 2012-08-29 at 10:25 -0700, H.K. Jerry Chu wrote:
But it probably matter slightly more for TCP Fast Open (the server
side patch has
been completed and will be posted soon, after I finish breaking it up
into
On Thu, Aug 30, 2012 at 9:45 AM, David Miller da...@davemloft.net wrote:
From: Eric Dumazet eric.duma...@gmail.com
Date: Thu, 30 Aug 2012 06:12:30 -0700
On Wed, 2012-08-29 at 10:25 -0700, H.K. Jerry Chu wrote:
But it probably matter slightly more for TCP Fast Open (the server
side patch has
On Thu, Aug 30, 2012 at 05:03:35PM +0800, Xiaofan Tian wrote:
Currently, regmap will write 1 to mask_base to mask
an interrupt and write 0 to unmask it.
Applied, thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Hello!
This patch series contains additional improvements to latency for
large systems (beyond those in 3.6), along with improvements to
synchronize_rcu_expedited(). It also fixes one race introduced by the
latency improvements and another that was there to start with (but made
more probable by
From: Dimitri Sivanich sivan...@sgi.com
The fields in the rcu_state structure that are protected by the
root rcu_node structure's -lock can share a cache line with the
fields protected by -onofflock. This can result in excessive
memory contention on large systems, so this commit applies
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Before grace-period initialization was moved to a kthread, the CPU
invoking this code would have at least one callback that needed
a grace period, often a newly registered callback. However, moving
grace-period initialization means that the CPU
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Large systems running RCU_FAST_NO_HZ kernels see extreme memory
contention on the rcu_state structure's -fqslock field. This
can be avoided by disabling RCU_FAST_NO_HZ, either at compile time
or at boot time (via the nohz kernel boot parameter),
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Moving the RCU grace-period processing to a kthread and adjusting the
tracing resulted in two of the rcu_state structure's fields being unused.
This commit therefore removes them.
Signed-off-by: Paul E. McKenney paul...@linux.vnet.ibm.com
---
From: Paul E. McKenney paul.mcken...@linaro.org
In kernels built with CONFIG_RCU_FAST_NO_HZ=y, CPUs can accumulate a
large number of lazy callbacks, which as the name implies will be slow
to be invoked. This can be a problem on small-memory systems, where the
default 6-second sleep for CPUs
From: Paul E. McKenney paul...@linux.vnet.ibm.com
RCU grace-period cleanup is currently carried out with interrupts
disabled, which can result in excessive latency spikes on large systems
(many hundreds or thousands of CPUs). This patch therefore makes the
RCU grace-period cleanup be
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The synchronize_rcu_expedited() function disables interrupts across a
scan of all leaf rcu_node structures, which is not good for real-time
scheduling latency on large systems (hundreds or especially thousands
of CPUs). This commit therefore
From: Paul E. McKenney paul.mcken...@linaro.org
The current quiescent-state detection algorithm is needlessly
complex. It records the grace-period number corresponding to
the quiescent state at the time of the quiescent state, which
works, but it seems better to simply erase any record of
From: Paul E. McKenney paul.mcken...@linaro.org
In the C language, signed overflow is undefined. It is true that
twos-complement arithmetic normally comes to the rescue, but if the
compiler can subvert this any time it has any information about the values
being compared. For example, given if
From: Paul E. McKenney paul...@linux.vnet.ibm.com
As the first step towards allowing quiescent-state forcing to be
preemptible, this commit moves RCU quiescent-state forcing into the
same kthread that is now used to initialize and clean up after grace
periods. This is yet another step towards
From: Paul E. McKenney paul...@linux.vnet.ibm.com
RCU grace-period initialization is currently carried out with interrupts
disabled, which can result in 200-microsecond latency spikes on systems
on which RCU has been configured for 4096 CPUs. This patch therefore
makes the RCU grace-period
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The current approach to grace-period initialization is vulnerable to
extremely low-probabity races. These races stem fro the fact that the
old grace period is marked completed on the same traversal through the
rcu_node structure that is marking
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The module parameters blimit, qhimark, and qlomark (and more
recently, rcu_fanout_leaf) have permission masks of zero, so
that their values are not visible from sysfs. This is unnecessary
and inconvenient to administrators who might like an easy
From: Paul E. McKenney paul...@linux.vnet.ibm.com
There are some additional potential grace-period initialization races
on systems with more than one rcu_node structure, for example:
1. CPU 0 completes a grace period, but needs an additional
grace period, so starts initializing one,
From: Paul E. McKenney paul.mcken...@linaro.org
Earlier versions of RCU invoked the RCU core from the CPU_DYING notifier
in order to note a quiescent state for the outgoing CPU. Because the
CPU is marked offline during the execution of the CPU_DYING notifiers,
the RCU core had to tolerate being
From: Paul E. McKenney paul...@linux.vnet.ibm.com
As the first step towards allowing grace-period initialization to be
preemptible, this commit moves the RCU grace-period initialization
into its own kthread. This is needed to keep large-system scheduling
latency at reasonable levels.
From: Paul E. McKenney paul...@linux.vnet.ibm.com
As a first step towards allowing grace-period cleanup to be preemptible,
this commit moves the RCU grace-period cleanup into the same kthread
that is now used to initialize grace periods. This is needed to keep
scheduling latency down to a dull
From: Paul E. McKenney paul.mcken...@linaro.org
Some uses of RCU benefit from shorter grace periods, while others benefit
more from the greater efficiency provided by longer grace periods.
Therefore, this commit allows the durations to be controlled from sysfs.
There are two sysfs parameters, one
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Now that the rcu_node structures' -completed fields are unconditionally
assigned at grace-period cleanup time, they should already have the
correct value for the new grace period at grace-period initialization
time. This commit therefore inserts
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Moving quiescent-state forcing into a kthread dispenses with the need
for the -n_rp_need_fqs field, so this commit removes it.
Signed-off-by: Paul E. McKenney paul...@linux.vnet.ibm.com
---
Documentation/RCU/trace.txt | 43
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Then rcu_gp_kthread() function is too large and furthermore needs to
have the force_quiescent_state() code pulled in. This commit therefore
breaks up rcu_gp_kthread() into rcu_gp_init() and rcu_gp_cleanup().
Signed-off-by: Paul E. McKenney
From: Paul E. McKenney paul...@linux.vnet.ibm.com
RCU quiescent-state forcing is currently carried out without preemption
points, which can result in excessive latency spikes on large systems
(many hundreds or thousands of CPUs). This patch therefore inserts
a voluntary preemption point into
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Now the the grace-period initialization procedure is preemptible, it is
subject to the following race on systems whose rcu_node tree contains
more than one node:
1. CPU 31 starts initializing the grace period, including the
first
2012/8/29 Laxman Dewangan ldewan...@nvidia.com:
@@ -3614,8 +3615,11 @@ static int __init regulator_init_complete(void)
mutex_lock(rdev-mutex);
- if (rdev-use_count)
+ if (rdev-use_count) {
+ if (rdev-supply c-boot_on)
+
Dear RT Folks,
I'm pleased to announce the 3.0.41-rt62 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
Head SHA1: 27770766f5425b466d3a61025350f9829840e5e9
Or to build 3.0.41-rt62 directly, the following
On Thu, 2012-08-30 at 11:43 -0600, Jim Cromie wrote:
On Sun, Aug 26, 2012 at 5:25 AM, Joe Perches j...@perches.com wrote:
The recent commit to fix dynamic_debug was a bit unclean.
Neaten the style for dynamic_debug.
Reduce the stack use of message logging that uses netdev_printk
Add
These set of patches make possible the remoteproc recover after a crash.
This is a hard recovery, that means the remoteproc is reset and it will
start from the beginning. When a crash happen all the virtio devices are
destroyed. Therefore, both rpmsg drivers and devices are gracefully
removed
This patch is exporting the rproc_report_crash function which can be used
to report a rproc crash to the remoteproc core. This function is specially
thought to be called by low-level remoteproc driver code in case of
detecting a crash (remoteproc is not functional anymore). Using this
function
Add a debugfs entry (named recovery) so that recovery can be disabled
dynamically at runtime. This entry is very useful when you are trying to
debug a rproc crash. Without this a recovery will take place making
impossible to debug the issue.
Original idea from Ohad Ben-Cohen and contributions
On 08/30/2012 10:32 AM, Murali Karicheri wrote:
This adds devres version of the of_iomap() to allow resource to be cleaned
through devres.
If you have a struct device, then don't you already have a resource and
can just use devm_ioremap in a driver? New drivers should not be using
of_iomap.
This patch is introducing rproc_trigger_recover function which is in
charge of recovering the rproc. One way to recover the rproc after a crash
is resetting all its virtio devices. Doing that, all rpmsg drivers are
restored along with the rpmsg devices and that also causes the reset of
the
On Thu, Aug 30, 2012 at 08:24:15PM +0200, Rabin Vincent wrote:
This does not handle the case where a regulator is not set boot_on but
is considered on (for example, because of the lack of an is_enabled
callback), and is later actually enabled by a consumer before
regulator_init_complete().
- After a little bit a playing with some surfaces, I can confuse the
input_mt_assign_slot_by_id function: for the very same contact id, I
got up to four different slots This accumulates the clicks and is
not very good :-(
Reading again, the input-mt match-by-id code does not do
The MCI makes use of the dw_dmac driver when DMA is being used.
Due to recent changes the driver was broken because:
- the SMS field in the CTLL register received the wrong value 0
- a patch in dw_dmac (http://lkml.org/lkml/2012/1/18/52)
allowed for 64-bit transfers on the memory side, giving an
In addition to Andrew's comment about making the stats struct and
functions generic...
On 8/27/12 3:51 AM, Dong Hao wrote:
---8---
+static void exit_event_decode_key(struct event_key *key, char decode[20])
+{
+ const char *exit_reason = get_exit_reason(key-key);
+
+
The dw_dmac was originally developed for avr32 to be used with the
Synopsys DesignWare AHB DMA controller. After 2.6.38, device access was done
with the little-endian readl/writel functions. This didn't work on the
avr32 platform, because it needs native-endian (i.e. big-endian) accessors.
This
The dw_dmac driver was earlier adapted to do 64-bit transfers
on the memory side (https://lkml.org/lkml/2012/1/18/52)
This works on ARM platforms but for AVR32 (AP700x) the maximum
allowed transfer size is 32-bits.
This patch allows the arch to set a new slave property
max_mem_width to limit the
After some recent changes to dw_dmac, the driver got broken
for the AVR32 platform for two reasons:
The accessors to i/o memory had become little-endian.
The maximum transfer width on the memory side was increased
from 32 to 64 bits. This led to undefined behavior on the
avr32 platform.
These
The MAX197 is an A/D converter, made by Maxim. This driver currently
supports the MAX197, and MAX199. They are both 8-Channel, Multi-Range,
5V, 12-Bit DAS with 8+4 Bus Interface and Fault Protection.
The available ranges for the MAX197 are {0,-5V} to 5V, and {0,-10V} to
10V, while they are
Thanks for the reply, Hans. Your question about opening /dev/uio0 O_RDWR
prompted me to check out how I was creating /dev/uio0 ... my system
isn't using udev, and I was accidentally creating it with major/minor
number 254/0 instead of the correct 253/0 (found by looking at
/proc/devices). Fixed
Hello!
This series covers changes to rcutorture and documentation updates.
The individual patches in this series are as follows:
1. Update rcutorture default values so that casual rcutorture
users will do more aggressive testing.
2. Make rcutorture track CPU-hotplug latency
From: Paul E. McKenney paul.mcken...@linaro.org
A number of new features have been added to rcutorture over the years, but
the defaults have not been updated to include them. This commit therefore
turns on a couple of them that have proven helpful and trustworthy, namely
periodic progress
From: Paul E. McKenney paul.mcken...@linaro.org
Many rcutorture runs include CPU-hotplug operations in their stress
testing. This commit accumulates statistics on the durations of these
operations in deference to the recent concern about the overhead and
latency of these operations.
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Drop a few characters by switching kernel/rcutorture.c from
printk(KERN_ALERT to pr_alert(.
Signed-off-by: Paul E. McKenney paul...@linux.vnet.ibm.com
---
kernel/rcutorture.c | 100 +-
1 files
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The current documentation did not help someone grepping for SRCU to
learn that disabling preemption is not a replacement for srcu_read_lock(),
so upgrade the documentation to bring this out, not just for SRCU,
but also for RCU-bh. Also document
From: Paul E. McKenney paul...@linux.vnet.ibm.com
When you do something like t = kthread_run(...), it is possible that
the kthread will start running before the assignment to t happens.
If the child kthread expects to find a pointer to its task_struct in t,
it will then be fatally disappointed.
On Thu, Aug 30, 2012 at 11:44:48AM -0700, Paul E. McKenney wrote:
Hello!
This series covers changes to rcutorture and documentation updates.
The individual patches in this series are as follows:
1.Update rcutorture default values so that casual rcutorture
users will do more
Hello!
This series contains miscellaneous fixes. The individual fixes are as
follows:
1. Add PROVE_RCU_DELAY Kconfig parameter to add delays as needed to
provoke difficult races.
2. Pull TINY_RCU dyntick-idle tracing into non-idle region.
3. Properly initialize
On Thu, Aug 30, 2012 at 11:45:08AM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul.mcken...@linaro.org
A number of new features have been added to rcutorture over the years, but
the defaults have not been updated to include them. This commit therefore
turns on a couple of them
On Thursday 30 August 2012 20:18:41 SeungGoo, Kim wrote:
@@ -748,8 +752,9 @@ int usbnet_open (struct net_device *net)
goto done_nopm;
}
- // put into known safe state
- if (info-reset (retval = info-reset (dev)) 0) {
+ /* put into known safe
On 8/29/2012 4:53 PM, Russell King - ARM Linux wrote:
On Tue, Aug 21, 2012 at 09:03:49PM -0700, Stephen Boyd wrote:
Nothing stops a process from hotplugging in a CPU concurrently
with a sys_reboot() call. In such a situation we could have
ipi_cpu_stop() mark a cpu as 'offline' and _cpu_up()
On Thu, Aug 30, 2012 at 06:36:53PM +, Worth, Kevin wrote:
Thanks for the reply, Hans. Your question about opening /dev/uio0 O_RDWR
prompted me to check out how I was creating /dev/uio0 ... my system
isn't using udev, and I was accidentally creating it with major/minor
number 254/0 instead
On Thu, Aug 30, 2012 at 11:45:09AM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul.mcken...@linaro.org
Many rcutorture runs include CPU-hotplug operations in their stress
testing. This commit accumulates statistics on the durations of these
operations in deference to the recent
On Thu, Aug 30, 2012 at 11:45:10AM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The current documentation did not help someone grepping for SRCU to
learn that disabling preemption is not a replacement for srcu_read_lock(),
so upgrade the documentation to
From: Peter Zijlstra pet...@infradead.org
Rabik and Paul reported two different issues related to the same few
lines of code.
Rabik's issue is that the nr_uninterruptible migration code is wrong in
that he sees artifacts due to this (Rabik please do expand in more
detail).
Paul's issue is that
From: Paul E. McKenney paul.mcken...@linaro.org
Posting a callback after the CPU_DEAD notifier effectively leaks
that callback unless/until that CPU comes back online. Silence is
unhelpful when attempting to track down such leaks, so this commit emits
a WARN_ON_ONCE() and unconditionally leaks
From: Paul E. McKenney paul.mcken...@linaro.org
Currently, _rcu_barrier() relies on preempt_disable() to prevent
any CPU from going offline, which in turn depends on CPU hotplug's
use of __stop_machine().
This patch therefore makes _rcu_barrier() use get_online_cpus() to
block CPU-hotplug
* Tony Lindgren t...@atomide.com [120824 13:37]:
* Arnd Bergmann a...@arndb.de [120823 10:27]:
On Thursday 23 August 2012, Arnd Bergmann wrote:
On Wednesday 22 August 2012, Russell King - ARM Linux wrote:
In any case, what we should be doing here as well is moving the headers
On Thu, Aug 30, 2012 at 11:45:11AM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Drop a few characters by switching kernel/rcutorture.c from
printk(KERN_ALERT to pr_alert(.
Signed-off-by: Paul E. McKenney paul...@linux.vnet.ibm.com
How about setting
On Sat, 25 Aug 2012 17:47:50 +0800
Gavin Shan sha...@linux.vnet.ibm.com wrote:
--- a/mm/mmu_notifier.c
+++ b/mm/mmu_notifier.c
@@ -192,22 +192,23 @@ static int do_mmu_notifier_register(struct
mmu_notifier *mn,
BUG_ON(atomic_read(mm-mm_users) = 0);
- ret = -ENOMEM;
-
On Thu, Aug 30, 2012 at 11:45:12AM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
When you do something like t = kthread_run(...), it is possible that
the kthread will start running before the assignment to t happens.
If the child kthread expects to find a
On Thu, Aug 30, 2012 at 10:45:56AM -0700, Dan Carpenter wrote:
On Thu, Aug 30, 2012 at 09:38:41AM -0500, Kent Yoder wrote:
acpi_os_map_memory expects its return value to be in the __iomem address
space. Cast it back later when used in a memcpy to avoid the same sparse
warning there.
Around Fri 31 Aug 2012 01:07:13 +0800 or thereabout, Hein Tibosch wrote:
The MCI makes use of the dw_dmac driver when DMA is being used.
Due to recent changes the driver was broken because:
- the SMS field in the CTLL register received the wrong value 0
- a patch in dw_dmac
On 08/30/2012 08:38 AM, Patil, Rachna wrote:
This patch adds support for TI's ADC driver.
This is a multifunctional device.
Analog input lines are provided on which
voltage measurements can be carried out.
You can have upto 8 input lines.
Nice concise driver.
A few comments and questions
On Tue, Aug 28, 2012 at 11:59:58AM -0700, David Brown wrote:
'make dtbs' in a clean tree will try running the dtc before actually
building it. Make these rules depend upon the scripts to build it.
David,
Could you please send this into rmk's queue? [1] This fix has been
cropping up by
On Wed, 29 Aug 2012 17:32:57 +0200
Gerald Schaefer gerald.schae...@de.ibm.com wrote:
This patch series adds support for transparent hugepages on System z.
Small changes to common code are necessary with regard to a different
pgtable_t, tlb flushing and kvm behaviour on s390, see patches 1 to
On Thursday 30 August 2012, Hein Tibosch wrote:
The dw_dmac was originally developed for avr32 to be used with the
Synopsys DesignWare AHB DMA controller. After 2.6.38, device access was done
with the little-endian readl/writel functions. This didn't work on the
avr32 platform, because it
On Thu, Aug 30, 2012 at 02:39:55PM -0400, Vivien Didelot wrote:
The MAX197 is an A/D converter, made by Maxim. This driver currently
supports the MAX197, and MAX199. They are both 8-Channel, Multi-Range,
5V, 12-Bit DAS with 8+4 Bus Interface and Fault Protection.
The available ranges for the
Thanks for the reply, Hans. Your question about opening /dev/uio0 O_RDWR
prompted me to check out how I was creating /dev/uio0 ... my system
isn't using udev, and I was accidentally creating it with major/minor
number 254/0 instead of the correct 253/0 (found by looking at
/proc/devices).
Submitted. Thanks.
Murali Karicheri
Software Design Engineer
-Original Message-
From: Nicolas Pitre [mailto:nicolas.pi...@linaro.org]
Sent: Thursday, August 30, 2012 11:59 AM
To: Karicheri, Muralidharan
Cc: Russell King - ARM Linux; t...@atomide.com; Shilimkar, Santosh;
This patchset updates the ACPI system-level (ex. hotplug)
notify handling with a new .sys_notify interface. It provides
the following changes:
- Allow ACPI drivers to register their system (hotplug) notify
handlers to a new .sys_notify interface in their acpi_driver
table. This removes
Added acpi_lookup_driver(), which looks up an associated driver
for the notified ACPI device object by walking through the list
of ACPI drivers.
Signed-off-by: Toshi Kani toshi.k...@hp.com
---
drivers/acpi/scan.c | 65 +++
include/acpi/acpi_bus.h
Added a new .sys_notify interface, which allows ACPI drivers to
register their system-level (ex. hotplug) notify handlers in their
acpi_driver table. The global notify handler acpi_bus_notify()
is called for all system-level ACPI notification, which is changed
to call an appropriate driver's
Changed the ACPI processor driver to use .sys_notify. Removed
ACPI namespace walks and their call-back function that register
and unregister the hotplug handler to all processor objects
through acpi_[install|remove]_notify_handler().
Signed-off-by: Toshi Kani toshi.k...@hp.com
---
Changed the ACPI container driver to use .sys_notify. Removed
ACPI namespace walks and their call-back function that register
and unregister the hotplug handler to all container objects
through acpi_[install|remove]_notify_handler().
Signed-off-by: Toshi Kani toshi.k...@hp.com
---
Changed the ACPI memory hotplug driver to use .sys_notify. Removed
ACPI namespace walks and their call-back functions that register and
unregister the hotplug handler to all memory device objects through
acpi_[install|remove]_notify_handler().
Signed-off-by: Toshi Kani toshi.k...@hp.com
---
On Wed, Aug 29, 2012 at 10:10:10AM -0400, Namjae Jeon wrote:
This commit adds FILEID_INVALID = 0xff in fid_type to
indicate invalid fid_type
OK, applying for 3.7.
Looks like this shows up in a lot of filesystems too as just 255. Are
you planning to patch up the filesystems afterwards?
--b.
On Wed, Aug 29, 2012 at 10:10:53AM -0400, Namjae Jeon wrote:
remove duplicate init in nfsd4_cb_recall
Thanks, applying for 3.7.--b.
Signed-off-by: Namjae Jeon linkinj...@gmail.com
Signed-off-by: Vivek Trivedi vtrivedi...@gmail.com
---
fs/nfsd/nfs4callback.c |1 -
1 file changed, 1
On 08/29/2012 05:49 PM, Oleg Nesterov wrote:
That would help but would require a change in ptrace_attach() or
something in gdb/strace/…
Well, I still think you should not touch ptrace_attach() at all.
Okay.
One thing I just noticed: If I don't register a handler for SIGUSR1 and
send one to
On Thu, Aug 30, 2012 at 12:00:18PM -0700, Josh Triplett wrote:
On Thu, Aug 30, 2012 at 11:45:09AM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul.mcken...@linaro.org
Many rcutorture runs include CPU-hotplug operations in their stress
testing. This commit accumulates
Dear RT Folks,
I'm pleased to announce the 3.0.42-rt63 stable release.
This release is just an update to the new stable 3.0.42 version
and no RT specific changes have been made.
You can get this release via the git tree at:
On Thu, Aug 30, 2012 at 09:38:08AM -0700, George Zhang wrote:
+/* VMCICptBufInfo: Used to set/get current context's checkpoint state. */
+struct vmci_ctx_chkpt_buf_info {
+ uint64_t cptBuf;
+ uint32_t cptType;
+ uint32_t bufSize;
+ int32_t result;
+ uint32_t
On Thu, Aug 30, 2012 at 09:40:34AM -0700, George Zhang wrote:
+struct vmci_device {
+ struct mutex lock; /* Device access mutex */
+
+ unsigned int ioaddr;
+ unsigned int ioaddr_size;
+ unsigned int irq;
+ unsigned int intr_type;
+ bool
On Thu, Aug 30, 2012 at 09:38:08AM -0700, George Zhang wrote:
Signed-off-by: George Zhang georgezh...@vmware.com
You seem to have forgotten to provide a valid changelog comment for this
patch, and all others in this series. Remember, your 00/11 email will
not be applied to the system, so
501 - 600 of 736 matches
Mail list logo
