PCI resets will attempt to take the device_lock for any device to be
reset. This is a problem if that lock is already held, for instance
in the device remove path. It's not sufficient to simply kill the
user process or skip the reset if called after .remove as a race could
result in the same
(2014/01/15 4:21), Prarit Bhargava wrote:
> When booting a kexec/kdump kernel on a system that has specific memory hotplug
> regions the boot will fail with warnings like:
>
> [2.939467] swapper/0: page allocation failure: order:9, mode:0x84d0
> [2.946564] CPU: 0 PID: 1 Comm: swapper/0
On 14/01/14, William Roberts wrote:
> The race was non existent. I had the VMA locked. I switched to this to keep
> the code that gets the cmdline value almost unchanged to try and reduce
> bugs. I can still author a patch on top of this later to optimize. However
> the buffer is smaller. Before
On Mon, Jan 06, 2014 at 01:33:53PM -0600, Tom Lendacky wrote:
> The following series implements a fix to hash length wrapping as well
> as some additional fixes and cleanups (proper gfp_t type on some memory
> allocations, scatterlist usage improvements, null request result field
> checks and
On 01/14/2014 05:52 PM, Michael S. Tsirkin wrote:
> On Tue, Jan 14, 2014 at 04:45:24PM +0800, Jason Wang wrote:
>> > On 01/14/2014 04:25 PM, Michael S. Tsirkin wrote:
>>> > > On Tue, Jan 14, 2014 at 02:53:07PM +0800, Jason Wang wrote:
> >> We used to limit the number of packets queued through
On Tue, 2014-01-14 at 16:48 -0700, Bjorn Helgaas wrote:
> On Mon, Dec 16, 2013 at 3:16 PM, Alex Williamson
> wrote:
> > PCI resets will attempt to take the device_lock for any device to be
> > reset. This is a problem if that lock is already held, for instance
> > in the device remove path.
On Mon, 6 Jan 2014, Davidlohr Bueso wrote:
> > If Andrew agree, It would be great to merge 1-7 patches into mainline
> > before your mutex approach. There are some of clean-up patches and, IMO,
> > it makes the code more readable and maintainable, so it is worth to merge
> > separately.
>
> Fine
On 01/15/2014 07:44 AM, Paul E. McKenney wrote:
On Tue, Jan 14, 2014 at 10:01:04AM -0800, Richard Henderson wrote:
On 01/14/2014 09:08 AM, Matt Turner wrote:
On Tue, Jan 14, 2014 at 3:03 AM, Peter Zijlstra wrote:
On Tue, Jan 14, 2014 at 10:28:23AM +0800, Daniel J Blueman wrote:
Peter,
I
On Wed, 2014-01-15 at 00:52 -0200, Fabio Estevam wrote:
> Fix the following checkpatch error and warning:
While you're at it:
> diff --git a/drivers/regulator/pfuze100-regulator.c
> b/drivers/regulator/pfuze100-regulator.c
[]
> @@ -309,14 +309,17 @@ static int pfuze_identify(struct pfuze_chip
On 01/15/2014 03:16 AM, Johannes Weiner wrote:
> On Tue, Jan 14, 2014 at 09:01:09AM +0800, Bob Liu wrote:
>> Hi Johannes,
>>
>> On 01/11/2014 02:10 AM, Johannes Weiner wrote:
>>> The VM maintains cached filesystem pages on two types of lists. One
>>> list holds the pages recently faulted into
On Wed, 15 Jan 2014 11:49:28 +0900
Namhyung Kim wrote:
> Hi Steve,
>
> On Tue, 14 Jan 2014 21:00:58 -0500, Steven Rostedt wrote:
> > On Wed, 15 Jan 2014 10:45:24 +0900
> > Namhyung Kim wrote:
> >
> >>
> >> @@ -32,8 +33,9 @@
> >> #define TRACE_SEQ_POISON ((void *)0xdeadbeef)
> >> #define
From: Ying Xue
Date: Wed, 15 Jan 2014 10:23:35 +0800
> Under rtnl_lock protection, we should use __dev_get_name/index()
> rather than dev_get_name()/index() to find interface handlers
> because the former interfaces can help us avoid to change interface
> reference counter.
>
> v2 changes:
> -
From: Fabio Estevam
Fix the following checkpatch error and warning:
ERROR: switch and case should be at the same indent
#311: FILE: drivers/regulator/pfuze100-regulator.c:311:
+ switch (value & 0x0f) {
[...]
+ case 0x8:
[...]
+ case 0x0:
[...]
+
On 01/14/2014 06:25 PM, Borislav Petkov wrote:
> On Tue, Jan 14, 2014 at 02:45:37PM -0800, Eric Dumazet wrote:
>> Even on a Jaguar, the proposed alternative
> I don't know what Jaguar you guys are talking about but the Jaguar
> I know - Fam16h - has an int hardware divider:
>
>
From: Hayes Wang
Date: Wed, 15 Jan 2014 10:42:13 +0800
> Remove the limitation between ecm mode and vendor mode.
>
> v2: replace the patch #3 with "ecm and vendor modes coexist".
This looks better, series, applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe
Hi Steve,
On Tue, 14 Jan 2014 21:00:58 -0500, Steven Rostedt wrote:
> On Wed, 15 Jan 2014 10:45:24 +0900
> Namhyung Kim wrote:
>
>>
>> @@ -32,8 +33,9 @@
>> #define TRACE_SEQ_POISON((void *)0xdeadbeef)
>> #define TRACE_SEQ_CHECK(s) \
>> do {
On Tue, 14 Jan 2014, Dave Hansen wrote:
> diff -puN include/linux/mm.h~slub-reset-page-at-free include/linux/mm.h
> --- a/include/linux/mm.h~slub-reset-page-at-free 2014-01-14
> 09:57:57.099666808 -0800
> +++ b/include/linux/mm.h 2014-01-14 09:57:57.110667301 -0800
> @@ -2076,5
Hi all,
Today's linux-next merge of the infiniband tree got a conflict in
include/linux/mlx4/device.h between commit 7ffdf726cfe0 ("net/mlx4_core:
Add basic support for TCP/IP offloads under tunneling") from the net-next
tree and commits 4de658036086 ("mlx4_core: Add support for steerable IB
UD
On Tue, 14 Jan 2014, Dave Hansen wrote:
> >> page->pfmemalloc does not deserve a spot in 'struct page'. It is
> >> only used transiently _just_ after a page leaves the buddy
> >> allocator.
> >
> > Why would we need to do this if we are removing the cmpxchg_double?
>
> Why do we need the
Heinz points out that adding buffers to a broken virtqueue (which
should "never happen") still works. Failing allows drivers to detect
and complain about broken devices.
Now drivers are robust, we can add this extra check.
Reported-by: Heinz Graalfs
Signed-off-by: Rusty Russell
---
The r8152 could support RTL8153. Update the relative descriptor.
Signed-off-by: Hayes Wang
---
drivers/net/usb/Kconfig | 5 +++--
drivers/net/usb/r8152.c | 2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/net/usb/Kconfig b/drivers/net/usb/Kconfig
index
Andi Kleen writes:
>> Cc: Andi Kleen
>> Signed-off-by: Johannes Berg
>
> Acked-by: Andi Kleen
Thanks, applied.
I added:
Fixes: e0f244c63fc9 ("asmlinkage, module: Make ksymtab [...] __visible")
Cheers,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
A bad implementation of virtio might cause us to mark the virtqueue
broken: we'll dev_err() in that case, and the device is useless, but
let's not BUG_ON().
ENOMEM or ENOSPC implies the ring is full, and we should try again
later (-ENOMEM is documented to happen, but doesn't, as we fall
through
A bad implementation of virtio might cause us to mark the virtqueue
broken: we'll dev_err() in that case, and the device is useless, but
let's not BUG_ON().
Signed-off-by: Rusty Russell
---
drivers/net/virtio_net.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Good for post-apocalyptic scenarios, like S/390 hotplug.
Signed-off-by: Rusty Russell
---
drivers/virtio/virtio_ring.c | 15 +++
include/linux/virtio.h | 2 ++
2 files changed, 17 insertions(+)
diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
index
Remove the limitation between ecm mode and vendor mode.
v2: replace the patch #3 with "ecm and vendor modes coexist".
Hayes Wang (3):
r8152: change the descriptor
r8152: fix the warnings and a error from checkpatch.pl
r8152: ecm and vendor modes coexist
drivers/net/usb/Kconfig | 5
Fix the following warnings and error:
- WARNING: usb_free_urb(NULL) is safe this check is probably not required
- WARNING: kfree(NULL) is safe this check is probably not required
- ERROR: do not use C99 // comments
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 42
Remove the limitation that the ecm and r8152 drivers couldn't coexist.
- Remove the devices from the blacklist of relative drivers.
- Remove usb_driver_set_configuration() from r8152 driver.
- Modify the id_table of the r8152 driver for the vendor mode only.
Signed-off-by: Hayes Wang
---
A bad implementation of virtio might cause us to mark the virtqueue
broken: we'll dev_err() in that case, and the device is useless, but
let's not BUG().
Signed-off-by: Rusty Russell
---
drivers/char/hw_random/virtio-rng.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
A bad implementation of virtio might cause us to mark the virtqueue
broken: we'll dev_err() in that case, and the device is useless, but
let's not BUG().
Signed-off-by: Rusty Russell
---
drivers/virtio/virtio_balloon.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git
On Wed, Jan 15, 2014 at 07:25:04AM +0700, Linus Torvalds wrote:
> On Wed, Jan 15, 2014 at 6:44 AM, Paul E. McKenney
> wrote:
> >
> > Which means that Alpha should be able to similarly emulate 1-byte and
> > 2-byte atomics, correct?
>
> Not reasonably, no.
>
> The ldl/stc implementation on early
On Tue, 14 Jan 2014, Dave Hansen wrote:
> > On Tue, 14 Jan 2014, Dave Hansen wrote:
> >> I found this useful to have in my testing. I would like to have
> >> it available for a bit, at least until other folks have had a
> >> chance to do some testing with it.
> >
> > I dont really see the point
The mm-of-the-moment snapshot 2014-01-14-18-13 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On Tue, 14 Jan 2014, Dave Hansen wrote:
> diff -puN
> include/linux/mm_types.h~make-slab-use-page-lru-vs-list-consistently
> include/linux/mm_types.h
> --- a/include/linux/mm_types.h~make-slab-use-page-lru-vs-list-consistently
> 2014-01-14 09:57:56.099621967 -0800
> +++
On Wed, 15 Jan 2014 10:45:28 +0900
Namhyung Kim wrote:
> The PEVENT_PLUGIN_UNLOADER function might need some cleanup using
> pevent like unregister some handlers. So pass pevent as argument.
>
> Cc: Jiri Olsa
> Signed-off-by: Namhyung Kim
Acked-by: Steven Rostedt
> ---
>
The following call chain we can identify that dn_cache_getroute() is
protected under rtnl_lock. So if we use __dev_get_by_index() instead
of dev_get_by_index() to find interface handlers in it, this would help
us avoid to change interface reference counter.
rtnetlink_rcv()
rtnl_lock()
As cgw_create_job() is always under rtnl_lock protection,
__dev_get_by_index() instead of dev_get_by_index() should be used to
find interface handler in it having us avoid to change interface
reference counter.
Cc: Oliver Hartkopp
Signed-off-by: Ying Xue
Acked-by: Oliver Hartkopp
---
The following call chain denotes that both do_reset() and do_del_chan()
are protected under rtnl_lock. If we use __dev_get_by_name() instead of
dev_get_by_name() to find interface handlers in them, this would help
us avoid to change interface reference counter.
dev_ioctl()
rtnl_lock()
The following call chains indicate that chnl_net_open() is under
rtnl_lock protection as __dev_open() is protected by rtnl_lock.
So if __dev_get_by_index() instead of dev_get_by_index() is used
to find interface handler in it, this would help us avoid to change
interface reference counter.
The following call chain indicates that eql_ioctl(), eql_enslave(),
eql_emancipate(), eql_g_slave_cfg() and eql_s_slave_cfg() are
protected under rtnl_lock. So if we use __dev_get_by_name() instead
of dev_get_by_name() to find interface handlers in them, this would
help us avoid to change
The following call chain indicates that bond_do_ioctl() is protected
under rtnl_lock. If we use __dev_get_by_name() instead of
dev_get_by_name() to find interface handler in it, this would
help us avoid to change reference counter of interface once.
dev_ioctl()
rtnl_lock()
dev_ifsioc()
The following call chains indicate that vxlan_fdb_parse() is
under rtnl_lock protection. So if we use __dev_get_by_index()
instead of dev_get_by_index() to find interface handler in it,
this would help us avoid to change interface reference counter.
rtnetlink_rcv()
rtnl_lock()
The following call chains indicate that batadv_is_on_batman_iface()
is always under rtnl_lock protection as call_netdevice_notifier()
is protected by rtnl_lock. So if __dev_get_by_index() rather than
dev_get_by_index() is used to find interface handler in it, this
would help us avoid to change
The following call chain indicates that dcb_doit() is protected
under rtnl_lock. So if we use __dev_get_by_name() instead of
dev_get_by_name() to find interface handlers in it, this would
help us avoid to change interface reference counter.
rtnetlink_rcv()
rtnl_lock()
netlink_rcv_skb()
As __cfg80211_rdev_from_attrs(), nl80211_dump_wiphy_parse() and
nl80211_set_wiphy() are all under rtnl_lock protection,
__dev_get_by_index() instead of dev_get_by_index() should be used
to find interface handler in them allowing us to avoid to change
interface reference counter.
Cc: Johannes Berg
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
arch/mips/bcm47xx/setup.c between commits dc8db0fd9f9f ("MIPS: BCM47XX: Prepare
support for LEDs"), db780310ed48 ("MIPS: BCM47XX: Prepare support for GPIO
buttons") and 7fb942c59696 ("MIPS: BCM47XX: fix position of
Under rtnl_lock protection, we should use __dev_get_name/index()
rather than dev_get_name()/index() to find interface handlers
because the former interfaces can help us avoid to change interface
reference counter.
v2 changes:
- Change return value of nl80211_set_wiphy() to 0 in patch #10
by
On Tue, 14 Jan 2014 18:25:55 -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 14, 2014 at 01:07:00PM -0800, Andi Kleen escreveu:
>> Namhyung Kim writes:
>> >
>> > +--percentage::
>> > + Determine how to display the overhead percentage of filtered
>> > entries.
>>
>> This should describe
On Tue, Jan 14, 2014 at 5:47 PM, Roy Franz wrote:
> On Tue, Jan 14, 2014 at 1:05 AM, Ard Biesheuvel
> wrote:
>> On 10 January 2014 17:30, Roy Franz wrote:
>>> This patch adds EFI stub support for the ARM Linux kernel. The EFI stub
>>> operates similarly to the x86 stub: it is a shim between
Hello Sergey,
On Tue, Jan 14, 2014 at 02:27:23PM +0300, Sergey Senozhatsky wrote:
> Do not pass rw argument down the __zram_make_request() -> zram_bvec_rw()
> chain, decode it in zram_bvec_rw() instead. Besides, this is the place
> where we distinguish READ (+READ AHEAD) and WRITE bio data
On Wed, 15 Jan 2014 10:45:26 +0900
Namhyung Kim wrote:
> Use plain malloc() and check its return value.
>
> Signed-off-by: Namhyung Kim
Acked-by: Steven Rostedt
-- Steve
> ---
> tools/lib/traceevent/trace-seq.c | 7 +--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git
From: Martin Kaiser
Date: Tue, 14 Jan 2014 16:21:28 +0100
> re-sent as requested by David M.
Sorry, dianthong sent his version of the fix meanwhile and I applied
his copy.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, 15 Jan 2014 10:45:25 +0900
Namhyung Kim wrote:
> If realloc() fails, it'll leak the buffer. Also increate buffer size
> only if the allocation succeeded.
>
> Signed-off-by: Namhyung Kim
> ---
Acked-by: Steven Rostedt
-- Steve
--
To unsubscribe from this list: send the line
On 2014/1/14 23:05, Robert Richter wrote:
> On 14.01.14 09:52:11, Weng Meiling wrote:
>> On 2014/1/13 16:45, Robert Richter wrote:
>>> On 20.12.13 15:49:01, Weng Meiling wrote:
>
The problem was once triggered on kernel 2.6.34, the main information:
<3>BUG: soft lockup - CPU#0 stuck for
On Wed, 15 Jan 2014 10:45:24 +0900
Namhyung Kim wrote:
>
> @@ -32,8 +33,9 @@
> #define TRACE_SEQ_POISON ((void *)0xdeadbeef)
> #define TRACE_SEQ_CHECK(s) \
> do { \
> - if
Hi Arnaldo,
On Tue, 14 Jan 2014 10:09:07 -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 14, 2014 at 10:41:37AM +0900, Masami Hiramatsu escreveu:
>> (2014/01/14 3:14), Arnaldo Carvalho de Melo wrote:
>> > Jiri, this is something else for the give-me-more-ponies list for
>> > tests/make:
Excerpts from Winkler, Tomas's message of 2014-01-14 19:31:26 +1100:
> > Today's linux-next merge of the akpm-current tree got a conflict in
> > drivers/misc/mei/init.c between commit 33ec08263147 ("mei: revamp mei
> > reset state machine") from the char-misc tree and commit dd045dab2999
> >
On Tue, 14 Jan 2014 18:14:46 +0100 Nicolas Schichan
wrote:
>
>
> Hi,
>
> I have recently been trying to find the cause a livelock occurring during MD
> device open.
>
> The livelock happens when a process tries to open an MD device for the
> first time and another opens the same MD device
On Tue, Jan 14, 2014 at 12:37:38PM +0300, Sergey Senozhatsky wrote:
> Introduce init_done() helper function which allows us to drop
> `init_done' struct zram member. init_done() uses the fact that
> ->init_done == 1 equals to ->meta != NULL.
>
> Signed-off-by: Sergey Senozhatsky
Acked-by:
Now all of its users were gone. :)
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/event-utils.h | 4
tools/lib/traceevent/parse-utils.c | 44 --
2 files changed, 48 deletions(-)
diff --git a/tools/lib/traceevent/event-utils.h
Hello,
When plugins are loaded, they register various event and function
handlers. But they don't unregister even after the plugins unloaded
so that events could have refererences to non-existing handlers.
This patchset added relevant unregister functions to handle that.
Note that this is not
If realloc() fails, it'll leak the buffer. Also increate buffer size
only if the allocation succeeded.
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/trace-seq.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/tools/lib/traceevent/trace-seq.c
When a plugin unloaded it needs to unregister its print handler from
pevent. So add unregister function to do it.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/event-parse.c | 23 +++
tools/lib/traceevent/event-parse.h | 2 ++
2 files changed, 25
The PEVENT_PLUGIN_UNLOADER function might need some cleanup using
pevent like unregister some handlers. So pass pevent as argument.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/event-parse.h | 7 ---
tools/lib/traceevent/event-plugin.c| 4 ++--
When a plugin unloaded it needs to unregister its handler from pevent.
So add unregister function to do it.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/event-parse.c | 113 -
tools/lib/traceevent/event-parse.h | 3 +
2 files changed,
The function handler should be unregistered when the plugin unloaded
otherwise it'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_function.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/lib/traceevent/plugin_function.c
The trace_seq->state is for tracking errors during the use of
trace_seq APIs and getting rid of die() in it.
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/Makefile | 2 +-
tools/lib/traceevent/event-parse.h | 7 ++
tools/lib/traceevent/trace-seq.c | 46
On Tue, Jan 14, 2014 at 1:05 AM, Ard Biesheuvel
wrote:
> On 10 January 2014 17:30, Roy Franz wrote:
>> This patch adds EFI stub support for the ARM Linux kernel. The EFI stub
>> operates similarly to the x86 stub: it is a shim between the EFI firmware
>> and the normal zImage entry point, and
The event handlers should be unregistered when the plugin unloaded
otherwise they'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_sched_switch.c | 12
1 file changed, 12 insertions(+)
diff --git
The function handler should be unregistered when the plugin unloaded
otherwise it'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_cfg80211.c | 7 +++
1 file changed, 7 insertions(+)
diff --git
The kvm handlers should be unregistered when the plugin unloaded
otherwise they'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_kvm.c | 30 ++
1 file changed, 30 insertions(+)
diff --git
The event handler should be unregistered when the plugin unloaded
otherwise it'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_mac80211.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/tools/lib/traceevent/plugin_mac80211.c
The kmem handlers should be unregistered when the plugin unloaded
otherwise they'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_kmem.c | 22 ++
1 file changed, 22 insertions(+)
diff --git
Use plain malloc() and check its return value.
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/trace-seq.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools/lib/traceevent/trace-seq.c b/tools/lib/traceevent/trace-seq.c
index 941d35d2cf87..339a0ffa21d5 100644
The timer handlers should be unregistered when the plugin unloaded
otherwise they'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_hrtimer.c | 10 ++
1 file changed, 10 insertions(+)
diff --git
The function handler should be unregistered when the plugin unloaded
otherwise it'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_xen.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/tools/lib/traceevent/plugin_xen.c
The function handlers should be unregistered when the plugin unloaded
otherwise they'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_jbd2.c | 11 +++
1 file changed, 11 insertions(+)
diff --git
The function handler should be unregistered when the plugin unloaded
otherwise it'll try to access invalid memory.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/plugin_scsi.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/tools/lib/traceevent/plugin_scsi.c
On 01/14/14 at 11:24am, Vivek Goyal wrote:
> On Tue, Jan 14, 2014 at 12:16:39PM +, One Thousand Gnomes wrote:
> > On Tue, 14 Jan 2014 16:23:23 +0800
> > Dave Young wrote:
> >
> > > In kdump kernel watchdog could interrupt vmcore capturing because we
> > > have no way to disable/stop it while
Veaceslav Falico writes:
> On Tue, Jan 14, 2014 at 11:31:39AM -0800, Greg KH wrote:
>>On Tue, Jan 14, 2014 at 08:12:08PM +0100, Veaceslav Falico wrote:
>>> On Tue, Jan 14, 2014 at 10:21:35AM -0800, Greg KH wrote:
>>> >On Tue, Jan 14, 2014 at 06:17:40PM +0100, Veaceslav Falico wrote:
>>> >>Hi,
On Wed, 15 Jan 2014 10:29:48 +0900 Minchan Kim wrote:
> Oops, I missed Tested-by from Sergey. Really, sorry.
> If I have a chance to resend from any review, I will add. Otherwise,
> Andrew, Could you add his tested-by?
Sure.
I normally wouldn't consider such a patchset this late in the kernel
Hello Jerome,
On Tue, Jan 14, 2014 at 10:29:40AM +0100, Jerome Marchand wrote:
> On 01/13/2014 12:19 PM, Minchan Kim wrote:
> > read/write lock's performance is really bad compared to
> > mutex_lock in write most workload.(AFAIR, recenlty there
> > were some effort to enhance it but not sure it
On Mon, 13 Jan 2014, William Roberts wrote:
> introduce get_cmdline() for retreiving the value of a processes
> proc/self/cmdline value.
>
> Signed-off-by: William Roberts
Acked-by: David Rientjes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Mon, 13 Jan 2014, William Roberts wrote:
> Re-factor proc_pid_cmdline() to use get_cmdline() helper
> from mm.h.
>
> Signed-off-by: William Roberts
Acked-by: David Rientjes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, Jan 15, 2014 at 10:11:06AM +0900, Minchan Kim wrote:
> Currently, zram->lock rw_semaphore is coarse-grained so it hurts
> for scalability.
> This patch try to enhance it with remove the lock in read path.
>
> [1] uses atomic opeartion so it removes dependency of 32bit stat
> from
On Wed, Oct 23, 2013 at 05:31:22PM +0800, Tiejun Chen wrote:
> We need to store thread info to these exception thread info like something
> we already did for PPC32.
>
> Signed-off-by: Tiejun Chen
>
> ---
> arch/powerpc/kernel/exceptions-64e.S | 22 +++---
> 1 file changed, 19
On Wed, 8 Jan 2014, Grygorii Strashko wrote:
> Update X86 code to use NUMA_NO_NODE instead of MAX_NUMNODES while
> calling memblock APIs, because memblock API is changed to use NUMA_NO_NODE and
> will produce warning during boot otherwise.
>
> See:
> https://lkml.org/lkml/2013/12/9/898
>
> Cc:
On 01/14/2014 08:11 PM, Johannes Berg wrote:
> On Tue, 2014-01-14 at 15:41 +0800, Ying Xue wrote:
>
>> @@ -2218,10 +2194,6 @@ static int nl80211_set_wiphy(struct sk_buff *skb,
>> struct genl_info *info)
>> rdev->wiphy.coverage_class = old_coverage_class;
>> }
>>
On 01/14/14 at 02:21pm, Prarit Bhargava wrote:
> When booting a kexec/kdump kernel on a system that has specific memory hotplug
> regions the boot will fail with warnings like:
>
> [2.939467] swapper/0: page allocation failure: order:9, mode:0x84d0
> [2.946564] CPU: 0 PID: 1 Comm:
On Tue, 2014-01-14 at 14:41 +, Mark Brown wrote:
> On Tue, Jan 14, 2014 at 04:00:17PM +0800, Zhang Rui wrote:
> > On Mon, 2014-01-13 at 17:35 +, Mark Brown wrote:
> > > On Mon, Jan 13, 2014 at 09:48:31PM +0800, Zhang Rui wrote:
> > > > ACPI enumerated devices has ACPI style _HID and _CID
On Tue, 14 Jan 2014 17:05:42 -0800 (PST) David Rientjes
wrote:
> On Tue, 14 Jan 2014, Andrew Morton wrote:
>
> > From: Andrew Morton
> > Subject: mm/memory_hotplug.c: register_memory_resource() fixes
> >
> > - register_memory_resource() should not go BUG on ENOMEM. That's
> > appropriate
On 01/14/14 at 10:18am, H. Peter Anvin wrote:
> On 01/13/2014 05:40 PM, Dave Young wrote:
> > On 01/13/14 at 06:48am, Arjan van de Ven wrote:
> >> On 1/13/2014 4:23 AM, Dave Young wrote:
>
> > How about do not limit to only if (pgd) case, instead do something
> > like below: set
(2014/01/15 3:24), Nathan Zimmer wrote:
> We don't need to do register_memory_resource() since it has its own lock and
> doesn't make any callbacks.
>
> Also register_memory_resource return NULL on failure so we don't have anything
> to cleanup at this point.
>
>
> The reason for this rfc is I
Some of fields in zram->stats are protected by zram->lock which
is rather coarse-grained so let's use atomic operation without
explict locking.
This patch is ready for removing dependency of zram->lock in
read path which is very coarse-grained rw_semaphore.
Of course, this patch adds new atomic
Use the syscon driver to parse out the reboot register map and issue
reboot via the regmap function.
Signed-off-by: Feng Kan
---
drivers/power/reset/xgene-reboot.c | 75 +---
1 files changed, 19 insertions(+), 56 deletions(-)
diff --git
Select X-Gene reboot driver for X-Gene platform.
Signed-off-by: Feng Kan
---
arch/arm64/Kconfig |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 249acb9..bfdf029 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@
Currently, zram->lock rw_semaphore is coarse-grained so it hurts
for scalability.
This patch try to enhance it with remove the lock in read path.
[1] uses atomic opeartion so it removes dependency of 32bit stat
from zram->lock.
[2] introduces table own lock instead of relying on zram->lock.
[3]
Currently, table is protected by zram->lock but it's rather
coarse-grained lock and it makes hard for scalibility.
Let's use own rwlock instead of depending on zram->lock.
This patch adds new locking so obviously, it would make slow
but this patch is just prepartion for removing coarse-grained
Add missing dts entries for the X-Gene reboot driver.
Signed-off-by: Feng Kan
---
arch/arm64/boot/dts/apm-storm.dtsi | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/arch/arm64/boot/dts/apm-storm.dtsi
b/arch/arm64/boot/dts/apm-storm.dtsi
index d37d736..7beac9d
Enable X-Gene platform driver for the X-Gene platform. Change the
driver to use syscon to access the system clock unit's system
reset register.
V2 Change:
- Add support for using ACPI resource.
V3 Change:
- Remove the reboot driver's use of acpi resource patch.
- Change
101 - 200 of 1818 matches
Mail list logo
